https://bugs.kde.org/show_bug.cgi?id=502213
Nicolas Fella changed:
What|Removed |Added
CC||nicolas.fe...@gmx.de
Severity|critica
https://bugs.kde.org/show_bug.cgi?id=502213
Nate Graham changed:
What|Removed |Added
Severity|normal |grave
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=502213
--- Comment #4 from Nicolas Fella ---
I understand you are frustrated, but this kind of language is not helping you
in any way. Please keep this in mind for future reports
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=502213
--- Comment #5 from php4...@gmail.com ---
How is this importance "normal"???
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=502213
--- Comment #3 from php4...@gmail.com ---
> When the issue happened, this was one of those cases.
I meant it was one of those cases where I shake the mouse immediately as I
notice that the screen changes. Obviously in this case it wasn't fast enough to
https://bugs.kde.org/show_bug.cgi?id=502213
--- Comment #2 from php4...@gmail.com ---
Just realized something.
Normally, when the screen goes to lock, if I am quick enough to shake the
mouse, it will unlock immediately without having to insert the password. I
assume that's intended. I do that pre
https://bugs.kde.org/show_bug.cgi?id=502213
--- Comment #1 from php4...@gmail.com ---
I now see that next time this happens I can do "loginctl unlock-session 1"
instead of rebooting.
Still, most users won't know this and will be forced to reboot, so the issue is
critical.
--
You are receiving th
