| Summary: | The screen locked and wouldn't unlock | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | php4fan |
| Component: | general | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | grave | CC: | kde, nate, nicolas.fella |
| Priority: | NOR | ||
| Version First Reported In: | 6.3.3 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Manjaro | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
php4fan
2025-03-30 19:33:13 UTC
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. 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 pretty often, when I'm thinking in front of the screen and not touching keyboard and mouse, and I notice that it's going to lock. I'm not sure if the password prompt is supposed to have the time to become visible in that case (or if it's only supposed to show an empty screen and then go back immediately to the desktop as you shake the mouse without ever transitioning to the password prompt screen) but it definitely often does show up for a brief moment, even though it then immediately goes away without having to actually insert the password. When the issue happened, this was one of those cases. So I'm thinking: MAYBE, just maybe, there's a race condition such that, if you shake the mouse exactly at the right (or rarther the wrong) time, just barely after the screen has gotten locked, the system "thinks" that you shook the mouse soon enough to prevent locking, but actually you didn't, so the password prompt is visible (and interactive), but the system "doesn't know" that it's required and therefore ignores it. Maybe it's nothing like that, I don't know, it's just a hypothesis. I've seen bugs this stupid, I wouldn't be surprised. > 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 prevent locking - that's the whole point.
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 How is this importance "normal"??? It should be higher than "normal", but your poor behavior caused Nicolas to over-react in changing the severity. Please try to communicate in a more neutral way, even when the problem is very severe. This will help avoid pointless arguments and hurt feelings. Thanks. Either way, duplicate of Bug 484363. *** This bug has been marked as a duplicate of bug 484363 *** *** This bug has been marked as a duplicate of bug 500339 *** |