System freezes after opening LibreOffice with AMD GPU and OpenGL rendering turned on

[Aron Budea]

I'm using an AMD A10-7800 APU (Kaveri with R7-category integrated GPU (GCN)), OS is Ubuntu 16.04 with default drivers.

Steps to reproduce:
1. Start LibreOffice.
2. Enable OpenGL rendering via menu Tools -> Options..., then View -> Use OpenGL for all rendering (on restart).
3. Restart LibreOffice.
4. Open menu Help -> About LibreOffice.

=> Driver will crash, attempt to restart (after screen going dark 1-2 times) and potentially freeze the whole system.

This happens with:
 -LibreOffice 5.1.4.2 bundled with Ubuntu 16.04,
 -also with 5.2.1.2 distributed by The Document Foundation.

This bug should probably be raised against the driver, but I'm not familiar with where they are tracked, so raising the issue here, since it seems to affect a wide range of systems with the default Ubuntu 16.04 installation (fortunately OpenGL rendering is turned off by default in LibreOffice).
The issue is also tracked in LibreOffice Bugzilla.

Note that the bug was reported in normal state, as it wouldn't have been possible to do so after the crash.

Let me know if I should supply further details.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: libreoffice-core 1:5.1.4-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Sep 11 15:35:54 2016
ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
InstallationDate: Installed on 2016-07-04 (68 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)
---
.tmp.unity_support_test.0:

ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
BootLog:

CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
DistUpgraded: Fresh install
DistroCodename: xenial
DistroRelease: Ubuntu 16.04
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 Graphics] [1002:130f] (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Kaveri [Radeon R7 Graphics] [1043:85cb]
InstallationDate: Installed on 2016-07-04 (68 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: System manufacturer System Product Name
Package: xorg 1:7.7+13ubuntu3
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=ff1c7218-9477-4528-bf93-8e5ff09cbc1b ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Tags: xenial ubuntu compiz-0.9
Uname: Linux 4.4.0-36-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 03/10/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2903
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: A88XM-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2903:bd03/10/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-PLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.12.2+16.04.20160801.3-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2

[penalvch (penalvch)]

Aron Budea, thank you for reporting this and helping make Ubuntu better.

Could you please run the following command once from a terminal by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information:
apport-collect -p xorg 1622339

[Aron Budea (baron-z)]

apport information

[Aron Budea (baron-z)]

apport information

[Aron Budea (baron-z)]

apport information

[Aron Budea (baron-z)]

apport information

[Aron Budea (baron-z)]

apport information

[Aron Budea (baron-z)]

apport information

[Aron Budea (baron-z)]

apport information

[Aron Budea (baron-z)]

apport information

[Aron Budea (baron-z)]

apport information

[Aron Budea (baron-z)]

apport information

[Aron Budea (baron-z)]

apport information

[Aron Budea (baron-z)]

apport information

[Aron Budea (baron-z)]

apport information

[Aron Budea (baron-z)]

apport information

[Aron Budea (baron-z)]

apport information

[Aron Budea (baron-z)]

apport information

[Aron Budea (baron-z)]

apport information

[Aron Budea (baron-z)]

apport information

[Aron Budea (baron-z)]

apport information

[penalvch (penalvch)]

Aron Budea, to clarify, after the system freezes, is there a crash file in /var/crash ?

[Aron Budea (baron-z)]

Yes, attaching the file.

[Aron Budea (baron-z)]

After switching screen with Ctrl-Alt-F1, the driver printed out some error messages, see attached photo.

I hope the attached information helps.
Thank you for your assistance so far, Christopher.

[penalvch (penalvch)]

Aron Budea, thank you for reporting this and helping make Ubuntu better. However, your crash report is manually attached.

Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal:
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y dist-upgrade && sudo service apport start force_start=1

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. Now reproduce the crash, then open a terminal, navigate to your /var/crash directory and file your report with:
sudo ubuntu-bug /var/crash/_my_crash_report.crash

where _my_crash_report.crash is the crash you would like to report. By default, this sends the crash to the Ubuntu Error Tracker infrastructure, which is different than Launchpad. For more on this, please see https://wiki.ubuntu.com/ErrorTracker .

However, if after doing this you would still like to have a crash report posted to Launchpad, for example to ease triage and add others to your report, one would need to open the following file via a terminal:
sudo nano /etc/apport/crashdb.conf

and comment out the line:
'problem_types': ['Bug', 'Package'],

by changing it to:
# 'problem_types': ['Bug', 'Package'],

Save, close, and file the crash report via:
sudo ubuntu-bug /var/crash/FILENAME.crash

Where FILENAME is the actual name of the file found in the folder.

However, this report is being closed since the process outlined above will deal with this issue more efficiently.

Also, please do not attach your crash report manually to this report and reopen it.

Thank you for your help.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs