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

Bug #848952 reported by Pete Graner
56
This bug affects 8 people
Affects Status Importance Assigned to Milestone
Nux
Fix Released
High
Unassigned
Unity
Fix Released
High
Unassigned
nux (Ubuntu)
Fix Released
High
Unassigned
unity (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Went to switch workspaces with CTL-RIGHT ARROW and the display froze. Then compiz crashed and popped up the submit bug dialog.

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 x86_64
ApportVersion: 1.22.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Tue Sep 13 08:59:31 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110911)
ProcCmdline: compiz
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f22eefd6298 <_ZN3nux4Area16FindKeyFocusAreaEjmm+24>: mov 0x128(%rax),%rax
 PC (0x7f22eefd6298) ok
 source "0x128(%rax)" (0x00000128) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading 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::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::ProcessForeignEvent(_XEvent*, void*) () from /usr/lib/libnux-1.0.so.0
Title: compiz crashed with SIGSEGV in nux::Area::FindKeyFocusArea()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Related branches

Revision history for this message
Pete Graner (pgraner) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 FindKeyFocusArea (special_keys_state=786432, x11_key_code=65363, key_symbol=6, this=<optimized out>) at ./Area.cpp:962
 nux::Area::FindKeyFocusArea (this=<optimized out>, key_symbol=6, x11_key_code=65363, special_keys_state=786432) at ./Area.cpp:952
 nux::WindowCompositor::FindKeyFocusArea (this=0x2a2af50, event_type=nux::NUX_KEYDOWN, key_symbol=65363, special_keys_state=786432, key_focus_area=0x7fff09d56d08, window=0x7fff09d56d10) at ./WindowCompositor.cpp:796
 nux::WindowCompositor::KeyboardEventCycle (this=0x2a2af50, event=...) at ./WindowCompositor.cpp:886
 nux::WindowCompositor::ProcessEvent (this=0x2a2af50, 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
Jason Smith (jassmith)
Changed in nux (Ubuntu):
status: New → Fix Committed
Revision history for this message
Carsten Gehling (carsten-sarum) wrote :

When will this fix be available in the update manager?

Revision history for this message
Pete Graner (pgraner) wrote :

Fixed for me in one of the recent updates.

Changed in nux (Ubuntu):
importance: Medium → Critical
Jay Taoko (jaytaoko)
Changed in nux:
status: New → Fix Committed
Changed in unity:
status: New → Fix Committed
Omer Akram (om26er)
Changed in nux (Ubuntu):
importance: Critical → High
Changed in unity:
importance: Undecided → High
Changed in nux:
importance: Undecided → High
Gord Allott (gordallott)
Changed in unity:
milestone: none → 5.0.0
Changed in nux:
status: Fix Committed → Fix Released
Changed in unity:
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package nux - 2.0.0-0ubuntu1

---------------
nux (2.0.0-0ubuntu1) precise; urgency=low

  [ Aurélien Gâteau ]
  * New upstream release:
    - compiz crashed with SIGSEGV in nux::ROProperty<std::string>::operator
      std::string() (LP: #881106)
    - compiz crashed with SIGSEGV in
      nux::WindowCompositor::FindKeyFocusAreaFrom() (LP: #860852)
    - compiz crashed with SIGSEGV in nux::Area::FindKeyFocusArea()
      (LP: #848952)
    - compiz crashed with SIGILL in typeinfo for std::ostream() (LP: #849881)
    - compiz crashed with SIGSEGV in nux::WindowThread::IsInsideLayoutCycle()
      (LP: #864686)
    - Select quicklist items with just one right click (LP: #688830)
    - OnMouseDoubleClick in InputArea isn't working (LP: #708020)
    - Menubar - horizontal scroll over a menu opens it (LP: #775872)
    - Clicking on a dash category header should not give it keyboard focus
      (LP: #905921)
    - Horizontal scroll on maximize/restore window control restores window.
      (LP: #809717)
    - Horizontally scrolling while highlighting an item in the dash or on an
      indicator will open the item. (LP: #837004)
    - compiz crashed with SIGSEGV in free() (LP: #864446)
    - Mouse wheel doesn't works if the mouse pointer is inside dash scrollbar.
      (LP: #888819)
  * debian/rules, debian/control:
    - add nuxabiversion capability as upstream is breaking a lot the ABI
      wasn't bumping the soname. Create a virtual package similar to what
      we already do in compiz to ensure we dep on the right version.
      Remove the makeshlibs override then as not needed anymore.
    - bump to nux 2.0 with new libnux-2.0-0, libnux-2.0-common, libnux-2.0-dev
      packages. Make the necessary changes in .install files as well
    - don't ship anymore the -doc package.
  * debian/nux-tools.install:
    - move the apport file there instead of the -common package to enable
      co-instability
 -- Didier Roche <email address hidden> Fri, 13 Jan 2012 09:04:48 +0100

Changed in nux (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.