No X display - gdm3 crash with segfault

[Dash]

This desktop was running 16.04.5 version and started few weeks ago to have the desktop crashing. In dmesg I saw compiz segfault at 0 ip [...] error 4. I decide to upgrade to 18.04.1 to solve this problem but it's still there: gnome-shell at 0 ip [...] error 4

In 18.04 i even don't get the desktop, only the mouse indicator is visible, disappearing from time to time (seems on each crash).

Attached is the output of an radeontool dump. The desktop is unusable in graphic mode.

Daniel

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
Uname: Linux 4.15.0-34-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.3
Architecture: amd64
Date: Wed Sep 5 14:40:14 2018
DistUpgraded: 2018-09-05 13:03:08,966 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py'
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RS482/RS485 [Radeon Xpress 1100/1150] [1002:5974] (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company DC5750 Microtower [103c:280a]
   Subsystem: Hewlett-Packard Company RS480 [Radeon Xpress 1150] (Secondary) [103c:280b]
InstallationDate: Installed on 2016-03-03 (916 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160227)
MachineType: Hewlett-Packard HP Compaq dc5750 Small Form Factor
ProcEnviron:
 TERM=screen
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=8c2df27f-cbc4-4c8d-a4f1-dc7994b41016 ro
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to bionic on 2018-09-05 (0 days ago)
dmi.bios.date: 04/18/2007
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 786E3 v02.22
dmi.board.name: 0A64h
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: CZC8312220
dmi.chassis.type: 4
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr786E3v02.22:bd04/18/2007:svnHewlett-Packard:pnHPCompaqdc5750SmallFormFactor:pvr:rvnHewlett-Packard:rn0A64h:rvr:cvnHewlett-Packard:ct4:cvr:
dmi.product.family: 103C_53307F
dmi.product.name: HP Compaq dc5750 Small Form Factor
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Wed Sep 5 08:36:00 2018
xserver.configfile: default
xserver.devices:
 input Power Button KEYBOARD, id 6
 input Power Button KEYBOARD, id 7
 input AT Translated Set 2 keyboard KEYBOARD, id 8
 input ImPS/2 Generic Wheel Mouse MOUSE, id 9
 input HP WMI hotkeys KEYBOARD, id 10
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.8
xserver.video_driver: radeon

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

[Dash (devel-tootai)]

Hi Daniel,

I found 2 files: /var/crash/_usr_bin_gnome-shell.124.crash and /var/crash/_usr_bin_Xwayland.124.crash that I sended them with ubuntu-bug but after this I never got new bugs ID :( Two new files appeard with extension .upload and they are empty. There is also a .lock file in this directory.

Where did I do something wrong ?

[Dash (devel-tootai)]

I tried point 2. Here are the links:

From 18.04 version

https://errors.ubuntu.com/oops/c20dade6-b1a0-11e8-8fa5-fa163ee63de6
https://errors.ubuntu.com/oops/da31709a-b19f-11e8-8fa5-fa163ee63de6

From 16.04 version

https://errors.ubuntu.com/oops/01680142-9cae-11e8-b517-fa163e0ec2f1
https://errors.ubuntu.com/oops/8380e58a-9ca5-11e8-add5-fa163e54c21f
https://errors.ubuntu.com/oops/2a8c663e-9a57-11e8-aaf2-fa163ef911dc

[Daniel van Vugt (vanvugt)]

Thanks. I can only decode one of those, which is bug 1731911.

Next, please go to step 3 in comment #2.

[Dash (devel-tootai)]

Bug #1791023 is the crash report after having applied the workaround. It's now against gdm3.