Xorg crash

[pd]

My Ubuntu 22.04.1 LTS installation crashes, but I was not able to figure out how to reproducibly trigger the crash. The last time it happened was with firefox and zoom running, the display suddenly went black and after a few seconds the X login screen appeared, my session gone.

There are files in /var/crash/

-rw-r--r-- 1 root whoopsie 0 Jan 5 14:09 _usr_lib_xorg_Xorg.0.upload
-rw-r----- 1 root whoopsie 12792518 Jan 5 14:09 _usr_lib_xorg_Xorg.0.crash
-rw------- 1 whoopsie whoopsie 37 Jan 5 14:09 _usr_lib_xorg_Xorg.0.uploaded
-rw-r--r-- 1 petr whoopsie 0 Jan 5 14:13 _usr_bin_xfsettingsd.1000.upload
-rw-r----- 1 petr whoopsie 516897 Jan 5 14:13 _usr_bin_xfsettingsd.1000.crash
-rw------- 1 whoopsie whoopsie 37 Jan 5 14:13 _usr_bin_xfsettingsd.1000.uploaded
-rw-r--r-- 1 petr whoopsie 0 Jan 5 14:13 _opt_zoom_zoom.1000.upload
-rw-r----- 1 petr whoopsie 46590288 Jan 5 14:13 _opt_zoom_zoom.1000.crash
-rw------- 1 whoopsie whoopsie 37 Jan 5 14:13 _opt_zoom_zoom.1000.uploaded

and .xsession-errors.old ends with

(xfwm4:8122): xfwm4-WARNING **: 14:11:00.736: unmanaged net_wm_state (window 0x6000049, atom "_NET_WM_STATE_STAYS_ON_TOP")
(xfwm4:10847): Gtk-WARNING **: 14:13:01.216: cannot open display: :0.0
Exiting due to channel error.
Failed to parse arguments: Cannot open display: :0.0
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
(xfsettingsd:10849): xfsettingsd-ERROR **: 14:13:01.239: Unable to open display.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
(xfwm4:10854): Gtk-WARNING **: 14:13:01.244: cannot open display: :0.0
Failed to parse arguments: Cannot open display: :0.0
(xfwm4:10860): Gtk-WARNING **: 14:13:01.264: cannot open display: :0.0
(xfwm4:10863): Gtk-WARNING **: 14:13:01.280: cannot open display: :0.0
Failed to parse arguments: Cannot open display: :0.0
(xfwm4:10865): Gtk-WARNING **: 14:13:01.293: cannot open display: :0.0
Failed to parse arguments: Cannot open display: :0.0
Failed to parse arguments: Cannot open display: :0.0
Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0"
Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0"
Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0"
Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0"

Is it safe and useful to upload the files from /var/crash/?

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
Uname: Linux 5.13.0-35-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: XFCE
Date: Thu Jan 5 14:17:42 2023
DistUpgraded: 2022-12-25 11:03:07,557 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus:
 virtualbox/6.1.38, 5.13.0-35-generic, x86_64: installed
 virtualbox/6.1.38, 5.15.0-56-generic, x86_64: installed
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c1) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Cezanne [17aa:3f96]
InstallationDate: Installed on 2021-11-07 (424 days ago)
InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: LENOVO 20YA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-35-generic root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: Upgraded to jammy on 2022-12-25 (11 days ago)
dmi.bios.date: 09/23/2021
dmi.bios.release: 1.27
dmi.bios.vendor: LENOVO
dmi.bios.version: GMCN27WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: ThinkBook 13s G3 ACN
dmi.ec.firmware.release: 1.19
dmi.modalias: dmi:bvnLENOVO:bvrGMCN27WW:bd09/23/2021:br1.27:efr1.19:svnLENOVO:pn20YA:pvrThinkBook13sG3ACN:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrThinkBook13sG3ACN:skuLENOVO_MT_20YA_BU_idea_FM_ThinkBook13sG3ACN:
dmi.product.family: ThinkBook 13s G3 ACN
dmi.product.name: 20YA
dmi.product.sku: LENOVO_MT_20YA_BU_idea_FM_ThinkBook 13s G3 ACN
dmi.product.version: ThinkBook 13s G3 ACN
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

