https://bugs.kde.org/show_bug.cgi?id=480026
akedrou <aked...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |aked...@gmail.com
--- Comment #25 from akedrou <aked...@gmail.com> ---
As mentioned above a Dell monitor's auto-input select requires a longer trigger
to stop the system from waking (e.g. my monitor seems to take ~17 seconds from
the power off message: 10 to start the scan and another 7 to test the inputs).
Is it reasonable to increase the timeout here further? I'm not sure users would
find it too surprising if they unplug a monitor and plug it in again within
even 30 seconds of it going to sleep that it doesn't trigger the screens to
reset, but I do see how that kind of delay starts risking confusion.
Also, the fix to not notify on the warp event seems to keep the screen lock
timer going and prevents other monitors from waking, but the system never
sleeps, so it seems the event isn't completely filtered. Is that managed
elsewhere?
The auto input select fixed my issue in the end, but it did take a ton of
investigation to get to the cause so if it's reasonable/uncontroversial enough
to change I could with some pointers (or would be happy if someone else wanted
to).
--
You are receiving this mail because:
You are watching all bug changes.
