compiz crashed with SIGSEGV in nux::WindowThread::GetTimerHandler()

[Stephen Rees-Carter]

I came back to my laptop after being away for 30 mins to find black screens. The lock screen wouldn't appear, and I was forced to use Ctrl+Alt+F2, and the run unity --replace &. This didn't actually fix the problem, and I had to run service lightdm restart.

I haven't found away to trigger this on demand, it just happens sometimes.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: libnux-3.0-0 3.6.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4
Uname: Linux 3.5.0-15-generic x86_64
ApportVersion: 2.5.2-0ubuntu4
Architecture: amd64
Date: Fri Sep 28 16:12:28 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120914)
ProcCmdline: compiz --replace
SegvAnalysis:
 Segfault happened at: 0x7f293a3d4460 <_ZNK3nux12WindowThread15GetTimerHandlerEv>: mov 0x190(%rdi),%rax
 PC (0x7f293a3d4460) ok
 source "0x190(%rdi)" (0x00000190) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nux
StacktraceTop:
 nux::WindowThread::GetTimerHandler() const () from /usr/lib/libnux-3.0.so.0
 nux::NuxTimerTickSource::~NuxTimerTickSource() () from /usr/lib/compiz/libunityshell.so
 unity::UnityScreen::~UnityScreen() () from /usr/lib/compiz/libunityshell.so
 unity::UnityScreen::~UnityScreen() () from /usr/lib/compiz/libunityshell.so
 CompManager::finiPlugin(CompPlugin*) () from /usr/lib/libcompiz_core.so.ABI-20120920
Title: compiz crashed with SIGSEGV in nux::WindowThread::GetTimerHandler()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers www-data

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1054074, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.