Second session has the greeter image, but there is no greeter process running. Password entry is not possible, clicking gives no reaction. STEPS TO REPRODUCE Me and my wife share the same computer for surfing / reading mail. We usually have two sessions running all the time. I use the computer more. Sometimes she finds that she can not log in (she does not log in every day). Updates are frequent (OpenSuSE Tumbleweed) and it usually works great some time after update... Not the first time (she had problems logging in before) but this time I decided to investigate. OBSERVED RESULT There is no kscreenlocker_greet for her account (output from Ctrl-Alt-F1 text console while both locked) roger 4137 0.0 0.0 215852 15528 ? Sl Nov02 0:02 /usr/lib64/libexec/kf5/kscreen_backend_launcher annika 9908 0.0 0.0 215836 13368 ? Sl Nov02 0:00 /usr/lib64/libexec/kf5/kscreen_backend_launcher roger 17235 1.2 0.4 830804 150480 ? Sl 08:39 0:01 /usr/lib64/libexec/kscreenlocker_greet --immediateLock --graceTime 5000 --ksldfd 66 root 17421 0.0 0.0 3680 796 tty1 S+ 08:41 0:00 grep --color=auto screen The only visible difference between (Ctrl-Alt-F7 i.e. my session) and (Ctrl-Alt-F8 i.e. her session) is time and date Mine is updated to todays date 11 November, hers is stuck at 8 November) EXPECTED RESULT Two kscreenlocker_greet processes, one for each session. Logging in should work on both sessions. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: OpenSuSE Tumbleweed (available in About System) KDE Plasma Version: 5.17.1 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION Intel integrated graphics drivers, xf86-video-intel 2.99.917+git8674.25c9a2fcc-4.1
> The only visible difference between (Ctrl-Alt-F7 i.e. my session) and > (Ctrl-Alt-F8 i.e. her session) is time and date > Mine is updated to todays date 11 November, hers is stuck at 8 November) Thanks, that's relevant. Can you correct the date and time on her account and see if that fixes the problem? I think the date being wrong may be triggering a security measure in the auth system.
Time on both accounts should be identical, I think her time was from when the process crached. I did a C-A-Backspace Backspace on her session it begun working again after that. Next time...
This interface is confusing - removing NEEDSINFO
Created attachment 124629 [details] zypp log Not seen the problem (nor rebooted since 2019-11-13 update), together with replacing CPU (disks are the same, still no external GPU) something (HW or SW) has fixed the issue! Old CPU: Intel Core i5-2500K RAM: 2*16GB + 2*8GB = 24GB DDR3 MB: ASUS P8H67-M New CPU: Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz RAM: 4*16G = 32GB DDR3 MB: ASUS H97M-PLUS Do not remember if the Power unit got replaced too, probably. Inherited the components from my children...
Created attachment 124796 [details] Another update (zypper history) After update problems reappeared in force... (unusable the day after) But after I changed from Plasma (Wayland or Full Wayland - don't remember) to pure Plasma (without Wayland) it works again.
Created attachment 125157 [details] strace of process So, when I got to the computer my screen was locked showing a time more than 12 h old. It was not possible to log in - no field for entry. But the kscreen lock process existed, straced it (see attachment) tried "kill -USR1 pid" no change, tried "kill -USR2 pid" time on screen updated and I was able to log in.
Note: I am running pure plasma now!
Thank you for reporting this issue. As it has been a while since it was reported, can we please ask you to see if you can reproduce the issue with a recent software version? Like Plasma 5.25, or ideally 5.26? If you can still reproduce the issue with one of those Plasma versions, please change the status to "CONFIRMED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!