Bug 360766 - Powerdevil should wakeup external display after suspend
Summary: Powerdevil should wakeup external display after suspend
Status: RESOLVED FIXED
Alias: None
Product: Powerdevil
Classification: Plasma
Component: general (show other bugs)
Version: 5.5.4
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Development Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-20 09:51 UTC by Robert Schetterer
Modified: 2020-11-13 06:46 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Schetterer 2016-03-20 09:51:31 UTC
reported
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555078

I did a xrandr workaround with systemd.

What happen is:
closing lid of docked thinkpad laptop works as configured to suspend in kde.
At resume the external display does not wake up auto. ( xrandr systemd workaround is possible with one external display attached, it does not work well when two external displays are attached ). But i noticed if if wait 10 mins after open lid and resume ( not login ) the prime laptop display
does brightness control as configured too in KDE ( went black ). Suprise when now touching laptop pad
the prime laptop display brightness comes up again with login screen and is also shown suddenly 
very fast on external display ( resume is much faster then with xrandr ). This should be the default by first resume action too ! So the question is ,how to wake up external display at first resume just like as its done when wakeup from configured brightness control time.

Reproducible: Always

Steps to Reproduce:
1.configure kde suspend also when external display does exist with closing lid
2.resume ( means open lid ,secondary display does not wake up ), do not login , wait default 10 mins prime laptop display goes black, wait again a few mins.
3. Now touch mouse etc both displays show login screen very fast


Expected Results:  
external attached displays should be resumed ever just like prime display
Comment 1 Robert Schetterer 2016-03-20 09:55:52 UTC
some debug lines

