Bug 375531 - Reactivate Monitor after powersave takes extremely long
Summary: Reactivate Monitor after powersave takes extremely long
Status: RESOLVED UPSTREAM
Alias: None
Product: KScreen
Classification: Plasma
Component: kded (other bugs)
Version First Reported In: 5.8.2
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Sebastian Kügler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-25 07:33 UTC by Pit
Modified: 2017-02-06 18:12 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
xsession-errors during wakeup (728 bytes, application/x-xz)
2017-01-25 07:33 UTC, Pit
Details
output from journalctl during wakeup (1.62 KB, application/x-xz)
2017-01-25 07:34 UTC, Pit
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Pit 2017-01-25 07:33:28 UTC
Created attachment 103628 [details]
xsession-errors during wakeup

If the computer is unused, the screen is blanked after a while and the monitor goes to power save mode.
If I then move the mouse and/or hit a key on the keyboard, it takes roughly 15s before I can see my desktop:  The monitor power first goes on, but the screen stays black.  After some 8-10s the monitor goes back into powersave mode, and only after 15 s it powers on again to show my desktop.  I have not seen this before.
The Monitor is a Dell P2415Q (4k) Monitor, the graphics card an NVidia GTX 1060 6GB (GP106-A) using driver version 375.26
Attached is the
Comment 1 Pit 2017-01-25 07:34:41 UTC
Created attachment 103629 [details]
output from journalctl during wakeup
Comment 2 Pit 2017-01-25 07:37:00 UTC
(sorry, hitting return sent the report before I was finished)
I'm attaching the relevant parts of ~/.xsession-errors and the journalctl syslog during the wakeup phase that shows a lot activity from kded, xcb-helper and xrandr modules.
Comment 3 Sebastian Kügler 2017-02-06 18:12:33 UTC
This smells a lot like a driver / monitor thing, so it's not something we can do anything about. Sorry to break that news for you, but unless this is a problem more common (meaning people with different hardware setups can reproduce), I'll file that as a upstream problem.