| Summary: | SimulateUserActivity doesn't unlock the screen, even when unlocking without password is enabled | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Forest <forestix> |
| Component: | Screen locking | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | CONFIRMED --- | ||
| Severity: | minor | CC: | audvare, bshah, kde, nate |
| Priority: | NOR | ||
| Version First Reported In: | 6.2.4 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Forest
2021-06-29 20:12:40 UTC
Docs for this method say: "If the screensaver is not activated then the idle timers will be reset. " Can you expand on your use case? > "If the screensaver is not activated then the idle timers will be reset. " The precondition in that sentence is strange, because it doesn't match what happens with actual user activity. Perhaps it was an oversight? Was it written before the "Allow unlocking without password" configuration setting existed? > Can you expand on your use case? The use case is gaming. I maintain a utility called joystickwake that delays screen blankers in response to game controller input, but this issue also applies to games and emulators that would do so themselves. Scenario: - User starts playing a joystick-based game with no mouse or keyboard activity. - SimulateUserActivity events periodically reset the screen timeout. - User pauses the game, perhaps to answer a phone call. - SimulateUserActivity calls are not produced while the joystick is idle. - Screen times out & goes blank. - User notices this and moves the joystick to wake the screen. - Screen does not wake. - User now has to put down the joystick, walk across the room, use the mouse or keyboard to wake the screen, walk back across the room, and pick up the joystick, before resuming play. If SimulateUserActivity actually simulated user activity, moving the joystick would have been sufficient to wake the screen. |