Bug 9531

Summary: Ctl-Alt-F1 and back again crashes compiz
Product: xorg Reporter: kronheim
Component: App/compizAssignee: David Reveman <reveman>
Status: RESOLVED NOTOURBUG QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: high    
Version: 7.1 (2006.05)   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
Screenshot of garbled screen none

Description kronheim 2007-01-03 16:47:33 UTC 
Using compiz 0.3.6 with gtk-window-decorator, start a session and then do:

1. Ctl-Alt-F1 to get to a terminal screen.
2. Ctl-Alt-F7 to get back to X.

The result here is that compiz usually crashes. Sometimes, compiz is still
running but the screen is garbled (screenshot to be attached). I am starting
compiz using the command line:

__GL_YIELD="NOTHING" compiz --replace gconf 

I am not using xgl; I am using nvidia with the driver version 9631. This is 100%
reproducible on my machine. Without compiz, steps 1 and 2 above produce no problems.

The same issue occurs with using the "Fast User Switch" applet in the gnome
panel to switch between sessions.
Comment 1 kronheim 2007-01-03 16:49:01 UTC 
Created attachment 8289 [details]
Screenshot of garbled screen

In this screenshot, compiz is alive still. But note the garbled screen where
the gnome panels should be. Often compiz crashes at this point.
Comment 2 kronheim 2007-01-03 20:04:41 UTC 
On the mailing lists, I saw the bug described as an nvidia driver issue. This
may be, but beryl manages to avoid the problem.
Comment 3 Treviño 2007-02-08 09:15:52 UTC 
In my PC I've a linked problem... If I've opened many windows, I simply don't come back with ctrl+alt+f7... I get a blank window and X freezes... The only "fix" is restarting my PC. This is really a problem for me especially using suspend2 :(
Comment 4 Daniel Stone 2007-02-27 01:35:29 UTC 
Sorry about the phenomenal bug spam, guys.  Adding xorg-team@ to the QA contact so bugs don't get lost in future.
Comment 5 Danny Baumann 2007-09-25 00:54:27 UTC 
This is an issue in the Nvidia drivers which should be solved by version 100.14.19.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.