[SOLVED] Irregular crashes on two different arch installs

Amicar · 2024-03-06 20:51:57

On my laptop (X1 Carbon Gen 7) and desktop (Ryzen 3600, 32gb RAM, Nvidia 2070 Super), I'm getting infrequent but regular and total crashes. Here is a log from one last week, included here as it pinpoints the exact time the crash happened, at 11:29 (as soon as I opened my laptop after coming back from a break):

https://pastebin.com/h9eRhB8v

When the crash happens, the screen turns black; on the laptop, around 20 @ symbols appear top left. On the desktop, a blinking underscore cursor _ appears. After a minute or so, I'm returned to the Gnome login screen. The device has essentially restarted.

With my current knowledge I'm not able to read into these error messages, but this section stood out, not least because it was highlighted in red by journalctl:

Feb 29 11:29:41 archlinux systemd-coredump[65197]: [?] Process 23262 (signal-desktop) of user 1000 dumped core.

What can I do with these messages to start pinpointing the issue?

Last edited by Amicar (2024-03-15 11:27:11)

seth · 2024-03-06 23:08:09

The device has essentially restarted.

No, your session crashed. The system didn't reboot.
The "@" reflect null, this is likely some spurious input and unrelated.
Things go down with

Feb 29 11:29:39 archlinux dbus-broker-launch[1199]: ERROR sockopt_get_peerpidfd @ ../dbus-broker-35/src/util/sockopt.c +244: Too many open files
Feb 29 11:29:39 archlinux dbus-broker-launch[1199]:       peer_new_with_fd @ ../dbus-broker-35/src/bus/peer.c +290
Feb 29 11:29:39 archlinux dbus-broker-launch[1199]:       listener_dispatch @ ../dbus-broker-35/src/bus/listener.c +54
Feb 29 11:29:39 archlinux dbus-broker-launch[1199]:       dispatch_context_dispatch @ ../dbus-broker-35/src/util/dispatch.c +344
Feb 29 11:29:39 archlinux dbus-broker-launch[1199]:       broker_run @ ../dbus-broker-35/src/broker/broker.c +229
Feb 29 11:29:39 archlinux gvfsd[1326]: A connection to the bus can't be made
Feb 29 11:29:39 archlinux gnome-shell[1318]: Lost or failed to acquire name org.gnome.Mutter.ServiceChannel

leading up to

Feb 29 11:29:39 archlinux gnome-shell[1318]: Shutting down GNOME Shell
Feb 29 11:29:39 archlinux dbus-broker-launch[1198]: Caught SIGCHLD of broker.
…
Feb 29 11:29:40 archlinux dbus-broker-launch[1198]: Exiting due to fatal error: -131

Is an S3 a necessary precondition for the crash?
Try to replace dbus-broker-units w/ dbus-daemon-units (and reboot) and see whether the system becomes stable.

However, dbus-broker might indeed just be the messenger.
https://unix.stackexchange.com/question … iles-issue

Any idea what might be leaking file handles?

Amicar · 2024-03-09 13:49:20

Thank you and please excuse the slow response - these crashes are regular but not frequent, so it's taking a bit of time to look into them.

I tried dbus-daemon-units on both devices, system instability massively decreased [EDIT! this should have read "massively increased"]. My first guess was that VirtualBox (used for MS Word and translation software like MemoQ) could be leaking file handles, but its logs look clean.
I'm not sure what you mean by S3 and googling didn't help - could you elaborate so I can look into that?

