Summary: | Powerdevil should wakeup external display after suspend | ||
---|---|---|---|
Product: | [Plasma] Powerdevil | Reporter: | Robert Schetterer <robert> |
Component: | general | Assignee: | Plasma Development Mailing List <plasma-devel> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | justin.zobel, mgraesslin |
Priority: | NOR | ||
Version: | 5.5.4 | ||
Target Milestone: | --- | ||
Platform: | Kubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Robert Schetterer
2016-03-20 09:51:31 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 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. 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 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. |