Compiz crashes on unlocking screensaver

[andypiper]

I'm running Compiz on NVIDIA 185.18.36, Ubuntu 9.10, Thinkpad T61p, 2.6.31-16-generic-pae #52-Ubuntu SMP Thu Dec 3 23:18:13 UTC 2009 i686 GNU/Linux)

If I let the screensaver kick in and the screen get locked, and then go away for a while, *sometimes* compiz.real will crash on unlocking the screen. I haven't yet been able to track down a definite repeatable instance though.

The error in the compiz debug / crash log is:
#0 0xb78ba430 in __kernel_vsyscall ()
#1 0xb7556513 in waitpid () from /lib/tls/i686/cmov/libc.so.6
#2 0xb74f8d03 in ?? () from /lib/tls/i686/cmov/libc.so.6
#3 0xb7611fad in system () from /lib/tls/i686/cmov/libpthread.so.0
#4 0xb54cd3e1 in ?? () from /usr/lib/compiz/libcrashhandler.so
#5 <signal handler called>
#6 0xb6b08154 in ?? () from /usr/lib/libGLcore.so.1
#7 0xb766fd10 in ?? () from /usr/lib/libGL.so.1
#8 0x00000000 in ?? ()

Guess this could be related to X, nvidia driver, compiz, screensaver, rss-glx (I've tried different screensavers), kernel, memory usage... I just don't know :-(

[Luke J Militello (kilahurtz)]

I can also confirm this bug. I have noticed compiz.real crashes with a segfault in libglcore.so while system is under load with the screensaver active. Judging from timestamps within the logs, it appears the crash happens while the screensaver is active rather that upon unlocking it. Again, I only notice this when the system is under load while the screensaver is active.

Key log info line...

Dec 30 09:53:23 Ignignokt kernel: [45441.966650] compiz.real[2560]: segfault at 10 ip 00007f6d50d8fea7 sp 00007fff21528358 error 4 in libGLcore.so.190.42[7f6d501e5000+ecb000]

Some key system info...

version -- ubuntu 9.10 (karmic) [64-bit]
kernel -- 2.6.31-17-generic (also happens on previous kernels)
nvidia driver -- 190.42 (direct from nvidia.com)

[Luke J Militello (kilahurtz)]

Marking this confirmed as I was also able to replicate this on another karmic machine.

[Luke J Militello (kilahurtz)]

This is starting drive me nuts. Always having to close out my open applications, logout and login to fix the issue.

[Nizar (nizarlethif)]

@4: run compiz --replace, atleast you don't have to close out all apps.

[Luke J Militello (kilahurtz)]

Nizar, doesn't help. All I get is just my desktop image, all my windows go away. I still have to logout and log back in to remedy it. Also, this bug only now shows itself because of this bug, #411350, being fixed. Is there any debug commands I can run to assist in a fix? Although not a major concern, this is rather frustrating.

[Luke J Militello (kilahurtz)]

Oh, I also upgraded to kernel 2.6.31-18 and install the most recent drivers from nvidia, 190.53.

[Keith Hughitt (keith-hughitt)]

Confirmed here as well: Ubuntu 9.10 32-bit, 2.6.31-17-generic-pae, nvidia-185, compiz 0.8.4. Crash seems more likely to occur if screen is locked for more than a few minutes. An obvious indicator is that compiz-dependent applications (e.g. Gnome-do) will have crashed as a result.

[Luke J Militello (kilahurtz)]

I'm not 100% sure, but I believe mouse movement has something to do with it all. For the past week or so, I have been waking my machine by hitting the escape key and so far have not had a crash since. If possible, a few others should try this and see what their results are.

[Luke J Militello (kilahurtz)]

Well, it was a long run, but the mouse thing proved irrelevant. Problem started happening again. Really starting to annoy. :( Is there not anyone from the dev team that can setup and help us out?

[Cory Coager (ccoager)]

Having the same problem also. Ubuntu 9.10 64-bit, nvidia-185.18.36-0ubuntu9, 2.6.31-19.56 generic kernel.

[266335.113090] compiz.real[2473]: segfault at 8 ip 00007fc4df2fc583 sp 00007fffe65953e0 error 4 in libGLcore.so.185.18.36[7fc4de80a000+dda000]
[271536.464872] compiz.real[693]: segfault at 8 ip 00007fbd1c6ff583 sp 00007fff8d5144b0 error 4 in libGLcore.so.185.18.36[7fbd1bc0d000+dda000]

[Tronix27 (cedric-neukomm)]

Same problem too.

Ubuntu 9.10 32 bit
Nvidia driver 185.18.36
Kernel 2.6.31-19-generic
Thinkpad T61
Card nVidia Corporation Quadro NVS 140M (rev a1)

Dmesg :
[ 6334.780046] compiz.real[3227]: segfault at 8 ip 019ec2c5 sp bfcb2424 error 4 in libGLcore.so.185.18.36[fa1000+d6f000]

Compiz is also randomly crashing when screen is locked for few minutes.
I haven't found any solutions or workaround yet :-(

[Luke J Militello (kilahurtz)]

There was a recent gnome-screensaver update. Not that it addressed this issue, but I am monitoring to see if I get a crash since then. Terrible to say this, but I am glad more users are seeing this issue. Perhaps now we can get some assistance on a possible workaround and/or fix.

[Luke J Militello (kilahurtz)]

Just had another crash. Could someone PLEASE acknowledge this?

[Travis Watkins (amaranth)]

Having me leave a comment saying "I have no idea why this is happening" doesn't really do much good but sure.

Actually it appears to be crashing inside nvidia's GL library so this is yet another nvidia bug.

[Luke J Militello (kilahurtz)]

Many thanks, Travis!!! Wasn't looking for a fix, just someone knowledgeable on the subject to point us in the right direction. Thanks again!!! :)

[Tronix27 (cedric-neukomm)]

No fix but a kind of workaround solution :

15 days ago, I have set my screensaver's theme to "blank screen" (or something like that, my ubuntu has french language).

Since there, no more compiz crashes after being back in my session. No more dmesg libGLcore messages too.

Hope this could help.

[Cory Coager (ccoager)]

I've always used "blank screen" for screensaver so I can tell you that won't fix the problem.

[Luke J Militello (kilahurtz)]

Now that this problem has been brought to the correct personnel, is it possible to get some assistance with this? I have been plagued by this ever since we got the bug fixed for the screensaver not starting by itself after time out (#411350). If this will be or has been corrected for Lucid it would be nice to know because I'll just upgrade the necessary packages from the Lucid repositories. Thanks in advance!

[Luke J Militello (kilahurtz)]

Any word on this? Anyone?

[Cory Coager (ccoager)]

I'm not so sure this is related to the screensaver. I've had compiz crashes outside the screensaver as well.

[Luke J Militello (kilahurtz)]

Don't want to jinx it, but I haven't had a crash in ten days, and counting...

Not sure, but this directly relates to the upgrade/installation of gnome-screensaver_2.28.0-0ubuntu3.5 on my system.

[Cory Coager (ccoager)]

I'm up-to-date and still having crashes everyday.

[Luke J Militello (kilahurtz)]

Looks like I did jinx it, just had another crash. :( I hope Lucid is not plagued by this...

[Luke J Militello (kilahurtz)]

I'm using driver version 190.53 as well.

[Robbob (rob-kirkbride)]

I'm getting it too. It wouldn't be so bad if I could restart it. Although compiz --replace does restart compiz I lose the gnome title and footer tiles so it's no use. I end up having to do a 'metacity --replace' so I don't have to shutdown all apps, reboot and start them all again.

Using Preferences/Visual Effects doesn't work either - just behaves the same way as compiz --replace.

It seems to have increased in frequency over the last couple of months.

[Phil Bayfield (phil-bayfield)]

I am having the same problem.

I was using the 185 driver initially and have upgraded to 195 which hasn't solved the problem.

I've turned off the screen saver hopefully this will help, it's kinda annoying that I leave my desk for 10 minutes and come back to find all my work is all over the place and Compiz has stopped working!

[Luke J Militello (kilahurtz)]

Perhaps this might help? Ubuntu devs, please read. It looks as though the driver is not at fault.

http://www.nvnews.net/vbulletin/showthread.php?t=144769

[Luke J Militello (kilahurtz)]

Ok, so Lucid is almost out which means Karmic is 1/3 through its life cycle...and still no movement on this. I'm starting to lose faith in this "18 months of support" thing... Not, trying to get on anyone's bad side, but it is very frustrating when you are plagued by a problem such as this, go through all the processes of reporting it and don't get any sort of response or assistance in a possible cause, workaround or solution. :(

[Luke J Militello (kilahurtz)]

See bug: https://bugs.launchpad.net/ubuntu/+bug/425160