Using sddm, login into a (preferably light) window manager and enter: loginctl you'll get: > loginctl SESSION UID USER SEAT c11 958 sddm seat0 c12 1000 you seat0 Session c11 here should not be closed: >loginctl session-status c11 returns: State: closing Unit: session-c11.scope ââ26557 dbus-launch --autolaunch b524af88b4fb6821f6a8a1a765167 ââ26558 /usr/bin/dbus-daemon --fork --print-pid 5 and this is dbus-launch --auto-launch which is causing the hang. > systemctl shows that, indeed, the session is "abandoned": session-c11.scope loaded active abandoned Session c11 of user sddm It is not clear to me why dbus-launch is started with the option --autolaunch, and if it is started by sddm or by our wrapper around it. The man of dbus-launch discourages to do so: "The --autolaunch option is considered an internal implementation detail of libdbus, and in fact there are plans to change it. There's no real reason to use it outside of the libdbus implementation anyhow". I am investigating, but any help would be welcome. I already reported this issue a while ago upstream, they do not give a s..., unfortunately. Cheers, Chris.
Arg, made a very unfortunate typo: I meant "Session c11 here should BE closed".
CC: (none) => marja11Assignee: bugsquad => mageia
CC: (none) => doktor5000
Assignee: mageia => kde
Added Neil as CC, he may have an idea from his fedora experience and all the DM started with systemd services ;)
CC: (none) => ngompa13
Workaround here: https://bugs.mageia.org/show_bug.cgi?id=19821#c1
is it still valid on current cauldron ?
CC: (none) => mageia
Yes it is. Reported upstream, they do not give a shit, as for the other bugs. I am convinced sddm sucks and the developers do not understand systemd. Even "xdm" works better. They please themselves ringing bells and making dirt shinning, but at the end, counting users and not pulling mess into the login sessions is too difficult for them. We should move to lightdm, that's a personal opinion of course, but supported by facts. Cheers, chris.
I noticed just last week that when the sddm package is deleted, sddm leaves it's entry in /etc/group.
CC: (none) => hoytduff
As of today in Cauldron, sddm version is sddm-0.18.1-4.mga8 and every sddm.user.slice are correctly ended when user log on to desktop env. loginctl reports: [aurelien@mageia ~]$ loginctl SESSION UID USER SEAT TTY c2 1000 aurelien seat0 So, no longer exists in Cauldron.
CC: (none) => ouaurelienResolution: (none) => OLDStatus: NEW => RESOLVED