compiz crashed with SIGSEGV in nux::NTextureData::ClearData()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nux (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
May possibly be related to bug 952378.
I just finished installing updates a few minutes ago and rebooted. After I signed back in, the desktop and unity bar appeared. I thought things were 'done loading', so I clicked on the terminal icon I added to the unity bar. The unity bar and all the desktop icons immediately disappeared leaving me with just my desktop background. They reappeared a few seconds later with a notification that compiz crashed.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: libnux-2.0-0 2.10.0-0ubuntu1
ProcVersionSign
Uname: Linux 3.2.0-23-generic x86_64
ApportVersion: 2.0.1-0ubuntu4
Architecture: amd64
Date: Tue Apr 17 09:18:11 2012
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: compiz
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7fd2e35ee805: cmp 0x18(%rdx),%r12
PC (0x7fd2e35ee805) ok
source "0x18(%rdx)" (0x320000800023e1c) not located in a known VMA region (needed readable region)!
destination "%r12" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nux
StacktraceTop:
?? () from /lib/x86_
?? () from /lib/x86_
nux::NTextureD
nux::NTextureD
nux::Texture2D
Title: compiz crashed with SIGSEGV in nux::NTextureDa
UpgradeStatus: Upgraded to precise on 2012-02-27 (50 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare
XsessionErrors:
gnome-
gnome-
(compiz:2525): GConf-CRITICAL **: gconf_client_
gnome-
(compiz:2567): GConf-CRITICAL **: gconf_client_
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 #952378, 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.