This is an Arch Linux issue but I’m not running Arch and we all know the rules about reporting issues there. It affects Manjaro too of course.
The recent switch to
dbus-broker introduced some new warnings. After digging further I found that none of them are cause for immediate concern but they do indicate that Arch and Manjaro use dbus activation in a way that depends on legacy support. In particular
Service file '/usr/share//dbus-1/services/org.kde.dolphin.FileManager1.service' is not named after the D-Bus name 'org.freedesktop.FileManager1'.
Service file '/usr/share//dbus-1/services/org.kde.plasma.Notifications.service' is not named after the D-Bus name 'org.freedesktop.Notifications'.
These session service files are named like that to allow multiple DEs to be installed (otherwise they’d all be fighting over e.g.
dbus-broker does not support that use-case (and never will) and there is no way to disable these warnings. It only allows this naming at all for legacy support.
After Fedora 30 switched to
dbus-broker they removed dbus activation of DE-specific org.freedesktop.* session services in Fedora 31. Arch will need do the same IMHO (or continue shipping a distro that outputs warnings indicating use of a dbus legacy support feature).
As for the other warnings;
Activation request for 'org.freedesktop.home1' failed: The systemd unit 'dbus-org.freedesktop.home1.service' could not be found.
systemd-homed service is disabled/masked. Can be silenced by commenting out 4 lines referring to
/etc/pam.d/system-auth. See [solved] pam fails to find unit dbus-org.freedesktop.home1.service / Newbie Corner / Arch Linux Forums
Activation request for 'org.freedesktop.resolve1' failed: The systemd unit 'dbus-org.freedesktop.resolve1.service' could not be found.
systemd-resolved service is disabled/masked. Can be silenced by adding
systemd-resolved=false option to NetworkManager configuration;
echo -e '[main]\nsystemd-resolved=false' | sudo tee /etc/NetworkManager/conf.d/no-systemd-resolved.conf
Service file '/usr/share//dbus-1/services/org.kde.kscreen.service' is not named after the D-Bus name 'org.kde.KScreen'.
Seems to be an upstream issue, as far as I can see there’s no good reason for it not to be capitalised correctly.