Xorg repeatedly crashes with SIGABRT

[lotuspsychje]

Ubuntu 20.04 development branch with kernel 5.3.0-18-generic up to date @ 27/11/2019

Several xorg crashes, unsure what have caused them

https://errors.ubuntu.com/oops/5f21a242-0a72-11ea-a7f3-fa163e6cac46

https://errors.ubuntu.com/oops/fffbd248-00f2-11ea-b65c-fa163e102db1

https://errors.ubuntu.com/oops/9ca0ef46-f975-11e9-a710-fa163e6cac46

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu9
Architecture: amd64
BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov 27 11:21:11 2019
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus: virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: CLEVO/KAPOK Computer UHD Graphics 620 [1558:7a01]
InstallationDate: Installed on 2019-10-25 (33 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191021)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:0025 Intel Corp.
 Bus 001 Device 002: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Notebook N7x0WU
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=b5dfba6b-1ac7-4113-8538-36b84cb54969 ro quiet splash vt.handoff=7
SourcePackage: xorg-server
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/07/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 7.13
dmi.board.asset.tag: Tag 12345
dmi.board.name: N7x0WU
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: N7x0WU
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.100-4
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

[Sebastien Bacher (seb128)]

Thank you for your bug report. Could you describe what you were doing at the time of the crash?
Could you also add your 'journalctl -b 0' log after getting the issue?

[lotuspsychje (lotuspsychje)]

@ Sebastien

I'm not really sure of this, but i think this happens when Xscreensaver
starts (wich i also have a bug for: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1849928 )

journal log attached

[Daniel van Vugt (vanvugt)]

None of those error reports are retraceable. The next best option is to wait for another crash and then attach a fresh Xorg.log so please do that. Please also tell us if you have any files in /var/crash.

[lotuspsychje (lotuspsychje)]

Yes i have currently 3 xorg crashes and 1 gnome-shell one in /var/crash

attached xorg.log

[Daniel van Vugt (vanvugt)]

Thanks but that log does not show a crash.

Please try following these instructions for your latest .crash files:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

[lotuspsychje (lotuspsychje)]

https://errors.ubuntu.com/user/cb36c5de1ffb50ae482d3229f8a2f70e727b96e656d23cc6d5028382d6e0be0a0d5d0534c9c092db38d15d6e49120078257f2f7842d480f0bb7db5d20caa84db

[Daniel van Vugt (vanvugt)]

Thanks again. Unfortunately it seems something strange is happening with your Xorg crashes and none are retraceable, all saying:

"This problem failed to retrace because there was no crash signature after retracing."

The only extra information we have from those crashes is:

dec 04 20:24:34 pluto gnome-shell[21047]: Connection to xwayland lost

which suggests it is Xwayland crashing. That reminds me, I think/wonder if upstream disabled Xwayland crash dumps in this version....

[Daniel van Vugt (vanvugt)]

Next time (and every time) after a crash happens, on the very next boot please run:

  journalctl -b-1 > prevboot.txt

and then send us the file 'prevboot.txt'.

[Daniel van Vugt (vanvugt)]

I also wonder why the 'Xorg' binary is crashing in the same session as 'Xwayland' problems being logged. Those two should never occur in the same session.

[lotuspsychje (lotuspsychje)]

journal logs attached

not sure about Xwayland, want me to test some time in wayland if i can reproduce?

[Daniel van Vugt (vanvugt)]

Thanks, that is the right log and it shows:

dec 20 03:37:32 RooTBoX whoopsie[3823]: [03:37:32] Parsing /var/crash/_usr_lib_xorg_Xorg.1000.crash.

dec 20 03:37:32 RooTBoX whoopsie[3823]: [03:37:32] Uploading /var/crash/_usr_lib_xorg_Xorg.1000.crash.

But no other info about the crash. Maybe the crash was from the boot before that, so please also try:

  journalctl -b-2 > prevprevboot.txt

[lotuspsychje (lotuspsychje)]

journalctl -b-2 > prevprevboot.txt as requested

[Daniel van Vugt (vanvugt)]

Success!

