compiz crashed with SIGSEGV in nux::WindowThread::GetTimerHandler()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nux (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Hello.
Just tried to enable the Gnome compatibility plugin back.
Well, truth be told, every time I try to enable any plugin or revert all the settings via CCSM, Compiz crashes.
I bet everything is in the logs, but I got Ubuntu 12.10 on Asus eeepc 1015PED with all recent updates.
Description: Ubuntu quantal (development branch)
Release: 12.10
Linux 3.5.0-15-generic #22-Ubuntu SMP Wed Sep 19 20:01:43 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
compiz:
Installed: 1:0.9.8.
Candidate: 1:0.9.8.
Version table:
*** 1:0.9.8.
500 http://
100 /var/lib/
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: libnux-3.0-0 3.6.0-0ubuntu1
ProcVersionSign
Uname: Linux 3.5.0-15-generic x86_64
NonfreeKernelMo
ApportVersion: 2.5.2-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Sun Sep 23 00:26:46 2012
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120201.1)
ProcCmdline: compiz
SegvAnalysis:
Segfault happened at: 0x7f8aa8188460 <_ZNK3nux12Wind
PC (0x7f8aa8188460) 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::WindowThr
nux::NuxTimerT
unity:
unity:
CompManager:
Title: compiz crashed with SIGSEGV in nux::WindowThre
UpgradeStatus: Upgraded to quantal on 2012-09-14 (8 days ago)
UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo wireshark
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.