Hi, I'm running Plasma + sddm on F31. Since a week, I try to use the computer with multiple users and then I log off before the other user logs in. When I log off, the screen just freezes. I can switch to a console screen with Ctrl+Alt+F2 and kill all processes of the first user (systemd, agent, sddm_helper) until I get the login screen again. Very annoying. Is there a way to make it work? Kind regards, F
On Thu, 2020-08-20 at 19:43 +0200, Frédéric wrote:
Hi, I'm running Plasma + sddm on F31. Since a week, I try to use the computer with multiple users and then I log off before the other user logs in. When I log off, the screen just freezes. I can switch to a console screen with Ctrl+Alt+F2 and kill all processes of the first user (systemd, agent, sddm_helper) until I get the login screen again. Very annoying. Is there a way to make it work?
I use Plasma + sddm on F31. I don't know if I have the same use that you have, but to restart sddm you just need
systemctl restart sddm
Kind regards, F _______________________________________________ kde mailing list -- kde@lists.fedoraproject.org To unsubscribe send an email to kde-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.org
Frédéric wrote:
Hi, I'm running Plasma + sddm on F31. Since a week, I try to use the computer with multiple users and then I log off before the other user logs in. When I log off, the screen just freezes. I can switch to a console screen with Ctrl+Alt+F2 and kill all processes of the first user (systemd, agent, sddm_helper) until I get the login screen again. Very annoying. Is there a way to make it work?
2 things to try: * disable session management, systemsettings5->startup&shutdown->desktop session, On Login chose option *other* than "Restore previous session" * enable logind feature to kill user processes on logout, edit /etc/systemd/logind.conf , set key KillUserProcesses=yes
-- Rex
2 things to try:
- disable session management, systemsettings5->startup&shutdown->desktop
session, On Login chose option *other* than "Restore previous session"
That was already set to "Start with an empty session".
- enable logind feature to kill user processes on logout, edit
/etc/systemd/logind.conf , set key KillUserProcesses=yes
This did not fix it. It's really a bug with sddm.
Thank you,
F
On 24/08/2020 22:32, Frédéric wrote:
2 things to try:
- disable session management, systemsettings5->startup&shutdown->desktop
session, On Login chose option *other* than "Restore previous session"
That was already set to "Start with an empty session".
- enable logind feature to kill user processes on logout, edit
/etc/systemd/logind.conf , set key KillUserProcesses=yes
This did not fix it. It's really a bug with sddm.
Thank you,
F ___________
I agree there is a problem but not 100% sure it is sddm.
I have a similar and may be the same problem.
I use multiple users to isolate work from play and I have had issues with one account that when I logout, it freezes with the background showing. Mouse moves but nothing works in it.
There are enough processes running and I go into another account and slowly kill them off. I have had KillUserProcesses=yes set for a very long time on this machine.
The last process I end up killing it the sddm-helper session for that user.
I have had this on both F31 and F32 but have not had the time or energy to try to do any debugging on it.
I have it set to start with an empty session.
On logout it freezes.
Other accounts don't freeze like this on this machine. I have another account that I have never had freeze up this way.
Under top, these are the processes that are running for this user after an attempt to logout.
dbus-broker gvfsd kglobalaccel5 dconf-service abrt-applet pulseaudio agent kactivitymanage at-spi-bus-laun dbus-broker-lau dbus-broker gconf-helper gconfd-2 kscreen_backend at-spi2-registr kdeconnectd
gconf-helper will remain a zombie until pulseaudio is killed.
I think there is a process that cannot be stopped and is preventing sddm from working properly.
I usually have at least two different session open on this machine at all times and will open a third and/or fourth session from time to time.
Robin