| Summary: | Black screen with cursor when resuming from sleep with a different display configuration | ||
|---|---|---|---|
| Product: | [Unmaintained] kscreenlocker | Reporter: | Simone Gaiarin <simgunz> |
| Component: | general | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | aldo-public, bshah, nate, plasma-bugs-null |
| Priority: | HI | Keywords: | regression |
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Simone Gaiarin
2021-08-05 17:25:17 UTC
I started noticing the problem in the last 1-2 months. 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? Also probably related to Bug #436590 (about greeter not resizing on display configuration change: which probably share the same root cause, i.e. kscreenlocker is not aware of the change or does not react to it). Ah and Bug #412527 is also almost the same problem. The three bugs are probable duplicates or symptoms of the same bug. *** This bug has been marked as a duplicate of bug 412527 *** |