[apport] compiz.real crashed with SIGSEGV (during screensaver or power state change?)

[hobie20dude]

Binary package hint: compiz

This is a new core2 duo machine with 965g chipset (x3000 integrated graphics).
Feisty herd 5 install with current updates. as of the reporting (march 25 2007)
Desktop effects is enabled. (not sure if that is obvious from the fact that the crash was in compiz)
Screensaver was set to random, "put display to sleep" and "put computer to sleep" both enabled.

This happened while the screensaver was active. I walked back to a black unresponsive display. Neither mouse nor keyboard would bring it back. <ctrl><alt><f[1-6]> did not bring up a virtual console. I ended up with the reset button.

I suspect the screensaver only because I previously (single digit hours in the past) had the computer lock similarly and show one of the screensavers + some garbage on the screen.

I don't know the time so I can't rule out power save activation causing this. I had "put display to sleep" and "put computer to sleep" both active at the time.

I have set the screensaver to blank and disabled "put computer to sleep" and have not seen this recur. I'll experiment a bit when I get time and add new information if I get it.

ProblemType: Crash
Architecture: i386
Date: Sun Mar 25 15:53:05 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/compiz.real
Package: compiz-core 1:0.3.6-1ubuntu8
PackageArchitecture: i386
ProcCmdline: /usr/bin/compiz.real --no-fbo --sm-client-id default0 gconf gconf
ProcCwd: /home/dave
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: compiz
Stacktrace: #0 0x08053260 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:

Uname: Linux catamaran 2.6.20-12-generic #2 SMP Wed Mar 21 20:55:46 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

[Apport retracing service (apport)]

StacktraceTop:

[Travis Watkins (amaranth)]

I believe this was a bug in the inotify plugin that has since been fixed.