Bug 127056 - ubuntu 18.04.3 crashes when loading Libreoffice after kernel update to 5.0.0-25-generic
Summary: ubuntu 18.04.3 crashes when loading Libreoffice after kernel update to 5.0.0-...
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
6.2.6.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-08-20 15:50 UTC by S Kumar
Modified: 2020-06-07 03:49 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
gdbtrace.log (2.72 KB, text/x-log)
2019-09-01 17:33 UTC, S Kumar
Details

Note You need to log in before you can comment on or make changes to this bug.
Description S Kumar 2019-08-20 15:50:28 UTC
Description:
I have been using Libreoffice since version 5 on ubuntu 12.04 to the latest ubuntu. Three days back my kernel got updated to 5.0.0-25-generic in ubuntu 18.04.3,since then the moment i start libreoffice, my system freezes when progress bar reaches the end. I have to do a reset to boot in to my system.
I have a Ryzen 3 2200G with MSI A320M board with 16 gigs of RAM. Till now i never had any problems. Can you suggest any solutions.

Steps to Reproduce:
1.Start libreoffice, it crashes ubuntu 18.04.3 once it reaches the end of progress bar
2.
3.

Actual Results:
ubuntu freezes

Expected Results:
ubuntu freezes


Reproducible: Always


User Profile Reset: No



Additional Info:
Normal loading and able to work
Comment 1 Julien Nabet 2019-08-20 16:09:32 UTC
Here are some steps you can follow:
https://wiki.documentfoundation.org/QA/FirstSteps
Comment 2 Julien Nabet 2019-08-20 16:10:33 UTC
If you still reproduce the crash after having applied my last comment, you can retrieve a backtrace by following steps from :
https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace
Comment 3 S Kumar 2019-09-01 17:33:52 UTC
Created attachment 153797 [details]
gdbtrace.log
Comment 4 S Kumar 2019-09-01 17:35:39 UTC
I ran $libreoffice --safe-mode and turned off the opengl and opencl. On restarting libreoffice it runs normally.
If select opencl and restart then ubuntu hangs again. I have to press reset button to again start ubuntu.
The first steps, you mentioned gives me access to help only once I turn off the opengl and opencl so I get (UI Render: default).

I tried How to get a backtrace steps, but once i tried crashing it by activating opencl,, ubuntu crashes and i cant get libreoffice to start or shut down or even ubuntu.
Comment 5 Julien Nabet 2019-09-01 18:19:33 UTC
This seems weird:
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
warning: Corrupted shared library list: 0x55555582b6e0 != 0x55555582a780

I don't know what could be the culprit.

For the test, could you give a try to LO 6.3.0 by using LO ppa (see https://launchpad.net/~libreoffice/+archive/ubuntu/ppa)?
(Also, be sure to have all the updates of your Ubuntu)
Comment 6 Xisco Faulí 2019-11-08 12:08:56 UTC
Hello S Kumar,
Could you please try to reproduce it with the latest version of LibreOffice
from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the bug is still present in the latest version.
Comment 7 QA Administrators 2020-05-07 03:58:30 UTC Comment hidden (obsolete)
Comment 8 QA Administrators 2020-06-07 03:49:27 UTC
Dear S Kumar,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp