Bug 744796 - Starting Gnome-shell from KDM causes screen corruption
Summary: Starting Gnome-shell from KDM causes screen corruption
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 16
Hardware: i386
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-10 13:54 UTC by Daniel Belton
Modified: 2012-03-22 21:22 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-22 21:22:28 UTC
Type: ---


Attachments (Terms of Use)
screen shot of corrupted screen (4.16 MB, image/png)
2011-10-10 13:54 UTC, Daniel Belton
no flags Details
xsession-errors file (9.23 KB, application/octet-stream)
2011-10-10 13:54 UTC, Daniel Belton
no flags Details

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 .


Note You need to log in before you can comment on or make changes to this bug.