The crash just happened again (https://pastebin.com/mJeMP49R), I'm beginning to suspect Signal Desktop messenger could be the culprit, given the output of journalctl here: https://pastebin.com/h7ZQD4NW

Last edited by Amicar (2024-03-09 15:13:06)

seth · 2024-03-09 14:22:39

Mar 09 14:20:42 archlinux dbus-broker-launch[1189]: Caught SIGCHLD of broker.
Mar 09 14:20:42 archlinux dbus-broker-launch[1189]:       run @ ../dbus-broker-35/src/launch/main.c +152
Mar 09 14:20:42 archlinux dbus-broker-launch[1189]: ERROR launcher_run @ ../dbus-broker-35/src/launch/launcher.c +1453: Return code 1

That's with dbus-broker again, though?

system instability massively decreased

Erronous double negation?
Dod dbus-daemon-units make it better or worse? If better, did you return to dbus-broker to analyze the situation or did you accidentally re-install it?

signal crashes after dbus-broker (and a bunch of other processes exit uncleanly as well), don't use -r

Mar 09 14:19:54 archlinux kernel: usb 4-2: Product: Pixel 8 ProMar 09 14:19:54 archlinux kernel: usb 4-2: Manufacturer: Google
Mar 09 14:19:54 archlinux kernel: usb 4-2: SerialNumber: 38151FDJG00F7M
Mar 09 14:19:54 archlinux kernel: usb 4-2: can't set config #1, error -32
Mar 09 14:19:54 archlinux kernel: usb 4-2: USB disconnect, device number 6
Mar 09 14:19:54 archlinux boltd[548]: probing: started [1000]
                                             #2   5c7255efb178 i   resource:///org/gnome/shell/ui/init.js:21 (11ba16f70ba0 @ 48)
                                             #1   5c7255efb208 i   resource:///org/gnome/shell/ui/components/automountManager.js:187 (2ddd8d8e0830 @ 20)
                                             #0   7ffc41fc7fc0 b   resource:///org/gnome/shell/ui/components/automountManager.js:251 (2ddd8d8e09c0 @ 69)
                                             == Stack trace for context 0x5c7255e33520 ==
y the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
Mar 09 14:19:54 archlinux gnome-shell[1309]: Object .GProxyVolume (0x5c72569a3720), has been already disposed — impossible to add toggle reference on it. This might be caused b
                                             #1   5c7255efb178 i   resource:///org/gnome/shell/ui/init.js:21 (11ba16f70ba0 @ 48)
                                             #0   5c7255efb208 i   resource:///org/gnome/shell/ui/components/automountManager.js:190 (2ddd8d8e0830 @ 38)
                                             == Stack trace for context 0x5c7255e33520 ==
ng been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
Mar 09 14:19:54 archlinux gnome-shell[1309]: Object .GProxyVolume (0x5c72569a3720), has been already disposed — impossible to access it. This might be caused by the object havi
                                             #1   5c7255efb178 i   resource:///org/gnome/shell/ui/init.js:21 (11ba16f70ba0 @ 48)
                                             #0   5c7255efb208 i   resource:///org/gnome/shell/ui/components/automountManager.js:212 (2ddd8d8e0830 @ 414)
                                             == Stack trace for context 0x5c7255e33520 ==
ng been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
Mar 09 14:19:54 archlinux gnome-shell[1309]: Object .GProxyVolume (0x5c72569a3720), has been already disposed — impossible to access it. This might be caused by the object havi
Mar 09 14:19:54 archlinux gnome-shell[1309]: Unable to mount volume Google Pixel 8 Pro: Gio.IOErrorEnum: Couldn’t find matching udev device.
Mar 09 14:19:56 archlinux boltd[548]: probing: timeout, done: [2002544] (2000000)
                                             #1   5c7255efb178 i   resource:///org/gnome/shell/ui/init.js:21 (11ba16f70ba0 @ 48)
                                             #0   7ffc41fc8a90 b   resource:///org/gnome/shell/ui/components/automountManager.js:247 (2ddd8d8e0a10 @ 6)
                                             == Stack trace for context 0x5c7255e33520 ==
y the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
Mar 09 14:20:04 archlinux gnome-shell[1309]: Object .GProxyVolume (0x5c72569a3720), has been already disposed — impossible to add toggle reference on it. This might be caused b
Mar 09 14:20:08 archlinux kernel: usb usb4-port2: attempt power cycle
Mar 09 14:20:28 archlinux gnome-shell[1309]: invalid (NULL) pointer instance
Mar 09 14:20:28 archlinux gnome-shell[1309]: g_signal_handler_disconnect: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Mar 09 14:20:28 archlinux gnome-shell[1309]: invalid (NULL) pointer instance
Mar 09 14:20:28 archlinux gnome-shell[1309]: g_signal_handler_disconnect: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Mar 09 14:20:30 archlinux rtkit-daemon[1020]: Supervising 9 threads of 6 processes of 1 users.
Mar 09 14:20:30 archlinux rtkit-daemon[1020]: Supervising 9 threads of 6 processes of 1 users.
Mar 09 14:20:37 archlinux rtkit-daemon[1020]: Supervising 9 threads of 6 processes of 1 users.
Mar 09 14:20:37 archlinux rtkit-daemon[1020]: Supervising 9 threads of 6 processes of 1 users.
Mar 09 14:20:42 archlinux dbus-broker-launch[1190]: ERROR sockopt_get_peerpidfd @ ../dbus-broker-35/src/util/sockopt.c +244: Too many open files
Mar 09 14:20:42 archlinux dbus-broker-launch[1190]:       peer_new_with_fd @ ../dbus-broker-35/src/bus/peer.c +290
Mar 09 14:20:42 archlinux dbus-broker-launch[1190]:       listener_dispatch @ ../dbus-broker-35/src/bus/listener.c +54
Mar 09 14:20:42 archlinux dbus-broker-launch[1190]:       dispatch_context_dispatch @ ../dbus-broker-35/src/util/dispatch.c +344
Mar 09 14:20:42 archlinux dbus-broker-launch[1190]:       broker_run @ ../dbus-broker-35/src/broker/broker.c +229
Mar 09 14:20:42 archlinux gvfsd[1319]: A connection to the bus can't be made
Mar 09 14:20:42 archlinux dbus-broker[1400]: Dispatched 26364 messages @ 2(±2)μs / message.
Mar 09 14:20:42 archlinux gnome-shell-calendar-server[1407]: gnome-shell-calendar-server[1407]: Lost (or failed to acquire) the name org.gnome.Shell.CalendarServer - exiting
Mar 09 14:20:42 archlinux gnome-shell[1309]: Lost or failed to acquire name org.gnome.Mutter.ServiceChannel
Mar 09 14:20:42 archlinux kernel: rfkill: input handler enabled
Mar 09 14:20:42 archlinux Nextcloud.desktop[1587]: ICE default IO error handler doing an exit(), pid = 1587, errno = 22
Mar 09 14:20:42 archlinux org.musicbrainz.Picard.desktop[21777]: ICE default IO error handler doing an exit(), pid = 21777, errno = 2
Mar 09 14:20:42 archlinux virtualbox.desktop[4684]: ICE default IO error handler doing an exit(), pid = 4684, errno = 0

Shit hits the fan w/

Mar 09 14:20:42 archlinux dbus-broker-launch[1190]: ERROR sockopt_get_peerpidfd @ ../dbus-broker-35/src/util/sockopt.c +244: Too many open files

https://www.google.com/search?q=%22dbus … 20files%22 has some hits
No idea whether this is b/c of

Mar 09 14:20:28 archlinux gnome-shell[1309]: g_signal_handler_disconnect: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Mar 09 14:20:28 archlinux gnome-shell[1309]: invalid (NULL) pointer instance
Mar 09 14:20:28 archlinux gnome-shell[1309]: g_signal_handler_disconnect: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Mar 09 14:20:28 archlinux gnome-shell[1309]: invalid (NULL) pointer instance

but if theproblem doesn't exist w/ dbus-daemon, it's more likely a dbus-broker bug.

Amicar · 2024-03-14 14:23:01

You were right, that was a typo - dbus-daemon-units initially made things worse. But I might just have had bad luck, as the next time I ran pacman -Syu another package was replaced with an alternative. (I didn't not down which). And the system became unusable, so I revered back to dbus-broker.

But after another crash I decided to try dbus-daemon-units again. I left it a few days to see if there were any further crashes - there have been none so far. Thanks!

seth · 2024-03-14 15:12:37

You can probalby also remove dbus-broker
=> https://github.com/bus1/dbus-broker/issues (I can't find any related bugs there)
The journanal for a run w/o dbus-broker might highlight issues that dbus-broker then trips over.

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Arch Linux

#1 2024-03-06 20:51:57

[SOLVED] Irregular crashes on two different arch installs

#2 2024-03-06 23:08:09

Re: [SOLVED] Irregular crashes on two different arch installs

#3 2024-03-09 13:49:20

Re: [SOLVED] Irregular crashes on two different arch installs

#4 2024-03-09 14:22:39

Re: [SOLVED] Irregular crashes on two different arch installs

#5 2024-03-14 14:23:01

Re: [SOLVED] Irregular crashes on two different arch installs

#6 2024-03-14 15:12:37

Re: [SOLVED] Irregular crashes on two different arch installs

Board footer