Warnings after installing dbus-broker-units

[MrLavender]

Some new warnings after installing dbus-broker-units should I be concerned?

$ journalctl -b1 -p4 --no-pager | grep dbus

$ journalctl -b -p4 --no-pager | grep dbus
Jan 13 12:05:59 RYZEN-5800X dbus-broker-launch[605]: Activation request for 'org.freedesktop.home1' failed: The systemd unit 'dbus-org.freedesktop.home1.service' could not be found.
Jan 13 12:06:00 RYZEN-5800X dbus-broker-launch[787]: Service file '/usr/share//dbus-1/services/org.kde.dolphin.FileManager1.service' is not named after the D-Bus name 'org.freedesktop.FileManager1'.
Jan 13 12:06:00 RYZEN-5800X dbus-broker-launch[787]: Service file '/usr/share//dbus-1/services/org.kde.kscreen.service' is not named after the D-Bus name 'org.kde.KScreen'.
Jan 13 12:06:00 RYZEN-5800X dbus-broker-launch[787]: Service file '/usr/share//dbus-1/services/org.kde.plasma.Notifications.service' is not named after the D-Bus name 'org.freedesktop.Notifications'.
Jan 13 12:06:04 RYZEN-5800X dbus-broker-launch[605]: Activation request for 'org.freedesktop.resolve1' failed: The systemd unit 'dbus-org.freedesktop.resolve1.service' could not be found.

[nikgnomic]

Messages relating to org.freedesktop.home1 and org.freedesktop.resolve1 can be ignored
But if you do not want messages spamming journal:

To get rid of messages for home1 edit file /etc/pam.d/system-auth

sudo nano /etc/pam.d/system-auth

and comment out the 4 lines relating to pam_systemd_home.so with #

/etc/pam.d/system-auth

#%PAM-1.0

auth       required                    pam_faillock.so      preauth
# Optionally use requisite above if you do not want to prompt for the password
# on locked accounts.
#-auth      [success=2 default=ignore]  pam_systemd_home.so
auth       [success=1 default=bad]     pam_unix.so          try_first_pass nullok
auth       [default=die]               pam_faillock.so      authfail
auth       optional                    pam_permit.so
auth       required                    pam_env.so
auth       required                    pam_faillock.so      authsucc
# If you drop the above call to pam_faillock.so the lock will be done also
# on non-consecutive authentication failures.

#-account   [success=1 default=ignore]  pam_systemd_home.so
account    required                    pam_unix.so
account    optional                    pam_permit.so
account    required                    pam_time.so

#-password  [success=1 default=ignore]  pam_systemd_home.so
password   required                    pam_unix.so          try_first_pass nullok shadow
password   optional                    pam_permit.so

#-session   optional                    pam_systemd_home.so
session    required                    pam_limits.so
session    required                    pam_unix.so
session    optional                    pam_permit.so

To get rid of messages for resolve1 Network manager can be configured to ignore systemd-resolved

sudo tee /etc/NetworkManager/conf.d/no-systemd-resolved.conf <<<'[main]
systemd-resolved=false'