https://bugs.kde.org/show_bug.cgi?id=485085
--- Comment #15 from kdeb...@toeai.com --- If it's really a race, as Steve Vialle indicates, then one's inability to reproduce is of no consequence; only one's ability to reproduce would be of consequence. The only indication that it has indeed been fixed is to point to code that was changed. While Steve Vialle's workaround is a help to those who experience the problem the most, it isn't ultimately a way of fixing things. What we need is a guarantee that the screen has in fact been redrawn/repainted, and only then sleep the system. per comment 13: > I did notice it happening also there, just way quicker than in Xorg and not > always, therefore probably not looking as bad an issue, but still existing. That's consistent with a race condition. As for "not looking as bad" on Wayland, that is of course relative. Anyone actively exploiting this security/privacy bug could use a camera and then take as much time as he likes to read the screen. And, given this report, the bug's current title "On X11, ..." and keyword "X11-only" are wrong and should be changed. And of course, once fixed, the wording of the settings should be changed from "Lock after waking" to "Lock before sleeping". -- You are receiving this mail because: You are watching all bug changes.
