compiz freezes x server after screensaver kicks in

Bug #103400 reported by Joe Barnett
18
Affects Status Importance Assigned to Milestone
linux-restricted-modules-2.6.20 (Ubuntu)
Won't Fix
High
Unassigned

Bug Description

Binary package hint: compiz

When running with compiz as the window manager, after returning to my computer after a while, I can not get the machine to wake up from the screensaver. If the screen is blacked out, it will power back on, but the screensaver image will remain on the screen after moving mouse/pressing keyboard. I've seen this on 2 separate machines, both running feisty, both with nvidia gfx cards, both on core 2 duo processors (but one running amd64 os, one running i386 os).

The last time this happened, the screensaver was frozen (appeared all of X was locked up). However, I have also seen where I can move the mouse pointer, but the screensaver does not exit (can't currently remember if the screensaver was frozen or drawing/updating), and no keyboard presses register (pressing num lock doesn't toggle the num lock key light, ctrl+alt+backspace doesn't kill X, for example).

This doesn't happen every time the screensaver kicks in, but does happen reliably often.

I haven't seen this ever happen w/ metacity.

Revision history for this message
Travis Watkins (amaranth) wrote :

This is a suspend problem with the nvidia driver.

Revision history for this message
Joe Barnett (thejoe) wrote :

even though the machine is not going into suspend? (Power Management preferences are set to put the computer to sleep "never")

Revision history for this message
RC Price (robcprice) wrote :

I cannot get my 7.04 amd core2 duo with nvidia to recover from screensaver if any screensaver is active for more than about five minutes. The image freezes and the only action available is reboot. Happens every time. Does anyone have any suggestions?

Revision history for this message
Warren Butler (grumpymole) wrote :

AMD Athlon XP 1600+ processor and GeForce FX5200 showing similar problems.

Currently, I am running beryl and I think I found a trend in my case. See if you can replicate it.

If I add any more applets to the panel at the top, then I find that the machine will go to blank screen and never come out again. I have the exit applet, the date and time applet, the peaker applet, and the NM applet (all standard form install). Also, I have the Beryl ruby icon and an icon for Gaim (or Pidgin). See attachment.

After a fresh install, everything was fine. Until I added the weather applet. It started freezing regularly. I removed the applet and it went through the night no problem. An update came through and the update icon seemed to trigger another freeze. Then fine since then.

I'll do some more testing to try and get more scientific about it.

Revision history for this message
Bryce Harrington (bryce) wrote :

Could you please test this against Gutsy tribe-4, and see if it still occurs?

If it does, I have packaged the latest -nvidia here: http://people.ubuntu.com/~bryce/Testing/linux-restricted-modules/
Could you please test if the issue remains when this is installed?

Changed in linux-restricted-modules-2.6.20:
status: New → Incomplete
Revision history for this message
Joe Barnett (thejoe) wrote :

just tested against latest in gutsy, and it still occurs. Latest gutsy has nvidia 100.14.11 and a new kernel abi (-10), so I didn't test against the ~bryce packages which are built against -9.

Changed in linux-restricted-modules-2.6.20:
status: Incomplete → New
Bryce Harrington (bryce)
Changed in linux-restricted-modules-2.6.20:
importance: Undecided → High
status: New → Confirmed
Revision history for this message
Jamie Strandboge (jdstrand) wrote :

I just tested this with latest gutsy as of today. IBM T42 with ATI Radeon 7500. Coming out of screensaver I was presented with a blank white screen.

Revision history for this message
Jai Singh (i922sparkcir) wrote :

This happens to me on my intel machine. Dell 700m, Pentium M, Intel 855 Graphics.

Revision history for this message
Bryce Harrington (bryce) wrote :

Jai, your issue is likely unrelated to the one described in this bug report since you're using the -intel driver, whereas this bug describes an nvidia proprietary driver issue.

Revision history for this message
Martin Capitanio (capnm) wrote :

Here similar happen (on any computer and every time)
Wenn recover from screensaver and after switching user
there is nothing (=white screen)

ctrl+alt+F1 & killall compiz.real
makes the screen accesible again.

Revision history for this message
Retromingent (ray-rwalk2730) wrote :

I am experiencing the same symptom, too: after the screen saver kicks in, the unlock password prompt takes minutes to appear. (I can create the same symptom just with "screen lock" and then attempting to unlock the screen.)
I see that compiz.real is running 100% CPU during the attempt to unlock. (I observe this by switching over with ctrl-alt-F1 and watching "top".) I am running Gutsy with the nvidia restricted driver.

Revision history for this message
Dave Vree (hdave) wrote :

I can also confirm this. Running Gutsy on a Dell XPS M1210 laptop with an Nvidia GEForce 7400.

If the screen saver is on less than 10 minutes I am fine. If more than 4 hours...the system will be frozen when I get back every single time.

Revision history for this message
h3 (h3) wrote :

Having the same problem with a Athlon X2 64 with a NVIDIA quadro fx card.

Everything works fine except when I leave the computer idle for a long period (+1h). When I come back both screens are white but I can still move the cursor.

Workaround found:

I change TTY (ctrl+alt+f1) and kill compiz from command line, which is taking 100% of my CPU. Then I switch back to graphical interface and re-enable desktop effect..

If someone need more infos on my system just give me the command to execute, I'll provide the infos.

Revision history for this message
ichudov (igor-chudov) wrote :

Exact same bug happens to me. It is VERY easy to reproduce:

A) wait until screensaver kicks in

or

B) Just close the lid of my laptop

-- and the screen freezes hard. Even Ctrl-Alt-Backspace does not work.

However, Linux itself is running, I can ssh to this server, etc.

Turning off nvidia proprietary driver fully fixes the problem.

Revision history for this message
kelvalok (kelvalok) wrote :

Here the same than ichudov (only A, it's not a notebook), from Kubuntu 7.10, and after upgrade the version to 8.04 it still freezes.
Turning off nvidia driver it doesn't freeze any more, and i can have my computer turn on for days!
My computer: Motherboard Gigabyte 965P-S3, Intel core duo 4300, sata 160Gb, dvd ide, nvidia 7600 gt pci-express 256Mb, 2Gb RAM.
It would be great if someone could say when we can use again this driver or another one.
Thanks for all.

Revision history for this message
Bryce Harrington (bryce) wrote : linux-restricted-modules-2.6.20 is obsolete

This package has become obsolete so we're closing out the bug report as WONTFIX.
Thanks for reporting it though!

Changed in linux-restricted-modules-2.6.20:
status: Confirmed → Won't Fix
Revision history for this message
Tuomas Heino (iheino+ub) wrote :

Reproduced this issue with linux-restricted-modules-2.6.28-14-generic on up-to-date Jaunty (with 8600gts, 8 gigs amd64).

System didn't seem to respond to keyboard input besides num/caps-lock, but I could switch to another user account with mouse.
Workaround: Switching away from the session and then back to the user account with the problem (and thus re-unlocking screensaver) seems to fix the symptoms.

Looks like a race condition - seen only once with this computer so far, and not with Hardy/Intrepid.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.