You are not logged in.
I also had this crash. At the moment of the crash, I was holding down my keyboard's volume down button. Here's /var/log/Xorg.0.log.old: https://pastebin.com/raw/wF03qNVU
Here is what journalctl -b was saying right before the crash:
Dec 03 01:39:43 localhost dbus-daemon[1139]: [system] Rejected: destination has a full message queue, 0 matched rules; type="error", sender="(unset)" ((bus)) interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.ServiceUnknown" requested_reply="1" destination=":1.133" (uid=1000 pid=63082 comm="/usr/lib/chromium/chromium --type=gpu-process --fi")
Dec 03 01:39:43 localhost dbus-daemon[1139]: [system] Rejected: destination has a full message queue, 0 matched rules; type="error", sender="(unset)" ((bus)) interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.ServiceUnknown" requested_reply="1" destination=":1.133" (uid=1000 pid=63082 comm="/usr/lib/chromium/chromium --type=gpu-process --fi")
Dec 03 01:39:43 localhost audit[1217]: ANOM_ABEND auid=4294967295 uid=0 gid=0 ses=4294967295 pid=1217 comm="Xorg" exe="/usr/lib/Xorg" sig=6 res=1
Dec 03 01:39:43 localhost kernel: audit: type=1701 audit(1638488383.955:435): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=1217 comm="Xorg" exe="/usr/lib/Xorg" sig=6 res=1
Dec 03 01:39:44 localhost systemd[1]: Created slice Slice /system/systemd-coredump.
Dec 03 01:39:44 localhost audit: BPF prog-id=73 op=LOAD
Dec 03 01:39:44 localhost audit: BPF prog-id=74 op=LOAD
Dec 03 01:39:44 localhost audit: BPF prog-id=75 op=LOAD
Dec 03 01:39:44 localhost systemd[1]: Started Process Core Dump (PID 121245/UID 0).
Dec 03 01:39:44 localhost audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@0-121245-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 03 01:39:44 localhost kernel: audit: type=1334 audit(1638488384.075:436): prog-id=73 op=LOAD
Dec 03 01:39:44 localhost kernel: audit: type=1334 audit(1638488384.075:437): prog-id=74 op=LOAD
Dec 03 01:39:44 localhost kernel: audit: type=1334 audit(1638488384.075:438): prog-id=75 op=LOAD
Dec 03 01:39:44 localhost kernel: audit: type=1130 audit(1638488384.075:439): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@0-121245-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 03 01:39:44 localhost systemd-coredump[121246]: [?] Process 1217 (Xorg) of user 0 dumped core.
That dbus-daemon's message had been spammed for quite a while, I noticed. It might be a separate problem, but still.
Offline
I don't know if this helps at all but, I'm not crashing. I found this message after installing acpid and starting/enabling it. When I checked it's status I found the message.
>systemctl status acpid
● acpid.service - ACPI event daemon
Loaded: loaded (/usr/lib/systemd/system/acpid.service; enabled; vendor preset: disabled)
Active: active (running) since Sat 2021-12-04 14:22:18 EST; 2min 40s ago
Docs: man:acpid(8)
Main PID: 603 (acpid)
Tasks: 1 (limit: 38386)
Memory: 364.0K
CPU: 425ms
CGroup: /system.slice/acpid.service
└─603 /usr/bin/acpid --foreground --netlink
Dec 04 14:22:18 hostname acpid[603]: waiting for events: event logging is off
Dec 04 14:22:20 hostname acpid[603]: input device has been disconnected, fd 28
Dec 04 14:22:20 hostname acpid[603]: input device has been disconnected, fd 30
Dec 04 14:22:20 hostname acpid[603]: input device has been disconnected, fd 29
Dec 04 14:22:20 hostname acpid[603]: input device has been disconnected, fd 28
Dec 04 14:22:21 hostname root[1194]: ACPI group/action undefined: jack/videoout / VIDEOOUT
Dec 04 14:22:21 hostname acpid[603]: client connected from 1190[0:0]
Dec 04 14:22:21 hostname acpid[603]: 1 client rule loaded
Dec 04 14:22:21 hostname acpid[603]: client connected from 1190[0:0]
Dec 04 14:22:21 hostname acpid[603]: 1 client rule loaded
I then installed acpi_call-dkms and regenerated my initramfs with mkinitcpio -P and that message went away. I am now receiving a bunch of messages that appear related to my Nvidia card.
acpi_call: Cannot get handle: Error: AE_NOT_FOUND
There's a lot of info in google about this particular error so may take a while to dig into. With this new information it may or may not have anything to do with your issue.
Last edited by KDen (2021-12-04 21:04:01)
Offline
FYI, I think this is probably the upstream bug "Out of bounds memory read in ActivateGrabNoDelivery() in 21.1.1" (https://gitlab.freedesktop.org/xorg/xse … ssues/1253). The symptoms are basically that Xorg crashes when using a keyboard shortcut (maybe it can happen in other cases too, but that is one), and Xorg.log shows XkbHandleActions() in the backtrace and "Segmentation fault at address XYZ" where XYZ is a value that ends in three zeroes.
Offline
Thanks @Synchronicity, it looks like that's the one!
Offline
After reading that, it appears there's no fix yet. If you're still experiencing stability issues you could try to pass some kernel flags at boot. There's quite a few related to acpi and power management. You could try them one by one to see if they help at all.
https://www.kernel.org/doc/Documentatio … meters.txt
Last edited by KDen (2021-12-05 14:35:26)
Offline
This bug hit me again. I was using the keyboard shortcut to increase the volume.
[ 5042.425] (II) event17 - USB USB Keyboard: is tagged by udev as: Keyboard
[ 5042.425] (II) event17 - USB USB Keyboard: device is a keyboard
[ 21295.213] (EE) event17 - USB USB Keyboard: client bug: event processing lagging behind by 17ms, your system is too slow
[ 21305.014] (EE) event17 - USB USB Keyboard: client bug: event processing lagging behind by 28ms, your system is too slow
[ 21448.671] (EE) event17 - USB USB Keyboard: client bug: event processing lagging behind by 25ms, your system is too slow
[ 21574.637] (EE) event17 - USB USB Keyboard: client bug: event processing lagging behind by 21ms, your system is too slow
[ 21672.513] (EE) event17 - USB USB Keyboard: client bug: event processing lagging behind by 17ms, your system is too slow
[ 21672.513] (EE) event17 - USB USB Keyboard: WARNING: log rate limit exceeded (5 msgs per 60min). Discarding future messages.
[ 25631.060] (EE) event17 - USB USB Keyboard: client bug: event processing lagging behind by 27ms, your system is too slow
[ 25668.408] (EE) event17 - USB USB Keyboard: client bug: event processing lagging behind by 36ms, your system is too slow
[ 26415.399] (EE) event17 - USB USB Keyboard: client bug: event processing lagging behind by 17ms, your system is too slow
[ 34082.974] (EE)
[ 34082.974] (EE) Backtrace:
[ 34082.974] (EE) 0: /usr/lib/Xorg (xorg_backtrace+0x89) [0x559b17a8c059]
[ 34082.974] (EE) 1: /usr/lib/Xorg (0x559b1793c000+0x15ae79) [0x559b17a96e79]
[ 34082.974] (EE) 2: /usr/lib/libpthread.so.0 (0x7f027cc9b000+0x13870) [0x7f027ccae870]
[ 34082.974] (EE) 3: /usr/lib/Xorg (0x559b1793c000+0x1e52c8) [0x559b17b212c8]
[ 34082.974] (EE) 4: /usr/lib/Xorg (0x559b1793c000+0x8d385) [0x559b179c9385]
[ 34082.974] (EE) 5: /usr/lib/Xorg (0x559b1793c000+0x8d9cc) [0x559b179c99cc]
[ 34082.974] (EE) 6: /usr/lib/Xorg (0x559b1793c000+0x8ebc3) [0x559b179cabc3]
[ 34082.974] (EE) 7: /usr/lib/Xorg (0x559b1793c000+0x10cd5b) [0x559b17a48d5b]
[ 34082.974] (EE) 8: /usr/lib/Xorg (XkbHandleActions+0x1d4) [0x559b17a827c4]
[ 34082.974] (EE) 9: /usr/lib/Xorg (0x559b1793c000+0x1dcf02) [0x559b17b18f02]
[ 34082.974] (EE) 10: /usr/lib/Xorg (0x559b1793c000+0x134c8e) [0x559b17a70c8e]
[ 34082.974] (EE) 11: /usr/lib/Xorg (0x559b1793c000+0x14e414) [0x559b17a8a414]
[ 34082.974] (EE) 12: /usr/lib/Xorg (WaitForSomething+0x2e2) [0x559b17a8a722]
[ 34082.974] (EE) 13: /usr/lib/Xorg (0x559b1793c000+0x3c83b) [0x559b1797883b]
[ 34082.974] (EE) 14: /usr/lib/libc.so.6 (__libc_start_main+0xd5) [0x7f027caf1b25]
[ 34082.974] (EE) 15: /usr/lib/Xorg (_start+0x2e) [0x559b1797975e]
[ 34082.974] (EE)
[ 34082.974] (EE) Segmentation fault at address 0x7ffd964e1000
[ 34082.974] (EE)
Fatal server error:
[ 34082.974] (EE) Caught signal 11 (Segmentation fault). Server aborting
[ 34082.974] (EE)
[ 34082.974] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 34082.974] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 34082.974] (EE)
[ 34082.974] (II) AIGLX: Suspending AIGLX clients for VT switch
[ 34083.091] (EE) Server terminated with error (1). Closing log file.
Excuse my poor English.
Offline
xorg-server 21.1.3 from testing repo still affected.
[ 37620.106] (EE) Backtrace:
[ 37620.106] (EE) 0: /usr/lib/Xorg (xorg_backtrace+0x89) [0x55fe84fba049]
[ 37620.106] (EE) 1: /usr/lib/Xorg (0x55fe84e6a000+0x15ae69) [0x55fe84fc4e69]
[ 37620.106] (EE) 2: /usr/lib/libpthread.so.0 (0x7f7469b95000+0x13870) [0x7f7469ba8870]
[ 37620.106] (EE) 3: /usr/lib/Xorg (0x55fe84e6a000+0x1e52d8) [0x55fe8504f2d8]
[ 37620.106] (EE) 4: /usr/lib/Xorg (0x55fe84e6a000+0x8d375) [0x55fe84ef7375]
[ 37620.106] (EE) 5: /usr/lib/Xorg (0x55fe84e6a000+0x8d9bc) [0x55fe84ef79bc]
[ 37620.106] (EE) 6: /usr/lib/Xorg (0x55fe84e6a000+0x8ebb3) [0x55fe84ef8bb3]
[ 37620.106] (EE) 7: /usr/lib/Xorg (0x55fe84e6a000+0x10cd4b) [0x55fe84f76d4b]
[ 37620.106] (EE) 8: /usr/lib/Xorg (XkbHandleActions+0x1d4) [0x55fe84fb07b4]
[ 37620.106] (EE) 9: /usr/lib/Xorg (0x55fe84e6a000+0x1dcf12) [0x55fe85046f12]
[ 37620.106] (EE) 10: /usr/lib/Xorg (0x55fe84e6a000+0x134c7e) [0x55fe84f9ec7e]
[ 37620.106] (EE) 11: /usr/lib/Xorg (0x55fe84e6a000+0x14e404) [0x55fe84fb8404]
[ 37620.106] (EE) 12: /usr/lib/Xorg (WaitForSomething+0x2e2) [0x55fe84fb8712]
[ 37620.106] (EE) 13: /usr/lib/Xorg (0x55fe84e6a000+0x3c83b) [0x55fe84ea683b]
[ 37620.106] (EE) 14: /usr/lib/libc.so.6 (__libc_start_main+0xd5) [0x7f74699ebb25]
[ 37620.106] (EE) 15: /usr/lib/Xorg (_start+0x2e) [0x55fe84ea775e]
[ 37620.106] (EE)
[ 37620.106] (EE) Segmentation fault at address 0x7ffecb23d000
[ 37620.106] (EE)
Fatal server error:
[ 37620.106] (EE) Caught signal 11 (Segmentation fault). Server aborting
Excuse my poor English.
Offline
Apologies for closing the bug thread (https://bugs.archlinux.org/task/72799) prematurely, hopefully someone will reopen it.
Offline
Apologies for closing the bug thread (https://bugs.archlinux.org/task/72799) prematurely, hopefully someone will reopen it.
It does not matter, this is an upstream bug anyways.
Excuse my poor English.
Offline
Still happening. Fortunately it doesn't happen on a daily basis, but it is quite inconvenient as it can cause you to lose your work at any time.
[ 312.170] (EE)
[ 312.170] (EE) Backtrace:
[ 312.170] (EE) 0: /usr/lib/Xorg (xorg_backtrace+0x89) [0x558576438049]
[ 312.170] (EE) 1: /usr/lib/Xorg (0x5585762e8000+0x15ae69) [0x558576442e69]
[ 312.170] (EE) 2: /usr/lib/libpthread.so.0 (0x7f675fc2e000+0x13870) [0x7f675fc41870]
[ 312.170] (EE) 3: /usr/lib/Xorg (0x5585762e8000+0x1e52d8) [0x5585764cd2d8]
[ 312.170] (EE) 4: /usr/lib/Xorg (0x5585762e8000+0x8d375) [0x558576375375]
[ 312.170] (EE) 5: /usr/lib/Xorg (0x5585762e8000+0x8d9bc) [0x5585763759bc]
[ 312.170] (EE) 6: /usr/lib/Xorg (0x5585762e8000+0x8ebb3) [0x558576376bb3]
[ 312.170] (EE) 7: /usr/lib/Xorg (0x5585762e8000+0x10cd4b) [0x5585763f4d4b]
[ 312.170] (EE) 8: /usr/lib/Xorg (XkbHandleActions+0x1d4) [0x55857642e7b4]
[ 312.170] (EE) 9: /usr/lib/Xorg (0x5585762e8000+0x1dcf12) [0x5585764c4f12]
[ 312.170] (EE) 10: /usr/lib/Xorg (0x5585762e8000+0x134c7e) [0x55857641cc7e]
[ 312.170] (EE) 11: /usr/lib/Xorg (0x5585762e8000+0x14e404) [0x558576436404]
[ 312.170] (EE) 12: /usr/lib/Xorg (WaitForSomething+0x2e2) [0x558576436712]
[ 312.170] (EE) 13: /usr/lib/Xorg (0x5585762e8000+0x3c83b) [0x55857632483b]
[ 312.170] (EE) 14: /usr/lib/libc.so.6 (__libc_start_main+0xd5) [0x7f675fa84b25]
[ 312.170] (EE) 15: /usr/lib/Xorg (_start+0x2e) [0x55857632575e]
[ 312.170] (EE)
[ 312.170] (EE) Segmentation fault at address 0x7ffdfde9d000
[ 312.170] (EE)
Fatal server error:
[ 312.170] (EE) Caught signal 11 (Segmentation fault). Server aborting
Excuse my poor English.
Offline
Well I'm unhappily joining the party of the ones affected. FWIW, Ryzen 5900HX, minipc. I use integrated Radeon card, symptoms are exactly the same. Funnily enough I see absolutely nothing about ACPI, it seems to be related purely to my inputs. It doesn't happen on Intel laptop that I also own and use extensively.
I noticed that on the AMD system there's much more of "client bug: event processing lagging behind" kind of logs, what would also indicate some issues w/ input processing. I'll try debug enabled build to see if something interesting pop up out of it.
Offline