dbus-broker.service: Exiting due to fatal error: -2

arc891 · 2024-05-01 15:03:28

Hi all, first time-poster here, medium Linux/Arch-noob, been working with Linux full-time for the past 3 years, Arch for about half a year.
I am very lost and have not been able to find anything useful relating to my specific issue.

Quick system info:

OS: Arch Linux x86_64 
Host: 21K7CTO1WW ThinkPad T16 Gen 2 
Kernel: 6.8.8-arch1-1
Shell: zsh 5.9
DE: Hyprland
CPU: AMD Ryzen 7 PRO 7840U w/ Radeon 780M Graphics (16) @ 5.289GHz 
GPU: AMD ATI 64:00.0 Phoenix1 
Memory: 792MiB / 30784MiB

Since yesterday, after a quick reboot (I had done multiple while working on some project including swaylock) and not much (to my knowledge) impactful changes made to my system, suddenly my Waybar didn't start on login, and when attempting to start it manually, gave me the short error of:

[2024-05-01 16:14:34.127] [info] Using configuration file /home/user/.config/waybar/config.jsonc
[2024-05-01 16:14:34.128] [error] Could not connect: Connection refused

After some more digging, I found multiple processes not starting up and giving errors about the D-Bus User Message Bus.

journalctl -b
May 01 15:51:34 arch systemd[1750]: pulseaudio.service: Scheduled restart job, restart counter is at 4.
May 01 15:51:34 arch systemd[1750]: Starting Sound Service...
May 01 15:51:34 arch rtkit-daemon[1774]: Successfully made thread 1799 of process 1799 owned by '1001' high priority at nice level -11.
May 01 15:51:34 arch rtkit-daemon[1774]: Supervising 1 threads of 1 processes of 1 users.
May 01 15:51:34 arch pulseaudio[1799]: Failed to create secure directory (/run/user/$(id -u)/pulse): No such file or directory
May 01 15:51:34 arch systemd[1750]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE
May 01 15:51:34 arch systemd[1750]: pulseaudio.service: Failed with result 'exit-code'.
May 01 15:51:34 arch systemd[1750]: Failed to start Sound Service.
May 01 15:51:34 arch NetworkManager[1336]: <info>  [1714571494.7693] dhcp6 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
May 01 15:51:34 arch NetworkManager[1336]: <info>  [1714571494.7857] dhcp6 (wlp2s0): state changed new lease
May 01 15:51:34 arch systemd[1750]: Starting D-Bus User Message Bus...
May 01 15:51:34 arch systemd[1]: Starting Network Manager Script Dispatcher Service...
May 01 15:51:34 arch dbus-broker-launch[1821]: Service file '/usr/share/dbus-1/services/org.knopwob.dunst.service' is not named after the D-Bus name 'org.freedesktop.Notifications'.
May 01 15:51:34 arch dbus-broker-launch[1821]: Service file '/usr/share/dbus-1/services/org.xfce.Thunar.FileManager1.service' is not named after the D-Bus name 'org.freedesktop.FileManager>
May 01 15:51:34 arch dbus-broker-launch[1821]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +31: Eavesdropping is deprecated and ignored
May 01 15:51:34 arch dbus-broker-launch[1821]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +33: Eavesdropping is deprecated and ignored
May 01 15:51:34 arch systemd[1750]: Started D-Bus User Message Bus.
May 01 15:51:34 arch dbus-broker-launch[1821]: ERROR launcher_connect @ ../dbus-broker-36/src/launch/launcher.c +1253: No such file or directory
May 01 15:51:34 arch dbus-broker-launch[1821]:       launcher_run @ ../dbus-broker-36/src/launch/launcher.c +1424
May 01 15:51:34 arch dbus-broker-launch[1821]:       run @ ../dbus-broker-36/src/launch/main.c +152
May 01 15:51:34 arch dbus-broker[1825]: Dispatched 4 messages @ 9(±3)μs / message.
May 01 15:51:34 arch dbus-broker-launch[1821]:       main @ ../dbus-broker-36/src/launch/main.c +178
May 01 15:51:34 arch dbus-broker-launch[1821]: Exiting due to fatal error: -2
May 01 15:51:34 arch systemd[1750]: dbus-broker.service: Main process exited, code=exited, status=1/FAILURE
May 01 15:51:34 arch systemd[1750]: dbus-broker.service: Failed with result 'exit-code'.

This is the output of 'systemctl --user status dbus.service':

× dbus-broker.service - D-Bus User Message Bus
     Loaded: loaded (/usr/lib/systemd/user/dbus-broker.service; static)
     Active: failed (Result: exit-code) since Wed 2024-05-01 15:55:06 CEST; 25min ago
   Duration: 18ms
TriggeredBy: × dbus.socket
       Docs: man:dbus-broker-launch(1)
    Process: 3124 ExecStart=/usr/bin/dbus-broker-launch --scope user (code=exited, status=1/FAILURE)
   Main PID: 3124 (code=exited, status=1/FAILURE)
        CPU: 8ms

