Dear Maintainer,

SDDM launches what appears to be a redundant dbus-daemon process.
This can be observed by simply logging in as normal and using
'pgrep --list-full dbus-daemon', which will list 2 processes
having the '--session' argument. Upon inspecting the PIDs,
once of the processes was started as user 'sddm' while the
other is started by the currently logged in user.

There is no activity on that dbus daemon session at all. This
was determined by applying load on the dbus daemon and observing
the CPU time used. After a day of uptime, the process started up
as the 'sddm' user had used 0:00.00 CPU time.

This is not a serious bug at all, as the dbus-daemon process is
usually very lightweight taking very small amounts of memory,
but it would be nice to have the process tree clean.
Maybe the upstream had plans to have sddm handle the dbus and
they haven't gone with it fully yet, this could explain it.

Thanks