CreateNotify: 29360141
MapNotify: 29360141
CreateNotify: 29360144
MapNotify: 33554469
powerdevil: Screen brightness value:  0
powerdevil: Brightness changed!!
powerdevil: Screen brightness value max:  852
powerdevil: Kbd backlight brightness value:  0
powerdevil: Can't contact ck
powerdevil: set screen brightness value:  767
powerdevil: Screen brightness value:  0
ktp-kded-module: 
powerdevil: Screen brightness value:  767
powerdevil: Brightness changed!!
powerdevil: Screen brightness value max:  852
powerdevil: Screen brightness value:  767
powerdevil: Brightness changed!!
powerdevil: Screen brightness value:  767
powerdevil: Brightness changed!!
UnmapNotify: 29360138
UnmapNotify: 29360138
UnmapNotify: 29360141
UnmapNotify: 29360141
QXcbConnection: XCB error: 3 (BadWindow), sequence: 65316, resource id: 29360138, major code: 2 (ChangeWindowAttributes), minor code: 0
CreateNotify: 29360146
QXcbConnection: XCB error: 3 (BadWindow), sequence: 65340, resource id: 29360146, major code: 18 (ChangeProperty), minor code: 0
kscreen: Primary output changed from KScreen::Output(Id: 67 , Name: "eDP1" ) ( "eDP1" ) to KScreen::Output(Id: 67 , Name: "eDP1" ) ( "eDP1" )
Grab Released
kscreen: Primary output changed from KScreen::Output(Id: 67 , Name: "eDP1" ) ( "eDP1" ) to KScreen::Output(Id: 67 , Name: "eDP1" ) ( "eDP1" )
kscreen: Primary output changed from KScreen::Output(Id: 67 , Name: "eDP1" ) ( "eDP1" ) to KScreen::Output(Id: 67 , Name: "eDP1" ) ( "eDP1" )
ktp-kded-module: 
kscreen.kded: Change detected
kscreen: Primary output changed from KScreen::Output(Id: 67 , Name: "eDP1" ) ( "eDP1" ) to KScreen::Output(Id: 67 , Name: "eDP1" ) ( "eDP1" )
kscreen.kded: Saving current config to file
kscreen.kded: Calculating config ID for KScreen::Config(0x2393e00)
kscreen.kded:   Part of the Id:  "3032f4cf9362cfbbe8f2ac54b6a4457a"
kscreen.kded:   Part of the Id:  "67e17eea79209d5f452f39568a86117e"
kscreen.kded:   Config ID: "f2113b76caeab28562af824abe643326"
kscreen.kded: Config saved on:  "/home/rschetterer/.local/share/kscreen/f2113b76caeab28562af824abe643326"
Created alarm 23068690
powerdevil: Screen brightness value:  767
powerdevil: Screen brightness value:  767
powerdevil: Kbd backlight brightness value:  0
powerdevil: Can't contact ck
powerdevil: set screen brightness value:  384
powerdevil: Screen brightness value:  767
powerdevil: Screen brightness value:  384
powerdevil: Brightness changed!!
powerdevil: Screen brightness value max:  852
powerdevil: Screen brightness value:  384
powerdevil: Can't contact ck
powerdevil: set screen brightness value:  96
powerdevil: Screen brightness value:  384
powerdevil: Screen brightness value:  96
powerdevil: Brightness changed!!
powerdevil: Screen brightness value max:  852
powerdevil: Screen brightness value:  96
powerdevil: Can't contact ck
powerdevil: set screen brightness value:  0
powerdevil: Screen brightness value:  96
powerdevil: Can't contact ck
lock called
Lock window Id:  33554475
Created alarm 33554477
CreateNotify: 33554475
CreateNotify: 29360131
CreateNotify: 29360135
CreateNotify: 29360137
CreateNotify: 29360138
CreateNotify: 29360139
MapNotify: 29360138
CreateNotify: 29360141
MapNotify: 29360141
CreateNotify: 29360144
MapNotify: 33554475
powerdevil: Screen brightness value:  0
powerdevil: Brightness changed!!
powerdevil: Screen brightness value max:  852
powerdevil: Kbd backlight brightness value:  0
libkcups: Renew-Subscription last error: 0 successful-ok
libkcups: Get-Jobs last error: 0 successful-ok
libkcups: Get-Jobs last error: 0 successful-ok
libkcups: 0
libkcups: 0
powerdevil: Can't contact ck
powerdevil: set screen brightness value:  767
powerdevil: Screen brightness value:  0
ktp-kded-module: 
powerdevil: Screen brightness value:  767
powerdevil: Brightness changed!!
powerdevil: Screen brightness value max:  852
powerdevil: Screen brightness value:  767
powerdevil: Brightness changed!!
powerdevil: Screen brightness value:  767
powerdevil: Brightness changed!!
Created alarm 23068691
powerdevil: Screen brightness value:  767
powerdevil: Screen brightness value:  767
powerdevil: Kbd backlight brightness value:  0
powerdevil: Can't contact ck
powerdevil: set screen brightness value:  384
powerdevil: Screen brightness value:  767
powerdevil: Screen brightness value:  384
powerdevil: Brightness changed!!
powerdevil: Screen brightness value max:  852
powerdevil: Screen brightness value:  384
powerdevil: Brightness changed!!
powerdevil: Screen brightness value:  384
powerdevil: Brightness changed!!
powerdevil: Screen brightness value:  384
powerdevil: Can't contact ck
powerdevil: set screen brightness value:  96
powerdevil: Screen brightness value:  384
powerdevil: Screen brightness value:  96
powerdevil: Brightness changed!!
powerdevil: Screen brightness value max:  852
Created alarm 33554478
powerdevil: Screen brightness value:  96
powerdevil: Can't contact ck
powerdevil: set screen brightness value:  0
powerdevil: Screen brightness value:  96
powerdevil: Screen brightness value:  0
powerdevil: Brightness changed!!
powerdevil: Screen brightness value max:  852
Comment 2 Martin Flöser 2016-03-21 07:10:52 UTC
I think that's outside the scope of powerdevil. Waking up the connected outputs is something the windowing system (e.g. X11, KWin_Wayland) needs to do. Powerdevil has no control over dpms, that's on X11 completely handled inside X11, it doesn't know whether the screen is on, whether dpms is in and has no way to end it.

If the problem is also present on KWin_Wayland the bug can be reassigned to KWin, for X11 it's outside the scope of our software stack.
Comment 3 Robert Schetterer 2016-03-21 16:41:01 UTC
Hi Martin, thx for info
i come up with powerdevil cause there is less more depend log info, i will try file the bug to
X11, KWin_Wayland
Regards
Comment 4 Justin Zobel 2020-11-12 22:53:05 UTC
Robert I've just tested this with Wayland on my Dell Inspiron and both displays wake up on resume.

I haven't tested on x11 though.

Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I'm setting status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks.