Bug 101836

Summary:	Crash when OpenGL enabled with AMD GPU, mesa driver, in Ubuntu 16.04
Product:	LibreOffice	Reporter:	Aron Budea <aron.budea>
Component:	graphics stack	Assignee:	Not Assigned <libreoffice-bugs>
Status:	RESOLVED WORKSFORME
Severity:	critical	CC:	bjoern.michaelsen, serval2412
Priority:	medium
Version:	5.1.4.2 release
Hardware:	All
OS:	Linux (All)
See Also:	https://bugs.documentfoundation.org/show_bug.cgi?id=101387 https://bugs.documentfoundation.org/show_bug.cgi?id=100981 https://launchpad.net/bugs/1622339 https://bugs.documentfoundation.org/show_bug.cgi?id=102295
Whiteboard:
Crash report or crash signature:		Regression By:
Bug Depends on:
Bug Blocks:	97937
Attachments:	Trace of the crash

Description Aron Budea 2016-09-01 07:41:23 UTC

Created attachment 127108 [details]
Trace of the crash

I'm using an AMD A10-7800 with integrated GPU, and in this case Ubuntu 16.04 with default drivers.

1. Enable OpenGL rendering
2. Visit 'Help -> About LibreOffice' (or probably just do a bunch of random things, I was going for the simplest way)
=> LibreOffice, the driver, sometimes the whole system crashes.

Happens both with v5.1.4.2 and v5.2.1.2.

This crash is mentioned in different bug reports already: bug 101387 and bug 100981. => setting status of this report to NEW

Setting severity to critical: though the crash only appears once before automatically disabling OpenGL, it's a particularly nasty one.

Attaching gdbtrace log.

Comment 1 Aron Budea 2016-09-01 07:43:09 UTC

Björn, you might want to follow up on this.

Comment 2 Aron Budea 2016-09-27 02:05:22 UTC

So, I opened a ticket on launchpad, which was closed with the hint that Ubuntu's builtin crash reporter should be used. I filed a crash report.

I wonder if the fixes for bug 102295 have any effect here... have to check later.

Comment 3 QA Administrators 2017-10-23 14:05:12 UTC Comment hidden (obsolete)

** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not
appropriate in this case)

If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword

Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

Comment 4 Julien Nabet 2018-01-29 13:42:33 UTC

Aron: do you still reproduce this after having upgraded towards last stable LO version (by using ppa) + last stable graphic/OpenGL drivers?
(+ rename your LO directory profile as usual to force LO to rescan OpenGL drivers)

If you still reproduce this, could you apply https://wiki.documentfoundation.org/QA/FirstSteps#Graphics-related_issues_.28OpenGL.29 ?
Indeed, perhaps we may need to blacklist some OpenGL Driver? (see https://opengrok.libreoffice.org/xref/core/vcl/opengl/opengl_blacklist_windows.xml)

Comment 5 Aron Budea 2018-02-05 05:16:19 UTC

No crash in 6.0.0.3 / Ubuntu 17.10 with OpenGL enabled.
Closing as WFM.