May 01 15:55:06 arch dbus-broker-launch[3124]:       launcher_run @ ../dbus-broker-36/src/launch/launcher.c +1424
May 01 15:55:06 arch dbus-broker-launch[3124]:       run @ ../dbus-broker-36/src/launch/main.c +152
May 01 15:55:06 arch dbus-broker-launch[3124]:       main @ ../dbus-broker-36/src/launch/main.c +178
May 01 15:55:06 arch dbus-broker-launch[3124]: Exiting due to fatal error: -2
May 01 15:55:06 arch dbus-broker[3125]: Dispatched 14 messages @ 6(±4)μs / message.
May 01 15:55:06 arch systemd[1750]: dbus-broker.service: Main process exited, code=exited, status=1/FAILURE
May 01 15:55:06 arch systemd[1750]: dbus-broker.service: Failed with result 'exit-code'.
May 01 15:55:11 arch systemd[1750]: dbus-broker.service: Start request repeated too quickly.
May 01 15:55:11 arch systemd[1750]: dbus-broker.service: Failed with result 'exit-code'.
May 01 15:55:11 arch systemd[1750]: Failed to start D-Bus User Message Bus.

I have since tried:

Starting dbus.service and dbus_broker.service manually
Checking for any upgraded packages that could be the cause, and downgrading them (including kernel to 6.8.7-arch1-1, 6.8.8-arch-1-1 version I installed just slightly after the issues started, but gave it a try)
Installing dbus-daemon-units instead of dbus-broker-units

The dbus-daemon-units at least made some things work again, like waybar, however they would take ages to start up (solid 2 minutes for waybar, didn't have the patience to wait for chromium to become visible after trying to start it multiple times), so this didn't fix anything either.

I have looked through dbus source code, trying to fin the mentioned lines, but nothing more came up than a function I couldn't find the definition of, named sd_bus_open_user(), but checks out.

Sadly, I had not been committed enough to make myself a good backup routine for my arch install, so freshly installing would require me to make these backups this after the fact.

Any help would be greatly appreciated!

seth · 2024-05-01 15:48:28

May 01 15:51:34 arch pulseaudio[1799]: Failed to create secure directory (/run/user/$(id -u)/pulse): No such file or directory

id
ls -lR /run/user
mount | grep run

arc891 · 2024-05-01 15:57:10

$ id
uid=1001(arc) gid=1001(arc) groups=1001(arc),108(vboxusers),965(plugdev),998(wheel)

$ ls -lR /run/user
drwx------ - arc  1 May 17:50  1001

/run/user/1001:
drwx------ - arc  1 May 16:42  dconf
drwx------ - arc  1 May 16:42  gcr
drwx------ - arc  1 May 16:42  gnupg
drwx------ - arc  1 May 16:42  keyring
drwxr-xr-x - arc  1 May 16:42  p11-kit
drwxr-xr-x - arc  1 May 16:42  polychromatic
drwx------ - arc  1 May 16:42  pulse
drwxr-xr-x - arc  1 May 17:08  systemd
srw-rw-rw- - arc  1 May 16:42  bus
.rw-r--r-- 0 root     1 May 17:16  pam-u2f-authpending
srwxr-xr-x - arc  1 May 16:42  swww-wayland-1.socket
srwxr-xr-x - arc  1 May 16:42  wayland-1
.rw-r----- 0 arc  1 May 16:42  wayland-1.lock

/run/user/1001/dconf:
.rw------- 2 arc  1 May 16:43  user

/run/user/1001/gcr:
srw-rw-rw- - arc  1 May 16:42  ssh

/run/user/1001/gnupg:
srw------- - arc  1 May 16:42  S.dirmngr
srw------- - arc  1 May 16:42  S.gpg-agent
srw------- - arc  1 May 16:42  S.gpg-agent.browser
srw------- - arc  1 May 16:42  S.gpg-agent.extra
srw------- - arc  1 May 16:42  S.gpg-agent.ssh
srw------- - arc  1 May 16:42  S.keyboxd

/run/user/1001/keyring:
srw-rw-rw- - arc  1 May 16:42  control
srwxr-xr-x - arc  1 May 16:42  pkcs11

/run/user/1001/p11-kit:
srw------- - arc  1 May 16:42  pkcs11

/run/user/1001/polychromatic:
.rw-r--r-- 4 arc  1 May 16:42  tray-applet.pid

/run/user/1001/pulse:
srw-rw-rw- - arc  1 May 16:42  native

/run/user/1001/systemd:
drwxr-xr-x - arc  1 May 17:08  generator.late
drwxr-xr-x - arc  1 May 16:42  inaccessible
drwxr-xr-x - arc  1 May 16:42  propagate
drwxr-xr-x - arc  1 May 16:42  units
srwxr-xr-x - arc  1 May 16:42  notify
srwx------ - arc  1 May 16:42  private

/run/user/1001/systemd/generator.late:
drwxr-xr-x   - arc  1 May 17:08  xdg-desktop-autostart.target.wants
.rw-r--r-- 578 arc  1 May 17:08  app-at\x2dspi\x2ddbus\x2dbus@autostart.service
.rw-r--r-- 376 arc  1 May 17:08  app-blueman@autostart.service
.rw-r--r-- 474 arc  1 May 17:08  app-geoclue\x2ddemo\x2dagent@autostart.service
.rw-r--r-- 529 arc  1 May 17:08  app-gnome\x2dkeyring\x2dpkcs11@autostart.service
.rw-r--r-- 526 arc  1 May 17:08  app-gnome\x2dkeyring\x2dsecrets@autostart.service
.rw-r--r-- 509 arc  1 May 17:08  app-gnome\x2dkeyring\x2dssh@autostart.service
.rw-r--r-- 458 arc  1 May 17:08  app-nm\x2dapplet@autostart.service
.rw-r--r-- 544 arc  1 May 17:08  app-org.gnome.SettingsDaemon.DiskUtilityNotify@autostart.service
.rw-r--r-- 419 arc  1 May 17:08  app-polychromatic\x2dautostart@autostart.service
.rw-r--r-- 468 arc  1 May 17:08  app-pulseaudio@autostart.service
.rw-r--r-- 448 arc  1 May 17:08  app-RQuickShare@autostart.service
.rw-r--r-- 456 arc  1 May 17:08  app-xfsettingsd@autostart.service

/run/user/1001/systemd/generator.late/xdg-desktop-autostart.target.wants:
lrwxrwxrwx - arc  1 May 17:08  app-at\x2dspi\x2ddbus\x2dbus@autostart.service -> ../app-at\x2dspi\x2ddbus\x2dbus@autostart.service
lrwxrwxrwx - arc  1 May 17:08  app-blueman@autostart.service -> ../app-blueman@autostart.service
lrwxrwxrwx - arc  1 May 17:08  app-geoclue\x2ddemo\x2dagent@autostart.service -> ../app-geoclue\x2ddemo\x2dagent@autostart.service
lrwxrwxrwx - arc  1 May 17:08  app-gnome\x2dkeyring\x2dpkcs11@autostart.service -> ../app-gnome\x2dkeyring\x2dpkcs11@autostart.service
lrwxrwxrwx - arc  1 May 17:08  app-gnome\x2dkeyring\x2dsecrets@autostart.service -> ../app-gnome\x2dkeyring\x2dsecrets@autostart.service
lrwxrwxrwx - arc  1 May 17:08  app-gnome\x2dkeyring\x2dssh@autostart.service -> ../app-gnome\x2dkeyring\x2dssh@autostart.service
lrwxrwxrwx - arc  1 May 17:08  app-nm\x2dapplet@autostart.service -> ../app-nm\x2dapplet@autostart.service
lrwxrwxrwx - arc  1 May 17:08  app-org.gnome.SettingsDaemon.DiskUtilityNotify@autostart.service -> ../app-org.gnome.SettingsDaemon.DiskUtilityNotify@autostart.service
lrwxrwxrwx - arc  1 May 17:08  app-polychromatic\x2dautostart@autostart.service -> ../app-polychromatic\x2dautostart@autostart.service
lrwxrwxrwx - arc  1 May 17:08  app-pulseaudio@autostart.service -> ../app-pulseaudio@autostart.service
lrwxrwxrwx - arc  1 May 17:08  app-RQuickShare@autostart.service -> ../app-RQuickShare@autostart.service
lrwxrwxrwx - arc  1 May 17:08  app-xfsettingsd@autostart.service -> ../app-xfsettingsd@autostart.service

/run/user/1001/systemd/inaccessible:
/run/user/1001/systemd/inaccessible/dir: Permission denied (os error 13)
d---------   - arc  1 May 16:42  dir
c--------- 0,0 arc  1 May 16:42  chr
|---------   - arc  1 May 16:42  fifo
.---------   0 arc  1 May 16:42  reg
s---------   - arc  1 May 16:42  sock

/run/user/1001/systemd/propagate:

/run/user/1001/systemd/units:
lrwxrwxrwx - arc  1 May 16:42  invocation:gcr-ssh-agent.socket -> 360e5f6c61b349b68b6a059185fd3862
lrwxrwxrwx - arc  1 May 16:42  invocation:gnome-keyring-daemon.service -> 7e054aad771b46e38e643329d3435474

$ mount | grep run
run on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755,inode64)
tmpfs on /run/user/1001 type tmpfs (rw,nosuid,nodev,relatime,size=3152296k,nr_inodes=788074,mode=700,uid=1001,gid=1001,inode64)

