compiz crashed with SIGSEGV in LauncherHoverMachine::SetQuirk()

Bug #761144 reported by Christopher Dönselmann-Theile
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
unity (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: unity

same old bug while switching profiles in ccsm

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: unity 3.8.6-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
CrashCounter: 1
Date: Thu Apr 14 23:05:47 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110402)
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=de:C:en
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x11e21f8 <_ZN20LauncherHoverMachine8SetQuirkENS_10HoverQuirkEb+104>: or %edi,0x14(%esi)
 PC (0x011e21f8) ok
 source "%edi" ok
 destination "0x14(%esi)" (0x039c3bd4) in non-writable VMA region: 0x02c83000-0x04336000 r-xp /usr/lib/nvidia-current/libnvidia-glcore.so.270.30
SegvReason: writing VMA /usr/lib/nvidia-current/libnvidia-glcore.so.270.30
Signal: 11
SourcePackage: unity
StacktraceTop:
 LauncherHoverMachine::SetQuirk(LauncherHoverMachine::HoverQuirk, bool) () from /usr/lib/compiz/libunityshell.so
 Launcher::SetStateMouseOverBFB(bool) () from /usr/lib/compiz/libunityshell.so
 Launcher::OnBFBUpdate(_GVariant*, void*) () from /usr/lib/compiz/libunityshell.so
 ?? () from /usr/lib/compiz/libunityshell.so
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: compiz crashed with SIGSEGV in LauncherHoverMachine::SetQuirk()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Christopher Dönselmann-Theile (sir-theile) wrote :
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.