Arch Linux

romch007

Member

From: France

Registered: 2023-02-08

Posts: 7

dbus-broker-launch crashing (Too many open files)

Hello,

dbus-broker-launch seems to be crashing and makes GNOME crash:

dbus-broker-launch[12498]: ERROR sockopt_get_peerpidfd @ ../dbus-broker-37/src/util/sockopt.c +244: Too many open files
dbus-broker-launch[12498]:       peer_new_with_fd @ ../dbus-broker-37/src/bus/peer.c +290
dbus-broker-launch[12498]:       listener_dispatch @ ../dbus-broker-37/src/bus/listener.c +54
dbus-broker-launch[12498]:       dispatch_context_dispatch @ ../dbus-broker-37/src/util/dispatch.c +344
dbus-broker-launch[12498]:       broker_run @ ../dbus-broker-37/src/broker/broker.c +209
systemd[3585]: Got disconnect on API bus.
kernel: rfkill: input handler enabled
gvfsd[12786]: A connection to the bus can't be made
firefox.desktop[16317]: [Parent 16317, Main Thread] WARNING: g_dbus_connection_unregister_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed: 'glib warning', file /usr/src/debug/firefox/firefox-147.0.3/toolkit/xre/nsSigHandlers.cpp:201
firefox.desktop[16317]: [Parent 16317, Main Thread] WARNING: nsDBusRemoteServer: Unable to unregister root object from within onNameLost!: 'glib warning', file /usr/src/debug/firefox/firefox-147.0.3/toolkit/xre/nsSigHandlers.cpp:201
firefox.desktop[16317]: [Parent 16317, Main Thread] WARNING: g_dbus_connection_unregister_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed: 'glib warning', file /usr/src/debug/firefox/firefox-147.0.3/toolkit/xre/nsSigHandlers.cpp:201
gdm-password][12273]: pam_unix(gdm-password:session): session closed for user romain
gnome-shell-calendar-server[12860]: gnome-shell-calendar-server[12860]: Lost (or failed to acquire) the name org.gnome.Shell.CalendarServer - exiting
dbus-broker[12836]: Dispatched 69 messages @ 6(±8)μs / message.
dbus-broker-launch[12498]:       run @ ../dbus-broker-37/src/broker/main.c +282
dbus-broker-launch[12498]:       main @ ../dbus-broker-37/src/broker/main.c +318
wireplumber[13059]: m-dbus-connection: <WpDBusConnection:0x5560c8b82630> DBus connection closed: Underlying GIOStream returned 0 bytes on an async read
dbus-broker-launch[12497]: ERROR launcher_run @ ../dbus-broker-37/src/launch/launcher.c +1476: Return code 1
dbus-broker-launch[12497]:       run @ ../dbus-broker-37/src/launch/main.c +152
systemd[1]: run-user-1000-gvfs.mount: Deactivated successfully.
gsd-media-keys[12888]: Failed to ungrab accelerators: The connection is closed
gsd-media-keys[12888]: g_hash_table_size: assertion 'hash_table != NULL' failed
wireplumber[13059]: m-dbus-connection: <WpDBusConnection:0x5560c8b82630> Trying to reconnect after core sync
firefox[16317]: g_dbus_connection_unregister_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
firefox[16317]: nsDBusRemoteServer: Unable to unregister root object from within onNameLost!
firefox[16317]: g_dbus_connection_unregister_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
systemd[1]: run-user-1000-doc.mount: Deactivated successfully.
dbus-broker[12498]: Dispatched 14114 messages @ 7(±11)μs / message.
dbus-broker-launch[12497]: Caught SIGCHLD of broker.
gnome-shell[12780]: Shutting down GNOME Shell
dbus-broker-launch[12497]:       main @ ../dbus-broker-37/src/launch/main.c +178
dbus-broker-launch[12497]: Exiting due to fatal error: -131

I read somewhere that it could be caused by an app doing too many D-Bus calls, but last time it crashed I was watching a video with mpv with nothing significant running in the background. Other crashes have happened while browsing the web in Firefox.

How can I debug that?

dimich

Member

From: Kharkiv, Ukraine

Registered: 2009-11-03

Posts: 474

Re: dbus-broker-launch crashing (Too many open files)

I read somewhere that it could be caused by an app doing too many D-Bus calls

Many calls should not cause such error. Many simoulaneous connections can. Or connections leakage in one of clients or descriptor leakage in dbus-broker-launch itself.

Get main PID of the service with

$ systemctl --user show --property='MainPID' dbus-broker.service

and check number of opened descriptors:

$ find /proc/PID/fd/ -type l | wc -l

(replace "PID" with real MainPID value).
Does this number grow significantly during casual activity?

How can I debug that?

Check unique peers on user bus with

$ busctl --user --unique

Does this list grow?
Also you can monitor dbus events with

$ busctl --user monitor

and look for suspicious dbus activity.

Last edited by dimich (2026-02-17 02:02:04)