Description: I have upgraded the system like I always do. After reboot, there is a problem with dbus.service. It cannot start, timeouts. Some user applications relying on dbus does not work (pulseaudio) or work but with limitations like no configuration saving (thunar)

I will attach the pacman.log with jounralctl output from the same time. There are some Permission denied messages, but the permissions look fine on the filesystem (read for all) for files like /usr/share/dbus-1/system.conf or others specified in the log file

The system I am running was installed about 8 years ago, so far I had no problem. There is more than 40G for ROOT filesystem, other filesystems has even more available space. Inodes are not even reaching 10% of capacity.

The logs are from time I've performed system update. Journalctl got crazy after systemd has been reinstalled (see pacman.log vs journalctl.log at the same time).

Can you please help me solving this issue? I do believe this is a bug in the newer systemd. I've tried compiling the systemd version 254.1 (version before 254.1-1 see: https://gitlab.archlinux.org/archlinux/packaging/packages/systemd/-/tree/16606ae8cfac3b36d38b3166fa1c40de9625dd00) but that did fail in check(), see compile.log

Also attaching installed file, containing output of pacman -Qs