[Daniel van Vugt (vanvugt)]

Please tell us the contents of /var/crash/_usr_lib_xorg_Xorg.0.uploaded as it will contain the unique ID of the Xorg crash.

[pd (petr-danecek)]

The file contains this ID: 311e7093-8cfa-11ed-aae6-fa163e55efd0

[Daniel van Vugt (vanvugt)]

Thanks. Unfortunately that's not showing the crash location, I don't know why:

https://errors.ubuntu.com/oops/311e7093-8cfa-11ed-aae6-fa163e55efd0

Can you find the system log entries (using journalctl) from the time of the crash? (Thu Jan 5 14:09:26 2023)

[pd (petr-danecek)]

The journal says contains these entries:

Jan 05 14:09:26 xlap systemd[1]: Starting Process error reports when automatic reporting is enabled...
Jan 05 14:09:26 xlap systemd[1]: Started crash report submission.
Jan 05 14:09:26 xlap whoopsie[5359]: [14:09:26] Using lock path: /var/lock/whoopsie/lock
Jan 05 14:09:26 xlap systemd[1]: whoopsie.service: Deactivated successfully.
Jan 05 14:09:26 xlap whoopsie-upload-all[5358]: INFO:root:/var/crash/_usr_libexec_valgrind_memcheck-amd64-linux.1000.crash already marked for upload, skipping
Jan 05 14:09:26 xlap whoopsie-upload-all[5358]: INFO:root:Collecting info for /var/crash/_usr_lib_xorg_Xorg.0.crash...
Jan 05 14:09:26 xlap systemd[1]: Started crash report submission.
Jan 05 14:09:26 xlap whoopsie[5364]: [14:09:26] Using lock path: /var/lock/whoopsie/lock
Jan 05 14:09:26 xlap systemd[1]: whoopsie.service: Deactivated successfully.

Do you want me to attach the file /var/crash/_usr_lib_xorg_Xorg.0.crash here?

[Daniel van Vugt (vanvugt)]

No we can't process .crash files manually.

Can you check to see if Xorg logged messages about the crash in the seconds prior to Thu Jan 5 14:09:26 2023?... Xorg likes to handle its own crashes which sometimes causes us problems. We don't get clean crash reports from Xorg, or that we don't get useful symbols in its bespoke crash logger.

[pd (petr-danecek)]

I don't see anything useful in the log:

