Bug 744796

Summary: Starting Gnome-shell from KDM causes screen corruption
Product: [Fedora] Fedora Reporter: Daniel Belton <danielbelton>
Component: gnome-shellAssignee: Owen Taylor <otaylor>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 16CC: browning48ky, maxamillion, otaylor, samkraju, walters
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-22 21:22:28 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
screen shot of corrupted screen
none
xsession-errors file none

Description Daniel Belton 2011-10-10 13:54:12 UTC
Created attachment 527241 [details]
screen shot of corrupted screen

Description of problem: Corrupted screen when starting Gnome-shell from KDM

Version-Release number of selected component (if applicable):

gnome-shell 3.2.0-2
kdm 4.7.2-1
xorg-x11-drv-nouveau 1.0.0.16-27.20110720gitb806e3f.fc16

How reproducible:

Set login manager to KDM and login to gnome-shell

Steps to Reproduce:
1. Change login manager to KDM instead of the default GNOME
2. Login using KDM, selecting Gnome as the desktop environment
3. Corrupted screen appears, then corrects itself when Gnome is fully loaded
  
Actual results:

Corrupted screen appears 

Expected results:

No screen corruption, and a smooth transition from KDM to Gnome. 

Additional info:

I am not certain if this bug should have been filed under Gnome-shell, KDM or nouveau (the video driver I an using).

Video adapter, Nvidia G73 GeForce 7300 GT

Comment 1 Daniel Belton 2011-10-10 13:54:54 UTC
Created attachment 527242 [details]
xsession-errors file

Comment 2 Daniel Belton 2012-03-22 21:21:59 UTC
Closing this one. No responses from the developer/packager, and the issue seems to have been corrected or fixed. I no longer see the corruption .