seth · 2024-05-01 16:13:09

Just to be sure

stat /run/user/1001

but the the output contracts equal uid and gid, this looks unsuspicious - pulse probably just runs w/ the UID of the pulse user?

Please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

Ftr, the failure is https://github.com/bus1/dbus-broker/blo … er.c#L1422 => https://github.com/bus1/dbus-broker/blo … er.c#L1251 and -2 is ENOENT

arc891 · 2024-05-01 16:26:33

seth wrote:

Just to be sure
stat /run/user/1001
but the the output contracts equal uid and gid, this looks unsuspicious - pulse probably just runs w/ the UID of the pulse user?
Please post your complete system journal for the boot:
sudo journalctl -b | curl -F 'file=@-' 0x0.st
Ftr, the failure is https://github.com/bus1/dbus-broker/blo … er.c#L1422 => https://github.com/bus1/dbus-broker/blo … er.c#L1251 and -2 is ENOENT

Yes I thought the pulse error was a weird one too, but here you go:

$ stat /run/user/1001
  File: /run/user/1001
  Size: 360       	Blocks: 0          IO Block: 4096   directory
Device: 0,52	Inode: 1           Links: 10
Access: (0700/drwx------)  Uid: ( 1001/ arc)   Gid: ( 1001/ arc)
Access: 2024-05-01 18:16:01.453637203 +0200
Modify: 2024-05-01 18:00:01.967604530 +0200
Change: 2024-05-01 18:00:01.967604530 +0200
 Birth: 2024-05-01 16:42:17.176205775 +0200

As for the system journal: https://0x0.st/XXbW.txt (edited link)

There's some clutter in there from some bad script I have running for my swww backgrounds.

And ah yeah, that ENOENT makes sense looking at the error message. Interesting.

Last edited by arc891 (2024-05-01 16:31:04)

seth · 2024-05-01 16:35:19