Jan 05 14:01:33 xlap gcr-prompter[3318]: Gcr: sending the secret exchange: [sx-aes-1]\npublic=4uc+8Lpm5dEaUqICltU/1RtAGdPAJRNDnjN+h4KK4+V198oPek0B866EgtZjQLXjDS9IA4iI+46VWpzNpyNd9hyBDrch5nR>
Jan 05 14:01:33 xlap gcr-prompter[3318]: Gcr: calling the PromptReady method on /org/gnome/keyring/Prompt/p3@:1.30
Jan 05 14:01:33 xlap gnome-keyring-daemon[1489]: asked to register item /org/freedesktop/secrets/collection/login/4, but it's already registered
Jan 05 14:01:33 xlap gcr-prompter[3318]: Gcr: returned from the PromptReady method on /org/gnome/keyring/Prompt/p3@:1.30
Jan 05 14:01:33 xlap gcr-prompter[3318]: Gcr: received PerformPrompt call from callback /org/gnome/keyring/Prompt/p3@:1.30
Jan 05 14:01:33 xlap gcr-prompter[3318]: Gcr: stopping prompting for operation /org/gnome/keyring/Prompt/p3@:1.30
Jan 05 14:01:33 xlap gcr-prompter[3318]: Gcr: closing the prompt
Jan 05 14:01:33 xlap gcr-prompter[3318]: Gcr: stopping prompting for operation /org/gnome/keyring/Prompt/p3@:1.30
Jan 05 14:01:33 xlap gcr-prompter[3318]: Gcr: couldn't find the callback for prompting operation /org/gnome/keyring/Prompt/p3@:1.30
Jan 05 14:01:33 xlap gcr-prompter[3318]: Gcr: stopping prompting for operation /org/gnome/keyring/Prompt/p3@:1.30
Jan 05 14:01:33 xlap gcr-prompter[3318]: Gcr: couldn't find the callback for prompting operation /org/gnome/keyring/Prompt/p3@:1.30
Jan 05 14:01:33 xlap gcr-prompter[3318]: Gcr: stopping prompting for operation /org/gnome/keyring/Prompt/p3@:1.30
Jan 05 14:01:33 xlap gcr-prompter[3318]: Gcr: couldn't find the callback for prompting operation /org/gnome/keyring/Prompt/p3@:1.30
Jan 05 14:01:33 xlap gcr-prompter[3318]: Gcr: calling the PromptDone method on /org/gnome/keyring/Prompt/p3@:1.30, and ignoring reply
Jan 05 14:01:44 xlap gcr-prompter[3318]: Gcr: 10 second inactivity timeout, quitting
Jan 05 14:01:44 xlap gcr-prompter[3318]: Gcr: unregistering prompter
Jan 05 14:01:44 xlap gcr-prompter[3318]: Gcr: disposing prompter
Jan 05 14:01:44 xlap gcr-prompter[3318]: Gcr: finalizing prompter
Jan 05 14:02:01 xlap wpa_supplicant[1006]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-66 noise=9999 txrate=144400
Jan 05 14:02:04 xlap wpa_supplicant[1006]: wlp1s0: PMKSA-CACHE-ADDED 00:23:5d:8e:bd:3e 0
Jan 05 14:02:04 xlap wpa_supplicant[1006]: wlp1s0: PMKSA-CACHE-ADDED 1c:e6:c7:3f:8a:c1 0
Jan 05 14:02:04 xlap wpa_supplicant[1006]: wlp1s0: PMKSA-CACHE-ADDED 00:23:5d:8e:bd:31 0
Jan 05 14:02:49 xlap rtkit-daemon[1213]: Supervising 8 threads of 5 processes of 1 users.
Jan 05 14:02:49 xlap rtkit-daemon[1213]: Supervising 8 threads of 5 processes of 1 users.
Jan 05 14:02:53 xlap rtkit-daemon[1213]: Supervising 8 threads of 5 processes of 1 users.
Jan 05 14:02:53 xlap rtkit-daemon[1213]: Supervising 8 threads of 5 processes of 1 users.
Jan 05 14:03:02 xlap rtkit-daemon[1213]: Supervising 8 threads of 5 processes of 1 users.
Jan 05 14:03:02 xlap rtkit-daemon[1213]: Supervising 8 threads of 5 processes of 1 users.
Jan 05 14:03:24 xlap wpa_supplicant[1006]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-62 noise=9999 txrate=270000
Jan 05 14:03:28 xlap wpa_supplicant[1006]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above...

[Daniel van Vugt (vanvugt)]

That's fine, it just means Xorg crashed hard. So please report new crashes whenever they occur again and eventually we'll have more luck.

[pd (petr-danecek)]

It just happened again, the content of /var/crash/_usr_lib_xorg_Xorg.0.uploaded is 3aa3f8c4-8f92-11ed-aafb-fa163e55efd0

[Daniel van Vugt (vanvugt)]

Thanks, but there's still no stack trace info:

https://errors.ubuntu.com/oops/3aa3f8c4-8f92-11ed-aafb-fa163e55efd0

It's possible that the crashes might be rejected if your system isn't fully up to date at the time of the crash so please make sure it is up to date:

  sudo apt update
  sudo apt full-upgrade

[pd (petr-danecek)]

It just happened again 3aa3f8c4-8f92-11ed-aafb-fa163e55efd0

In the logs I see

Jan 09 09:38:34 xlap whoopsie-upload-all[1059]: INFO:root:/var/crash/_usr_bin_xfsettingsd.1000.crash already marked for upload, skipping
Jan 09 09:38:34 xlap whoopsie-upload-all[1059]: INFO:root:/var/crash/_opt_zoom_zoom.1000.crash already marked for upload, skipping
Jan 09 09:38:34 xlap whoopsie-upload-all[1059]: INFO:root:/var/crash/_usr_lib_xorg_Xorg.0.crash already marked for upload, skipping
Jan 09 09:38:34 xlap whoopsie-upload-all[1059]: INFO:root:Waiting for whoopsie to upload reports (timeout: 20 s)
Jan 09 09:38:34 xlap whoopsie-upload-all[1059]: INFO:root:All reports uploaded successfully

