Closed xiangsheng closed 8 months ago
Thanks for the report! Do you use DDE
? Did you try uninstalling whatever provides dde-session@.service
?
Thanks for the report! Do you use
DDE
? Did you try uninstalling whatever providesdde-session@.service
?
No, I don't use it. The only reason that I keep it is because I don't know how to uninstall it completely.
You can use pacman -Qo /path/to/file
to see which package owns a specific file (in this case dde-session@.service
. You can then use pacman -Rs <package>
to remove the package.
You can also use pacman -Qs dde
to find locally installed packages with dde
in their name.
After removing the dde, I can log into the plasma normally with dbus-broker-units
. So the problem may be caused by the existence of dde.
I notice another info maybe related to this bug. That is, the following error, appearing in my opening post, also appears if I use the dbus-daemon-units
.
Jan 16 20:30:11 xiangsheng-pc systemd[1104]: dde-session@x11.service: Two services allocated for the same bus name org.kde.KWin, refusing operation.
However, with dbus-daemon-units
, this error only happens after I've logged into the KDE. Maybe, that is the reason why the same error doesn't lead to a failed login in dbus-daemon-units
.
Jan 16 20:30:11 xiangsheng-pc systemd[1104]: dde-session@x11.service: Two services allocated for the same bus name org.kde.KWin, refusing operation.
However, with
dbus-daemon-units
, this error only happens after I've logged into the KDE. Maybe, that is the reason why the same error doesn't lead to a failed login indbus-daemon-units
.
This error originates in systemd, which complains that multiple units in your user-instance have the same bus-name configured.
Whether this errors happens before or after you login depends on which units are available for your login manager. However, this configuration is completely outside of the control of the message bus.
I will close this bug as resolved, given that conflicting configurations lead to the issue, and this seems to be resolved. Let me know if there is more to investigate! Thanks!
I have a maybe similar problem as #337. But I can reach the SDDM screen but just get stuck here. When I try to log in, the kde tries to load the desktop environment (a black screen with an icon indicating loading in the center) and fails, just goes back to the SDDM.
I look through the journald log for the failed login. It seems the following part of log is rather suspicious. As I understand, this log says that the kwin service failed to start due to the existence of another DE, i.e. dde or deepin de. Although, I don't know why another DE exists in my system, I only use KDE, this extra DE never causes any problem before and I just ignored it.