May 01 16:42:10 arch dbus-broker-launch[1098]: Looking up NSS user entry for 'pulse'...
May 01 16:42:10 arch dbus-broker-launch[1098]: NSS returned no entry for 'pulse'
May 01 16:42:10 arch dbus-broker-launch[1098]: Invalid user-name in /usr/share/dbus-1/system.d/pulseaudio-system.conf +27: user="pulse"
May 01 16:42:11 arch dbus-broker-launch[1098]: Ready
May 01 16:42:11 arch boltd[1164]: watchdog: enabled [pulse: 90s]
May 01 16:42:11 arch systemd[1]: Starting pulsesecure service Daemon...
May 01 16:42:11 arch root[1233]: pulsesecure started successfully !!
May 01 16:42:11 arch systemd[1]: Started pulsesecure service Daemon.
May 01 16:42:14 arch dbus-broker-launch[1098]: Activation request for 'org.freedesktop.home1' failed: The systemd unit 'dbus-org.freedesktop.home1.service' could not be found.
May 01 16:42:14 arch dbus-broker-launch[1310]: Service file '/usr/share/dbus-1/services/org.knopwob.dunst.service' is not named after the D-Bus name 'org.freedesktop.Notifications'.
May 01 16:42:14 arch dbus-broker-launch[1310]: Service file '/usr/share/dbus-1/services/org.xfce.Thunar.FileManager1.service' is not named after the D-Bus name 'org.freedesktop.FileManager1'.
May 01 16:42:14 arch dbus-broker-launch[1310]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +31: Eavesdropping is deprecated and ignored
May 01 16:42:14 arch dbus-broker-launch[1310]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +33: Eavesdropping is deprecated and ignored
May 01 16:42:14 arch dbus-broker-launch[1310]: Ready
May 01 16:42:17 arch pulseaudio[1362]: Failed to create secure directory (/run/user/$(id -u)/pulse): No such file or directory
May 01 16:42:17 arch systemd[1348]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE
May 01 16:42:17 arch systemd[1348]: pulseaudio.service: Failed with result 'exit-code'.
May 01 16:42:17 arch systemd[1348]: pulseaudio.service: Scheduled restart job, restart counter is at 1.
May 01 16:42:17 arch pulseaudio[1376]: Failed to create secure directory (/run/user/$(id -u)/pulse): No such file or directory
May 01 16:42:17 arch systemd[1348]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE
May 01 16:42:17 arch systemd[1348]: pulseaudio.service: Failed with result 'exit-code'.
May 01 16:42:18 arch systemd[1348]: pulseaudio.service: Scheduled restart job, restart counter is at 2.
May 01 16:42:18 arch pulseaudio[1388]: Failed to create secure directory (/run/user/$(id -u)/pulse): No such file or directory
May 01 16:42:18 arch systemd[1348]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE
May 01 16:42:18 arch systemd[1348]: pulseaudio.service: Failed with result 'exit-code'.
May 01 16:42:18 arch systemd[1348]: pulseaudio.service: Scheduled restart job, restart counter is at 3.
May 01 16:42:18 arch pulseaudio[1397]: Failed to create secure directory (/run/user/$(id -u)/pulse): No such file or directory
May 01 16:42:18 arch systemd[1348]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE
May 01 16:42:18 arch systemd[1348]: pulseaudio.service: Failed with result 'exit-code'.
May 01 16:42:18 arch dbus-broker-launch[1420]: Service file '/usr/share/dbus-1/services/org.knopwob.dunst.service' is not named after the D-Bus name 'org.freedesktop.Notifications'.
May 01 16:42:18 arch dbus-broker-launch[1420]: Service file '/usr/share/dbus-1/services/org.xfce.Thunar.FileManager1.service' is not named after the D-Bus name 'org.freedesktop.FileManager1'.
May 01 16:42:18 arch dbus-broker-launch[1420]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +31: Eavesdropping is deprecated and ignored
May 01 16:42:18 arch dbus-broker-launch[1420]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +33: Eavesdropping is deprecated and ignored
May 01 16:42:18 arch dbus-broker-launch[1420]: ERROR launcher_connect @ ../dbus-broker-36/src/launch/launcher.c +1253: No such file or directory
May 01 16:42:18 arch dbus-broker-launch[1420]:       launcher_run @ ../dbus-broker-36/src/launch/launcher.c +1424
May 01 16:42:18 arch dbus-broker-launch[1420]:       run @ ../dbus-broker-36/src/launch/main.c +152
May 01 16:42:18 arch dbus-broker-launch[1420]:       main @ ../dbus-broker-36/src/launch/main.c +178
May 01 16:42:18 arch dbus-broker-launch[1420]: Exiting due to fatal error: -2
May 01 16:42:18 arch systemd[1348]: pulseaudio.service: Scheduled restart job, restart counter is at 4.

What if you replace pulsesecure w/ the regular pulseadio?

arc891 · 2024-05-01 16:44:32

seth wrote:

What if you replace pulsesecure w/ the regular pulseadio?

Ah, Pulsesecure is a VPN I have for work (hence some redaction of usernames going on). I just have normal pulseaudio installed, however I did have some issues with it a while back by installing pipewire and wanting to switch back, not sure if related.
Do you think that the PulseSecure package is the issue at hand? I personally don't see too much correlation of issues between it and pulseaudio, but it does make the various uses of "pulse" very confusing.

seth · 2024-05-01 21:22:32

No, pulseaudio is probably just another indicator:

May 01 16:42:17 arch systemctl[1357]: Failed to connect to bus: No such file or directory
May 01 16:42:17 arch systemctl[1356]: Failed to connect to bus: No such file or directory
May 01 16:42:17 arch mpris-proxy[1360]: Can't get on session bus
May 01 16:42:17 arch systemd[1348]: mpris-proxy.service: Main process exited, code=exited, status=1/FAILURE
May 01 16:42:17 arch systemd[1348]: mpris-proxy.service: Failed with result 'exit-code'.
May 01 16:42:17 arch pulseaudio[1362]: Failed to create secure directory (/run/user/$(id -u)/pulse): No such file or directory