I will try to the apt commands, but that should not be a problem, I upgraded my system very recently. And since then have been getting these crashes... :-/

[pd (petr-danecek)]

Updated now.

[pd (petr-danecek)]

Two more crashes, this time without a new entries in /var/crash/.
What can I do to collect more information? The system was stable before I upgraded from impish to jammy.

[Daniel van Vugt (vanvugt)]

Next time a crash happens please:

1. Wait 10 seconds.

2. Reboot.

3. Run:

   journalctl -b-1 > prevboot.txt

4. Attach the resulting text file here.

[pd (petr-danecek)]

This time it crashed almost instantly after logging in. There is a new id in /var/crash/_usr_lib_xorg_Xorg.0.uploaded

be43a9e0-9103-11ed-9d0c-fa163e993415

[Daniel van Vugt (vanvugt)]

Thanks. Unfortunately that doesn't contain the Xorg log that it should. I don't know if that's because this is Xubuntu or because this is an upgrade from 21.10 to 22.04.

On that note, you're also using an old kernel 5.13 which should have upgraded to at least 5.15. But the old kernel is *probably* not the cause of this bug.

Can you find where your current Xorg log files are (containing the crash)?

[pd (petr-danecek)]

Uh, did not have time for this until now, got quite a few crashes in the meantime. I am attaching the latest xorg log that gives a backtrace

[Daniel van Vugt (vanvugt)]

Thanks. That's a good start but the symbols are bogus:

[ 160.566] (EE) Backtrace:
[ 160.569] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x56325264c719]
[ 160.569] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7f5527424520]
[ 160.569] (EE) 2: /usr/lib/xorg/Xorg (NewCurrentScreen+0x258) [0x5632524e1298]
[ 160.569] (EE) 3: /usr/lib/xorg/Xorg (ProcSendEvent+0x848) [0x5632524e9688]
[ 160.570] (EE) 4: /usr/lib/xorg/Xorg (InitProximityClassDeviceStruct+0x1e43) [0x5632525c28b3]
[ 160.570] (EE) 5: /usr/lib/xorg/Xorg (XkbHandleActions+0x1dc) [0x5632525ece7c]
[ 160.570] (EE) 6: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x7c1) [0x5632525e5f51]
[ 160.570] (EE) 7: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x9be) [0x5632525e614e]
[ 160.570] (EE) 8: /usr/lib/xorg/Xorg (TimerSet+0x170) [0x563252645c90]
[ 160.570] (EE) 9: /usr/lib/xorg/Xorg (WaitForSomething+0x258) [0x563252645f18]
[ 160.570] (EE) 10: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x5632524d6267]
[ 160.570] (EE) 11: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x5632524da534]
[ 160.571] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) [0x7f552740bd90]
[ 160.571] (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) [0x7f552740be40]
[ 160.571] (EE) 14: /usr/lib/xorg/Xorg (_start+0x25) [0x5632524c3605]
[ 160.571] (EE)
[ 160.571] (EE) Segmentation fault at address 0x7ffe2c2b8000

We need proper debug symbols so please install https://launchpad.net/~ubuntu-security/+archive/ubuntu/ppa/+build/24907314/+files/xserver-xorg-core-dbgsym_21.1.3-2ubuntu2.5_amd64.ddeb and continue to report all new crashes after that.

Although I can see other recent crashes from the machine in:

https://errors.ubuntu.com/user/03ee3ad05735e452058026f308fdab5a759c144bde76f488875d1d877224459da0fcea51f892a6f2d385c5ffbdcf99758f4ae9764bad8eb4f0f322cbda9ac72b

it seems your system is being silently rejected for automated crash analysis. I guess some part of the dist upgrades over the years has made the system ineligible and sadly I don't know how to fix that other than a fresh install of 22.04.

[pd (petr-danecek)]

I've got a new crash after installing the xorg-core-dbgsym, the backtrace looks the same though. What else can I provide, other than reinstalling the whole machine? That's something I'd really like to avoid if possible

