FS#50233 - powersave HDMI monitor wake-up bug after update to xf86-video-intel

Attached to Project: Arch Linux
Opened by Mike Cloaked (mcloaked) - Tuesday, 02 August 2016, 19:13 GMT
Last edited by Doug Newgard (Scimmia) - Wednesday, 03 August 2016, 13:26 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

After update xf86-video-intel 1:2.99.917+676+g26f8ab5-1 -> 1:2.99.917+688+g49daf5d-1 when running plasma and allowing the HDMI connected monitor to enter energy saving mode after a typical 10 minute timeout period, the monitor goes blank as expected - but if the mouse is moved, or a key such as shift is pressed the monitor does not come out of powersave, but stays off. Using ctrl-alt-F3 brings the screen back on, and then ctrl-alt-F1 brings back the screensaver password display to then return to normal working.

Downgrading to xf86-video-intel 1:2.99.917+676+g26f8ab5-1 brings back correct operation, and allows the monitor to wake up from powersave using a mouse movement or hitting the shift key.

Additional info:
* package version(s)

xf86-video-intel 1:2.99.917+688+g49daf5d-1 seems to have this regression bug.

* config and/or log files etc.


Steps to reproduce:
Update to xf86-video-intel 1:2.99.917+688+g49daf5d-1 - monitor will no longer wake up from powersave mode.
Downgrade to xf86-video-intel 1:2.99.917+676+g26f8ab5-1 - monitor will again wake up from powersave mode using the mouse or hitting a key.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Wednesday, 03 August 2016, 13:26 GMT
Reason for closing:  Fixed
Comment by Mike Cloaked (mcloaked) - Wednesday, 03 August 2016, 07:48 GMT
After a slew of updates last night including plasma-workspace (5.7.2-2 -> 5.7.3-1) this issues seems to have been resolved so the package xf86-video-intel 1:2.99.917+688+g49daf5d-1 now works with the latest plasma packages again. So I will request closure of this bug.

Loading...