printenv

Can you login properly into a fresh user account?

arc891 · 2024-05-01 22:22:42

seth wrote:

No, pulseaudio is probably just another indicator:

May 01 16:42:17 arch systemctl[1357]: Failed to connect to bus: No such file or directory
May 01 16:42:17 arch systemctl[1356]: Failed to connect to bus: No such file or directory
May 01 16:42:17 arch mpris-proxy[1360]: Can't get on session bus
May 01 16:42:17 arch systemd[1348]: mpris-proxy.service: Main process exited, code=exited, status=1/FAILURE
May 01 16:42:17 arch systemd[1348]: mpris-proxy.service: Failed with result 'exit-code'.
May 01 16:42:17 arch pulseaudio[1362]: Failed to create secure directory (/run/user/$(id -u)/pulse): No such file or directory

printenv

Can you login properly into a fresh user account?

That makes sense.

For the printenv, quickly ran it after having made the new user account from starting up a new Hyprland session from tty3, but should still be representable:

$ printenv
SHELL=/usr/bin/zsh
HYPRLAND_CMD=Hyprland
XDG_BACKEND=wayland
_P9K_TTY=/dev/pts/3
SSH_AUTH_SOCK=/run/user/1001/gcr/ssh
CREDENTIALS_DIRECTORY=/run/credentials/getty@tty3.service
P9K_TTY=old
MEMORY_PRESSURE_WRITE=c29tZSAyMDAwMDAgMjAwMDAwMAA=
EDITOR=nvim
XDG_SEAT=seat0
PWD=/home/arc
LOGNAME=arc
XDG_SESSION_DESKTOP=Hyprland
XDG_SESSION_TYPE=wayland
SYSTEMD_EXEC_PID=3437
WLR_EGL_NO_MODIFIERS=1
MOTD_SHOWN=pam
HOME=/home/arc
LANG=en_US.UTF-8
_JAVA_AWT_WM_NONREPARENTING=1
NVCC_PREPEND_FLAGS=-ccbin /opt/cuda/bin
XDG_CURRENT_DESKTOP=Hyprland
MEMORY_PRESSURE_WATCH=/sys/fs/cgroup/system.slice/system-getty.slice/getty@tty3.service/memory.pressure
WAYLAND_DISPLAY=wayland-1
INVOCATION_ID=3f194e76bb174357b4c3c260b896ac5d
XDG_SESSION_CLASS=user
TERM=xterm-kitty
USER=arc
CUDA_PATH=/opt/cuda
HYPRLAND_INSTANCE_SIGNATURE=fe7b748eb668136dd0558b7c8279bfcd7ab4d759_1714601062
DISPLAY=:2
SHLVL=2
MOZ_ENABLE_WAYLAND=1
XDG_VTNR=3
XDG_SESSION_ID=12
XDG_RUNTIME_DIR=/run/user/1001
DEBUGINFOD_URLS=https://debuginfod.archlinux.org 
P9K_SSH=0
PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/opt/cuda/bin:/opt/cuda/nsight_compute:/opt/cuda/nsight_systems/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/usr/local/opt/tcl-tk/bin:/home/arc/.spicetify:/home/arc/.scripts:/home/arc/.cargo/bin:/home/arc/.config/spotifyc
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1001/bus
MAIL=/var/spool/mail/arc
OLDPWD=/home/arc
_=/usr/bin/printenv
KITTY_WINDOW_ID=1
COLORTERM=truecolor
KITTY_PID=4900
KITTY_PUBLIC_KEY=1:Ng}8_J_{vkafdK={TjJKZK}YfMOt`f8PKd8Pgrbr
TERMINFO=/usr/lib/kitty/terminfo
KITTY_INSTALLATION_DIR=/usr/lib/kitty

For the fresh user account, I simply ran:

# usermod -m -G wheel tempuser
# passwd tempuser

And rebooted to get a fresh journalctl output from only that user.
Here's the fresh user journalctl: http://0x0.st/XXmC.txt.

Edit: Some more outputs for clarity:

$ systemctl --user status dbus.service
● dbus-broker.service - D-Bus User Message Bus
     Loaded: loaded (/usr/lib/systemd/user/dbus-broker.service; disabled; preset: enabled)
     Active: active (running) since Thu 2024-05-02 00:20:08 CEST; 7min ago
TriggeredBy: ● dbus.socket
       Docs: man:dbus-broker-launch(1)
   Main PID: 1343 (dbus-broker-lau)
      Tasks: 2 (limit: 36921)
     Memory: 1.0M (peak: 1.6M)
        CPU: 36ms
     CGroup: /user.slice/user-1002.slice/user@1002.service/session.slice/dbus-broker.service
             ├─1343 /usr/bin/dbus-broker-launch --scope user
             └─1344 dbus-broker --log 4 --controller 10 --machine-id 2e9279bcd36d417fb30b906c8f1a0568 --max-bytes 100000000000000 --max-fds 25000000000000 --max-matches 5000000000

May 02 00:20:08 arch systemd[1314]: Starting D-Bus User Message Bus...
May 02 00:20:08 arch dbus-broker-launch[1343]: Service file '/usr/share/dbus-1/services/org.knopwob.dunst.service' is not named after the D-Bus name 'org.freedesktop.Notifications'.
May 02 00:20:08 arch dbus-broker-launch[1343]: Service file '/usr/share/dbus-1/services/org.xfce.Thunar.FileManager1.service' is not named after the D-Bus name 'org.freedesktop.FileManager1'.
May 02 00:20:08 arch dbus-broker-launch[1343]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +31: Eavesdropping is deprecated and ignored
May 02 00:20:08 arch dbus-broker-launch[1343]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +33: Eavesdropping is deprecated and ignored
May 02 00:20:08 arch systemd[1314]: Started D-Bus User Message Bus.
May 02 00:20:08 arch dbus-broker-launch[1343]: Ready

Interestingly the same 'Service file not named after D-Bus name' warning keeps showing up.

$ journalctl -u dbus-broker.service -b
May 02 00:20:00 arch systemd[1]: Starting D-Bus System Message Bus...
May 02 00:20:00 arch dbus-broker-launch[1068]: Looking up NSS user entry for 'pulse'...
May 02 00:20:00 arch dbus-broker-launch[1068]: NSS returned no entry for 'pulse'
May 02 00:20:00 arch dbus-broker-launch[1068]: Invalid user-name in /usr/share/dbus-1/system.d/pulseaudio-system.conf +27: user="pulse"
May 02 00:20:00 arch systemd[1]: Started D-Bus System Message Bus.
May 02 00:20:00 arch dbus-broker-launch[1068]: Ready
May 02 00:20:03 arch dbus-broker-launch[1068]: Activation request for 'org.freedesktop.home1' failed: The systemd unit 'dbus-org.freedesktop.home1.service' could not be found.
May 02 00:20:08 arch dbus-broker-launch[1068]: Activation request for 'org.freedesktop.resolve1' failed: The systemd unit 'dbus-org.freedesktop.resolve1.service' could not be found.

Some familiar faces... Not sure what to get from this information though.

Edit 2: I'm off to bed, stayed up till 4 am last night trying to fix this, will check back in on this first thing in the morning. Also, massive thank you for all the effort you're putting in Seth! I am very grateful to you

Last edited by arc891 (2024-05-01 22:41:00)

seth · 2024-05-01 22:48:05

Interestingly the same 'Service file not named after D-Bus name' warning keeps showing up.

dbus-broker-spam, that's not an issue

The bad messages were

May 01 16:42:17 arch systemctl[1357]: Failed to connect to bus: No such file or directory
May 01 16:42:17 arch systemctl[1356]: Failed to connect to bus: No such file or directory

and those don't exist w/ the new user.

What if you chsh /usr/bin/bash for the "arc" user?
(Ie. is this a zsh-related issue, though I don't see any OMZ variables there )

arc891 · 2024-05-02 09:15:38

Interestingly the same 'Service file not named after D-Bus name' warning keeps showing up.
dbus-broker-spam, that's not an issue

Ah okay, good to know.

The bad messages were
May 01 16:42:17 arch systemctl[1357]: Failed to connect to bus: No such file or directory
May 01 16:42:17 arch systemctl[1356]: Failed to connect to bus: No such file or directory
and those don't exist w/ the new user.
What if you chsh /usr/bin/bash for the "arc" user?
(Ie. is this a zsh-related issue, though I don't see any OMZ variables there )

Just did, but nothing changed as far as I can tell.
I uploaded my output for 'sudo journalctl -b' again: http://0x0.st/XXQa.txt

seth · 2024-05-02 13:12:01

Revert to zsh, if you log into eg. an openbox or sway, or icewm or anything that's not hyprland, do you still get the "Failed to connect to bus" errors?
If not, post yout hyprland config

arc891 · 2024-05-02 14:03:25

seth wrote:

Revert to zsh, if you log into eg. an openbox or sway, or icewm or anything that's not hyprland, do you still get the "Failed to connect to bus" errors?
If not, post yout hyprland config

I don't currently have another WM setup, but I could try to set one up and see if the same error occurs indeed.

In the meantime, here's my hyprland config: https://pastebin.com/ZYexgGA2.

(Edit for clarity)

Last edited by arc891 (2024-05-02 14:04:13)

arc891 · 2024-05-02 14:20:26

seth wrote:

Revert to zsh, if you log into eg. an openbox or sway, or icewm or anything that's not hyprland, do you still get the "Failed to connect to bus" errors?

Just installed IceWM and quickly tried this, but seems the same errors are still appearing...
IceWM 'sudo journalctl -b' output: https://0x0.st/XXe-.txt

seth · 2024-05-02 14:30:43

pastebin is 403, but b/c of icewm we know it's not hyprland.
It's also not your $SHELL but seems to be the UID.
"DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1001/bus" looks ok, too.

User daemon specific?

ls -laR ~/.config/systemd/user

arc891 · 2024-05-02 14:41:39

seth wrote:

pastebin is 403, but b/c of icewm we know it's not hyprland.

Ah mb, put it on private instead of unlisted, should be up now, but yeah indeed, makes sense it's not hyprland.

seth wrote:

It's also not your $SHELL but seems to be the UID.
"DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1001/bus" looks ok, too.
User daemon specific?
ls -laR ~/.config/systemd/user

Oooh okay, so this might be something here actually, to comment back on my little project I was working on, since it now might actually be relevant, I was trying to make swaylock activate upon removal of my YubiKey. Now to do this, I had been fiddling with udev rules, and making those run a systemd service which would run swaylock. During this, I tried making a user systemd service, for which I saw some recommendations to put those in a .config/systemd/user folder, which did not yet exist on my system, so I made it and added my service file in there. Now that I ran your command, I'm seeing a lot more files in there than I put there myself:

$ ls -laR ~/.config/systemd/user
drwxr-xr-x - arc 14 Mar 17:44  default.target.wants
drwxr-xr-x - arc 10 Mar 22:46  sockets.target.wants
lrwxrwxrwx - arc  2 May 16:36  lock_screen.service -> ../../../.dotfiles/.config/systemd/user/lock_screen.service
.rw-r--r-- 0 arc  2 May 16:36  mpris-proxy.service
lrwxrwxrwx - arc 10 Mar 22:38  pipewire-media-session.service -> /dev/null
lrwxrwxrwx - arc 10 Mar 22:38  pipewire-pulse.service -> /dev/null
lrwxrwxrwx - arc 10 Mar 22:38  pipewire.service -> /dev/null

/home/arc/.config/systemd/user/default.target.wants:
lrwxrwxrwx - arc 14 Mar 17:44  mpris-proxy.service -> /home/arc/.config/systemd/user/mpris-proxy.service
lrwxrwxrwx - arc 10 Mar 22:46  pulseaudio.service -> /usr/lib/systemd/user/pulseaudio.service

/home/arc/.config/systemd/user/sockets.target.wants:
lrwxrwxrwx - arc 10 Mar 22:46  pulseaudio.socket -> /usr/lib/systemd/user/pulseaudio.socket

seth · 2024-05-02 14:57:34

You're masking pipewire and run pulseaudio and mpris.

I'd try to undo "fiddling with udev rules, and making those run a systemd service which would run swaylock. During this, I tried making a user systemd service, for which I saw some recommendations to put those in a .config/systemd/user folder" and see whether that has any impact on the situation.
If it fixes it, we at least know what it is and can focus on straighten that out.

arc891 · 2024-05-02 15:32:58

seth wrote:

You're masking pipewire and run pulseaudio and mpris.

This might still be from the time I accidentally installed pipewire and wanted to move back, but couldn't uninstall due to errors breaking dependencies:

$ sudo pacman -R pipewire
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: removing pipewire breaks dependency 'pipewire' required by gst-plugin-pipewire
:: removing pipewire breaks dependency 'pipewire' required by obs-studio
:: removing pipewire breaks dependency 'pipewire' required by wireplumber
:: removing pipewire breaks dependency 'pipewire' required by xdg-desktop-portal
:: removing pipewire breaks dependency 'pipewire' required by xdg-desktop-portal-hyprland

I managed to get pulseaudio working again after a lot of messing around and masking pipewire and perhaps also mpris.

seth wrote:

I'd try to undo "fiddling with udev rules, and making those run a systemd service which would run swaylock. During this, I tried making a user systemd service, for which I saw some recommendations to put those in a .config/systemd/user folder" and see whether that has any impact on the situation.
If it fixes it, we at least know what it is and can focus on straighten that out.

Alright, I removed my custom udev rule file from /etc/udev/rules.d/, checked to make sure my user service file was not in /etc/systemd/system/ and not loaded anywhere with 'systemctl --user list-units --all', and renamed my .config/systemd folder to .config/systemd.old so it wouldn't be used, and rebooted. That should be about all the changes I made (checked my .zsh_history), however, this did not make a difference either Still the same errors.
Either I'm still missing something, or it's not it, but I really thought we were on the right track here.

seth · 2024-05-02 18:41:31

You didn't mask pipewire/enable pulseaudio for your test user, did you?
I'm not even sure whether this is possible on a per-user service level.

=> Try to do the same for the test user and see whether it causes the same symptoms there.

arc891 · 2024-05-02 19:50:22

seth wrote:

You didn't mask pipewire/enable pulseaudio for your test user, did you?
I'm not even sure whether this is possible on a per-user service level.
=> Try to do the same for the test user and see whether it causes the same symptoms there.

No I didn't mask pipewire there, so sure, I can try. Am not currently at my laptop, so will get back on this, but would it also suffice to forcibly remove pipewire? Just found out about pacman -Rdd, but not sure if that's a good move.

I'll let you know what I find on my test user after masking.

seth · 2024-05-02 19:55:40

I'd try to replicate the error to understand where it's coming from rather than messing the system up even more.
In case the PW/PA shenanigans are at the bottom of this, I'd then ask why you're doing that at all (ie. try to enforce PA this way despite PW apparently being a hard dependency of the system setup)

arc891 · 2024-05-02 20:02:55

seth wrote:

I'd try to replicate the error to understand where it's coming from rather than messing the system up even more.
In case the PW/PA shenanigans are at the bottom of this, I'd then ask why you're doing that at all (ie. try to enforce PA this way despite PW apparently being a hard dependency of the system setup)

That makes sense.

I have a lot of pulseaudio applications, and when I installed Pipewire just being curious about the differences, it messed up my existing pulseaudio setup and I had no audio whatsoever anymore, after which I was then also not able to remove Pipewire, hence the weird situation with masking it etc.

But good point, I'll make sure to first figure out the current situation by trying to replicate it. Perhaps I didn't mask it correctly or did something else wrong.

I'll get back to you once I get back behind my laptop.

seth · 2024-05-02 20:03:58

https://archlinux.org/packages/extra/x8 … ire-pulse/

arc891 · 2024-05-02 21:33:45

seth wrote:

You didn't mask pipewire/enable pulseaudio for your test user, did you?
I'm not even sure whether this is possible on a per-user service level.
=> Try to do the same for the test user and see whether it causes the same symptoms there.

Just went ahead and tried this, for a second thought that I had reproduced it, but turns out I hadn't. I was lucky to find my zsh history still had the commands from when it happened, I ran a few commands to try and fix it at the time:

$ systemctl --user mask wireplumber pipewire-pulse{,.socket} --now
$ systemctl --user --now disable pipewire-media-session.service
$ systemctl --user --now mask pipewire-media-session.service
$ systemctl --user --now disable pipewire pipewire-pulse
$ systemctl --user --now mask pipewire pipewire-pulse
$ systemctl --user unmask pulseaudio.service pulseaudio.socket
$ sudo systemctl --user enable pulseaudio.service pulseaudio.socket
$ sudo systemctl enable pulseaudio

All in attempt to undo the changes that had been done during pipewire's installation, and trying to make pulseaudio work again.
Also, seems like pipewire-pulse had also been the package I had tried to install back when this happened a few months back.
However, running all these commands on my test user had no effect on it whatsoever as far as I can see. After a reboot the dbus was still up and running like it's a normal day in the field, and sound was still working just fine under pulseaudio.
The two commands disabling pipewire, pipewire-pulse and pipewire-media-session gave some error message about this not being the right way to do it, and something to do with the d-bus (didn't save the output, and now can't get the same message back sadly), after which I got some outputs which reminded me a lot of the journalctl errors we found earlier, but turns out those were unrelated and situational, and nothing happened after a reboot.

Would just fixing this on my 'issue'-account have the possibility to solve the problem at hand?

arc891 · 2024-05-02 21:51:32

arc891 wrote:

Would just fixing this on my 'issue'-account have the possibility to solve the problem at hand?

Well, I went ahead and tried to look for stray pipewire and wireplumber services, and I found some running, so I stopped and disabled them, ~~after which my pulseaudio errors in my journalctl disappeared,~~ however the dbus issue still persists, ~~so it likely wasn't pulseaudio/pipewire related~~

For clarity, the commands I ran:

$ systemctl --user stop pipewire.socket
$ systemctl --user disable pipewire.socket
$ sudo systemctl --global disable pipewire.socket
$ systemctl --user stop wireplumber.service
$ systemctl --user disable wireplumber.service
$ sudo systemctl --global disable wireplumber.service

My current output of 'sudo journalctl -b': https://0x0.st/XX9E.txt

Edit: wait I didn't look correctly, apparently nothing is fixed huh, when going through the journalctl output and searching for pulseaudio I couldnt find anything, and now it is still in there, let me get back on this.
-> Edit 2: The error messaged only appeared after my first journalctl -b which is the one I searched through, I posted my second run of the command, expecting it to be the same, but which did contain the errors.
Edit 3: Even though pulseaudio gives those errors after a boot and fails, pulseaudio does still manage to start up after a manual 'systemctl --user start pulseaudio' without issues. Not sure if helpful/related, but figured I'd add it.

Last edited by arc891 (2024-05-02 22:01:31)

Arch Linux

#1 2024-05-01 15:03:28

dbus-broker.service: Exiting due to fatal error: -2

#2 2024-05-01 15:48:28

Re: dbus-broker.service: Exiting due to fatal error: -2

#3 2024-05-01 15:57:10

Re: dbus-broker.service: Exiting due to fatal error: -2

#4 2024-05-01 16:13:09

Re: dbus-broker.service: Exiting due to fatal error: -2

#5 2024-05-01 16:26:33

Re: dbus-broker.service: Exiting due to fatal error: -2

#6 2024-05-01 16:35:19

Re: dbus-broker.service: Exiting due to fatal error: -2

#7 2024-05-01 16:44:32

Re: dbus-broker.service: Exiting due to fatal error: -2

#8 2024-05-01 21:22:32

Re: dbus-broker.service: Exiting due to fatal error: -2

#9 2024-05-01 22:22:42

Re: dbus-broker.service: Exiting due to fatal error: -2

#10 2024-05-01 22:48:05

Re: dbus-broker.service: Exiting due to fatal error: -2

#11 2024-05-02 09:15:38

Re: dbus-broker.service: Exiting due to fatal error: -2

#12 2024-05-02 13:12:01

Re: dbus-broker.service: Exiting due to fatal error: -2

#13 2024-05-02 14:03:25

Re: dbus-broker.service: Exiting due to fatal error: -2

#14 2024-05-02 14:20:26

Re: dbus-broker.service: Exiting due to fatal error: -2

#15 2024-05-02 14:30:43

Re: dbus-broker.service: Exiting due to fatal error: -2

#16 2024-05-02 14:41:39

Re: dbus-broker.service: Exiting due to fatal error: -2

#17 2024-05-02 14:57:34

Re: dbus-broker.service: Exiting due to fatal error: -2

#18 2024-05-02 15:32:58

Re: dbus-broker.service: Exiting due to fatal error: -2

#19 2024-05-02 18:41:31

Re: dbus-broker.service: Exiting due to fatal error: -2

#20 2024-05-02 19:50:22

Re: dbus-broker.service: Exiting due to fatal error: -2

#21 2024-05-02 19:55:40

Re: dbus-broker.service: Exiting due to fatal error: -2

#22 2024-05-02 20:02:55

Re: dbus-broker.service: Exiting due to fatal error: -2

#23 2024-05-02 20:03:58

Re: dbus-broker.service: Exiting due to fatal error: -2

#24 2024-05-02 21:33:45

Re: dbus-broker.service: Exiting due to fatal error: -2

#25 2024-05-02 21:51:32

Re: dbus-broker.service: Exiting due to fatal error: -2

Board footer