[ 60.469] (EE)
[ 60.469] (EE) Backtrace:
[ 60.472] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x5625c4342719]
[ 60.473] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7f129d1d3520]
[ 60.473] (EE) 2: /usr/lib/xorg/Xorg (NewCurrentScreen+0x258) [0x5625c41d7298]
[ 60.473] (EE) 3: /usr/lib/xorg/Xorg (ProcSendEvent+0x848) [0x5625c41df688]
[ 60.473] (EE) 4: /usr/lib/xorg/Xorg (InitProximityClassDeviceStruct+0x1e43) [0x5625c42b88b3]
[ 60.474] (EE) 5: /usr/lib/xorg/Xorg (XkbHandleActions+0x1dc) [0x5625c42e2e7c]
[ 60.474] (EE) 6: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x7c1) [0x5625c42dbf51]
[ 60.474] (EE) 7: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x9be) [0x5625c42dc14e]
[ 60.474] (EE) 8: /usr/lib/xorg/Xorg (TimerSet+0x170) [0x5625c433bc90]
[ 60.474] (EE) 9: /usr/lib/xorg/Xorg (WaitForSomething+0x258) [0x5625c433bf18]
[ 60.474] (EE) 10: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x5625c41cc267]
[ 60.475] (EE) 11: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x5625c41d0534]
[ 60.475] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) [0x7f129d1bad90]
[ 60.476] (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) [0x7f129d1bae40]
[ 60.476] (EE) 14: /usr/lib/xorg/Xorg (_start+0x25) [0x5625c41b9605]
[ 60.476] (EE)
[ 60.476] (EE) Segmentation fault at address 0x7fffbdcbf000
[ 60.476] (EE)
Fatal server error:
[ 60.476] (EE) Caught signal 11 (Segmentation fault). Server aborting

[Daniel van Vugt (vanvugt)]

Thanks. It sounds like Xorg is not smart enough to use the debug symbols.

Your latest crashes on errors.ubuntu.com still show the robots are ignoring crashes from this machine. I don't know the reasons but can only guess something has changed during the upgrade process. And so the only suggestion I have right now is to reinstall from scratch if you want automated crash retracing to work.

Other weirdness in your crash reports on errors.ubuntu.com:

  JournalErrors -- No entries --

So there is no system log being collected either.

[pd (petr-danecek)]

I reinstalled the system and it happened again. The crash id from /var/crash/_usr_lib_xorg_Xorg.0.uploaded is f5810a24-aba6-11ed-b81a-fa163ef35206

[pd (petr-danecek)]

And another one...
35f5fbf4-abc7-11ed-9e34-fa163e993415

[Daniel van Vugt (vanvugt)]

Still much the same. No usable backtrace but one at least has a system log (which isn't useful). I wonder if this is a Xubuntu-specific problem with crash reports.

[Daniel van Vugt (vanvugt)]

Are you using the built-in amdgpu driver or did you install it manually?

[pd (petr-danecek)]

Everything is from the fresh install, I did none modify any of the system drivers.

[Daniel van Vugt (vanvugt)]

I've gone through the most common Xorg crashes on 22.04 and found one where the call addresses seem to match yours:

  https://errors.ubuntu.com/problem/6c8ea4e88ac1e5642e14d17c955dc4b73b389612

So that's bug 2000649. Unfortunately we don't know what change fixed it, only that it is fixed in newer Xorg releases 21.1.4 and later. And that is only in Ubuntu 22.10 and later for the moment. I don't know when Ubuntu 22.04 will get the slight Xorg update it needs to collect that fix.

[pd (petr-danecek)]

Is there something I can do to trigger this bugfix to incorporated into regular ubuntu updates? It's really annoying to work on unstable system, and knowing it has been fixed already, sigh..?

[Daniel van Vugt (vanvugt)]

The fix for bug 2000649 has been requested for inclusion in a future 22.04 update. Other than waiting, the only options are:

  * Use regular Ubuntu rather than Xubuntu, and you will get a Wayland session by default so won't experience Xorg bugs.

  * Use Xubuntu 22.10 instead of 22.04.