Description of problem:
I'm using T500 in dock connected to an external display, dual head in span mode. In rhel6.1 when I closed the lid, the screen conf. changed - Laptop display was disconnected I had only external display active. After opening the lid I got span mode again.
This doesn't work in rhel6.2 anymore, when I close the lid, laptop screen is still on and desktop is still in span mode, i.e. I have some windows on the closed laptop screen .
Also when I manually turn the laptop screen off and then open the lid, screen is still off.
Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller
[8086:2a42] (rev 07)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. log into desktop session using span mode
2. close the laptop lid
3. open the laptop lid
screen conf. doesn't change
closing/opening the lid should trigger change in screen conf.
So. The X server no longer proxies lid state into output connectivity, because doing so caused resume failures. The session does listen for lid events, but does not inspect lid state itself. gnome-power-manager implements two possible states where the lid can be closed but the system stays running: "Do Nothing", and "Blank Screen". Do Nothing does indeed do nothing; it does not update the screen configuration to be external-only. Blank Screen does indeed blank the screen, which blanks both screens, which isn't horribly useful.
So the problem is deciding where to fix this. The server apparently ought not look at lid state. We could change that and reintroduce some resume failures. Or we could patch Gnome to have Do Nothing not do nothing. Both are kind of ugly.
After some digging, it's not as dire as I'd thought.
The resume failure I noted above turns out to be a rather subtle deadlock in gnome-screensaver, triggerable with the lid state proxy patch applied (but theoretically possible to trigger in other scenarios). I have a patch which resolves this deadlock, though it still needs review from the screensaver maintainer since for all I know it could have security implications.
Once that's merged, I believe we can re-merge the lid state proxy, at which point this bug will probably be fixed.
*** Bug 747005 has been marked as a duplicate of this bug. ***
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.