dec 19 16:17:29 RooTBoX /usr/lib/gdm3/gdm-x-session[3035]: (EE) Backtrace:
dec 19 16:17:29 RooTBoX /usr/lib/gdm3/gdm-x-session[3035]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x55b862a79acc]
dec 19 16:17:29 RooTBoX /usr/lib/gdm3/gdm-x-session[3035]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7f1b2d46859f]
dec 19 16:17:29 RooTBoX /usr/lib/gdm3/gdm-x-session[3035]: (EE) 2: /usr/lib/xorg/modules/libglamoregl.so (glamor_get_pixmap_texture+0xa1) [0x7f1b2cbf7f71]
dec 19 16:17:29 RooTBoX /usr/lib/gdm3/gdm-x-session[3035]: (EE) 3: /usr/lib/xorg/modules/libglamoregl.so (glamor_finish+0xb6) [0x7f1b2cbf9016]
dec 19 16:17:29 RooTBoX /usr/lib/gdm3/gdm-x-session[3035]: (EE) 4: /usr/lib/xorg/modules/libglamoregl.so (glamor_create_gc+0xd96e) [0x7f1b2cc1625e]
dec 19 16:17:29 RooTBoX /usr/lib/gdm3/gdm-x-session[3035]: (EE) 5: /usr/lib/xorg/modules/libglamoregl.so (glamor_finish+0x7c0) [0x7f1b2cbf9ab0]
dec 19 16:17:29 RooTBoX /usr/lib/gdm3/gdm-x-session[3035]: (EE) 6: /usr/lib/xorg/modules/libglamoregl.so (glamor_finish+0xde6) [0x7f1b2cbfa8d6]
dec 19 16:17:29 RooTBoX /usr/lib/gdm3/gdm-x-session[3035]: (EE) 7: /usr/lib/xorg/Xorg (miCopyRegion+0x9b) [0x55b862a570fb]
dec 19 16:17:29 RooTBoX /usr/lib/gdm3/gdm-x-session[3035]: (EE) 8: /usr/lib/xorg/Xorg (miDoCopy+0x446) [0x55b862a57846]
dec 19 16:17:29 RooTBoX /usr/lib/gdm3/gdm-x-session[3035]: (EE) 9: /usr/lib/xorg/modules/libglamoregl.so (glamor_finish+0x1838) [0x7f1b2cbfbf28]
dec 19 16:17:29 RooTBoX /usr/lib/gdm3/gdm-x-session[3035]: (EE) 10: /usr/lib/xorg/Xorg (DamageRegionAppend+0x3926) [0x55b862a01a56]
dec 19 16:17:29 RooTBoX /usr/lib/gdm3/gdm-x-session[3035]: (EE) 11: /usr/lib/xorg/Xorg (SendGraphicsExpose+0x2cd) [0x55b862914b2d]
dec 19 16:17:29 RooTBoX /usr/lib/gdm3/gdm-x-session[3035]: (EE) 12: /usr/lib/xorg/Xorg (SendErrorToClient+0x354) [0x55b862918f44]
dec 19 16:17:29 RooTBoX /usr/lib/gdm3/gdm-x-session[3035]: (EE) 13: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x55b86291cfd4]
dec 19 16:17:29 RooTBoX /usr/lib/gdm3/gdm-x-session[3035]: (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7f1b2d2871e3]
dec 19 16:17:29 RooTBoX /usr/lib/gdm3/gdm-x-session[3035]: (EE) 15: /usr/lib/xorg/Xorg (_start+0x2e) [0x55b862906a1e]
dec 19 16:17:29 RooTBoX /usr/lib/gdm3/gdm-x-session[3035]: (EE)
dec 19 16:17:29 RooTBoX /usr/lib/gdm3/gdm-x-session[3035]: (EE) Segmentation fault at address 0x0
dec 19 16:17:29 RooTBoX /usr/lib/gdm3/gdm-x-session[3035]: (EE)
dec 19 16:17:29 RooTBoX /usr/lib/gdm3/gdm-x-session[3035]: Fatal server error:
dec 19 16:17:29 RooTBoX /usr/lib/gdm3/gdm-x-session[3035]: (EE) Caught signal 11 (Segmentation fault). Server aborting

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1853266, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.