https://bugs.kde.org/show_bug.cgi?id=495451
--- Comment #2 from Oded Arbel <o...@geek.co.il> --- The problem is that the system is broken, and it isn't clear that it's the user's/distro fault and what needs fixing, and how. The example, `loginctl unlock-session` doesn't work. It took me quite a while to figure out that the problem is the screen locker, and that it was the pam error messages that are related. I remember there used to be a behaviour, when the screen locker would have a problem - you'd get a black screen with a message "the lock screen is broken, switch to a virtual terminal and run loginctl unlock-session", or something like that - this seems like a premise example of a situation that can benefit that from such a behaviour. I think at the minimum, there shouldn't be a lock screen issue that prevents loginctl unlock-session from working. -- You are receiving this mail because: You are watching all bug changes.
