https://bugs.kde.org/show_bug.cgi?id=479659
Vlad Zahorodnii <vlad.zahorod...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|ASSIGNED |RESOLVED
Latest Commit| |https://invent.kde.org/plas
| |ma/kwin/-/commit/bbb40a9a84
| |200866872ea6726c3c070f279e5
| |9a1
--- Comment #7 from Vlad Zahorodnii <vlad.zahorod...@kde.org> ---
Git commit bbb40a9a84200866872ea6726c3c070f279e59a1 by Vlad Zahorodnii.
Committed on 23/01/2024 at 21:05.
Pushed by vladz into branch 'master'.
Fix lingering dpms input event filter after cancelling scheduled dpms mode
change
The output goes through the following stages when it changes its dpms
mode:
- Output::aboutToTurnOff()]
- some time later, Output::dpmsModeChanged() to indicate that it's off
- Output::dpmsModeChanged() to indicate that it's back on
- Output::wakeUp()
The Output::dpmsModeChanged() signals in the middle are optional. They
may not be emitted after Output::aboutToTurnOff() if the user quickly
cancels the dpms mode transition.
The Workspace should monitor the Output::wakeUp() signal instead.
Alternatively, create the dpms input event filter only after the dpms
mode has changed. While the screen won't be turned back on immediately,
it's still going to produce acceptable visuals. Either solution is fine.
This patch makes the Workspace monitor the wakeUp signal because it
takes fewer lines of code.
M +1 -1 src/workspace.cpp
https://invent.kde.org/plasma/kwin/-/commit/bbb40a9a84200866872ea6726c3c070f279e59a1
--
You are receiving this mail because:
You are watching all bug changes.
