You are not logged in.
I had the same problem and I think the error tells very clear what the issue is.
I solved it by making a symlink "dbus-org.freedesktop.home1.service" -> "systemd-hostnamed.service".
After this the log spam stopped.
Actually this is the real solution as dbus-org.freedesktop.home1.service is an alias to systemd-hostnamed.service (similar like dbus-org.freedesktop.oom1.service to systemd-oomd.service) but for whatever reason the symlink is (only for this one file) missing.
Offline
for whatever reason the symlink is (only for this one file) missing.
Upstream does not create the alias for dbus-org.freedesktop.home1.service [1].
It does for dbus-org.freedesktop.oom1.service but that is being removed in systemd 251 [2] as such links are meant to be dynamically installed when the service is enabled.
[1] https://github.com/systemd/systemd/blob … build#L229
[2] https://github.com/systemd/systemd/comm … 94c33391a0
Last edited by loqs (2022-04-23 12:05:44)
Offline
I had the same problem and I think the error tells very clear what the issue is.
I solved it by making a symlink "dbus-org.freedesktop.home1.service" -> "systemd-hostnamed.service".
After this the log spam stopped.Actually this is the real solution as dbus-org.freedesktop.home1.service is an alias to systemd-hostnamed.service (similar like dbus-org.freedesktop.oom1.service to systemd-oomd.service) but for whatever reason the symlink is (only for this one file) missing.
You're confusing hostnamed with homed.
systemd-hostnamed has an alias dbus-org.freedesktop.hostname1.service, but that has nothing to do with homed.
This is what you probably wanted instead:
sudo ln -s /usr/lib/systemd/system/systemd-homed.service /etc/systemd/system/dbus-org.freedesktop.home1.service
which results in /etc/systemd/system/dbus-org.freedesktop.home1.service -> /usr/lib/systemd/system/systemd-homed.service
But this will result in systemctl list-unit-files reporting systemd-homed as enabled and the file will be removed if you systemctl disable systemd-homed.
Last edited by xnor (2022-07-22 19:28:50)
Offline
So what is the proper solution/workaround as of 2023? This little bugger is flooding my journal.
Offline
You can comment all pam_systemd_home.so lines in /etc/pam.d/* (mostly system-auth) but will have to adapt future changes to the file manually.
nb. that this is just spam and not an actual error (or indicative of one)
Offline
I have this in my pacman.conf, to avoid having to edit PAM config:
NoExtract = usr/lib/security/pam_systemd_home.so
(and remove the file manually once)
Offline