compiz crashed with SIGSEGV in nux::Area::FindKeyFocusArea()

Bug #849367 reported by Ahmad Zain
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
nux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

compiz crashed with SIGSEGV in nux::Area::FindKeyFocusArea()

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: libnux-1.0-0 1.8.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-11.17-generic 3.0.4
Uname: Linux 3.0.0-11-generic i686
NonfreeKernelModules: wl
ApportVersion: 1.22.1-0ubuntu2
Architecture: i386
CrashCounter: 1
Date: Tue Sep 13 21:43:33 2011
Disassembly: => 0x18: Cannot access memory at address 0x18
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcCmdline: compiz
SegvAnalysis:
 Segfault happened at: 0x18: Cannot access memory at address 0x18
 PC (0x00000018) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: nux
StacktraceTop:
 ?? ()
 nux::Area::FindKeyFocusArea(unsigned int, unsigned long, unsigned long) () from /usr/lib/libnux-1.0.so.0
 nux::View::FindKeyFocusArea(unsigned int, unsigned long, unsigned long) () from /usr/lib/libnux-1.0.so.0
 nux::Area::FindKeyFocusArea(unsigned int, unsigned long, unsigned long) () from /usr/lib/libnux-1.0.so.0
 nux::View::FindKeyFocusArea(unsigned int, unsigned long, unsigned long) () from /usr/lib/libnux-1.0.so.0
Title: compiz crashed with SIGSEGV in nux::Area::FindKeyFocusArea()
UpgradeStatus: Upgraded to oneiric on 2011-08-25 (19 days ago)
UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin plugdev root sambashare tape users video www-data

Revision history for this message
Ahmad Zain (am-zain) wrote :
Changed in nux (Ubuntu):
status: New → Confirmed
Revision history for this message
Sérgio Faria (sergio91pt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 815114, so it 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. Feel free to continue to report any other bugs you may find.

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.