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

Bug #846039 reported by Anders Feder
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Crashed when clicking an indicator.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: libnux-1.0-0 1.8.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
Uname: Linux 3.0.0-10-generic x86_64
ApportVersion: 1.22.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Fri Sep 9 23:27:58 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcCmdline: compiz
SegvAnalysis:
 Segfault happened at: 0x7f38bda32298 <_ZN3nux4Area16FindKeyFocusAreaEjmm+24>: mov 0x128(%rax),%rax
 PC (0x7f38bda32298) ok
 source "0x128(%rax)" (0x10000012c) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nux
StacktraceTop:
 nux::Area::FindKeyFocusArea(unsigned int, unsigned long, unsigned long) () from /usr/lib/libnux-1.0.so.0
 nux::WindowCompositor::FindKeyFocusArea(nux::NuxEventType, unsigned int, unsigned int, nux::InputArea**, nux::BaseWindow**) () from /usr/lib/libnux-1.0.so.0
 nux::WindowCompositor::KeyboardEventCycle(nux::Event&) () from /usr/lib/libnux-1.0.so.0
 nux::WindowCompositor::ProcessEvent(nux::Event&) () from /usr/lib/libnux-1.0.so.0
 nux::WindowThread::ExecutionLoop(unsigned int) () from /usr/lib/libnux-1.0.so.0
Title: compiz crashed with SIGSEGV in nux::Area::FindKeyFocusArea()
UpgradeStatus: Upgraded to oneiric on 2011-09-02 (7 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors: (gnome-terminal:3642): Gdk-CRITICAL **: gdk_window_get_events: assertion `GDK_IS_WINDOW (window)' failed

Revision history for this message
Anders Feder (afeder) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 FindKeyFocusArea (special_keys_state=0, x11_key_code=65513, key_symbol=6, this=<optimized out>) at ./Area.cpp:962
 nux::Area::FindKeyFocusArea (this=<optimized out>, key_symbol=6, x11_key_code=65513, special_keys_state=0) at ./Area.cpp:952
 nux::WindowCompositor::FindKeyFocusArea (this=0x1616840, event_type=nux::NUX_KEYDOWN, key_symbol=65513, special_keys_state=0, key_focus_area=0x7fff793d9aa8, window=0x7fff793d9ab0) at ./WindowCompositor.cpp:796
 nux::WindowCompositor::KeyboardEventCycle (this=0x1616840, event=...) at ./WindowCompositor.cpp:886
 nux::WindowCompositor::ProcessEvent (this=0x1616840, event=...) at ./WindowCompositor.cpp:1026

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in nux (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Changed in nux (Ubuntu):
status: New → Confirmed
Jeremy Bícha (jbicha)
visibility: private → public
Revision history for this message
Lukasz Olszewski (olszewskil) 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.