https://bugs.kde.org/show_bug.cgi?id=440639
Aldoo <aldo-pub...@laposte.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |aldo-pub...@laposte.net
--- Comment #2 from Aldoo <aldo-pub...@laposte.net> ---
I am pretty sure I have this bug since way longer than a couple of months (much
like several years, I think).
Also, there is the "reverse" reproduction: use your laptop unplugged, put it to
sleep, plug it to an external monitor while asleep, then wake it up.
In this case, often (not always), one of the screens will be black. Also there
are focusing issues, making the password hard to enter (not going more into
details, as this deserves a separate bug report).
Since this is an old ongoing bug, I assume the resolution is probably
difficult, and probably hardware dependent (by the way, like the opener, I use
an Intel integrated GPU: Mesa Intel(R) UHD Graphics (CML GT2) (0x9bca)).
Maybe, until there is a proper fix, a workaround could be provided, making it
easy to restart kscreenclocker when it is not usable? (I don't know, maybe a
"panic" key combo of some sort, that does not require to switch to some other
virtual terminal)
Also, is there no way for kscreenlocker to detect that the screen is currently
black?
--
You are receiving this mail because:
You are watching all bug changes.
