Bug 748951

Summary: Resume of gnome-shell after removing one of two displays corrupts display
Product: [Fedora] Fedora Reporter: Brian G. Anderson <bikehead>
Component: gnome-shellAssignee: Owen Taylor <otaylor>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 16CC: beland, browning48ky, maxamillion, otaylor, samkraju, walters
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-11 18:54:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Brian G. Anderson 2011-10-25 16:39:10 UTC 
Description of problem:
I have a Dell 6410 laptop with intel Arrandale graphics (i915?) and a docking station with a large screen monitor.  When I attach dock the laptop, the second display is selected and gnome-shell shows the desktop across both screens (yay!).  However it puts the activities bar on the smaller laptop display so I reconfigure gnome-shell to choose the larger display for the activity bar (I use the displays settings to temporarily remove the laptop screen which forces the activity bar to the secondary screen and then I re-enable the laptop screen).  Now every time I dock the laptop it will detect the second screen and put the activities bar on the larger screen.

However,  if I suspend the laptop and undock it and then resume it undocked or docked in another location but with no second display, the gnome-shell will resume but the display will be corrupted (screen flickering,  flashing small back lines, and general corruption).  It may or may not be accepting input, but I can tell since the screen is corrupted.  I can ssh into the system and it works fine, but I cannot reset the display:  switching to a console, killing X, using systemctl to go to multi-user mode all don't work.  The display is corrupted even in console mode.

The funny thing is that if I don't move the activities bar to the second display, I can resume fine with no display problems:  in the undocked resume gnome-shell correctly detects that I have only one screen and moves all windows on to it.  I *suspect* it is the placement of the activities bar that is causing the problem.

There are no errors in .xsession-errors or in the log as far as I can see.

I am fully up-to-date on dell BIOS A10.

Version-Release number of selected component (if applicable):
gnome-shell-3.2.1-1.fc16.x86_64
kernel-3.1.0-1.fc16.x86_64
xorg-x11-drv-intel-2.16.0-2.fc16.x86_64

How reproducible:
Every time

Steps to Reproduce:
1. See above
2.
3.
  
Actual results:
Corrupted display

Expected results:
Proper resume

Additional info:
The corruption occurs over the 2.3x kernels too.  This behaviour occurs in F15 also.
Comment 1 Fedora End Of Life 2013-01-16 16:23:19 UTC 
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 2 Christopher Beland 2013-02-11 18:54:55 UTC 
The same bug is seen in Fedora 18 and has been reported separately.  Since F16 is near EOL, arbitrarily marking this as a duplicate and linking it.

*** This bug has been marked as a duplicate of bug 902316 ***