compiz crashed with SIGSEGV in CompWindow::id()

Bug #694945 reported by Gary M
248
This bug affects 58 people
Affects Status Importance Assigned to Milestone
Unity
Fix Released
High
Michael Terry
unity (Ubuntu)
Fix Released
High
Unassigned
Natty
Fix Released
High
Unassigned

Bug Description

Compiz occasionally crashes, leaving open windows where they are. Mouse input works, Keyboard does not work (except for Caps-lock and Ctrl-Alt-F*).

Compiz crashed in ordinary Unity session. Keyboard was then unresponsive while mouse was ok.

Relevant metadata:

Package: compiz-core 1:0.9.2.1+glibmainloop3-0ubuntu5
RelatedPackageVersions:
 xserver-xorg 1:7.5+6ubuntu6
 libgl1-mesa-glx 7.9+repack-1ubuntu3
 libdrm2 2.4.22-2ubuntu1
 xserver-xorg-video-intel 2:2.13.901-2ubuntu2
 xserver-xorg-video-ati 1:6.13.2-1ubuntu2
SegvAnalysis:
 Segfault happened at: 0x807fa77 <_ZN10CompWindow2idEv+7>: mov 0x2c(%eax),%eax
 PC (0x0807fa77) ok
 source "0x2c(%eax)" (0x61626998) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11SourcePackage: compiz
StacktraceTop:
 CompWindow::id() ()
 UnityScreen::getWindowPaintList() () from /usr/lib/compiz/libunityshell.so
 CompositeScreen::getWindowPaintList() () from /usr/lib/compiz/libcomposite.so
 PrivateGLScreen::paintOutputRegion(GLMatrix const&, CompRegion const&, CompOutput*, unsigned int) () from /usr/lib/compiz/libopengl.so
 GLScreen::glPaintOutput(GLScreenPaintAttrib const&, GLMatrix const&, CompRegion const&, CompOutput*, unsigned int) () from /usr/lib/compiz/libopengl.so
Title: compiz crashed with SIGSEGV in CompWindow::id()

Related branches

Revision history for this message
Gary M (garym) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 CompWindow::id (this=0x6162696c)
 UnityScreen::getWindowPaintList (this=0x9f97670)
 CompositeScreen::getWindowPaintList (this=0x9bd9c40)
 PrivateGLScreen::paintOutputRegion (this=0x9be1200,

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 compiz (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Gary M (garym)
tags: added: regression-release
visibility: private → public
Gary M (garym)
description: updated
Revision history for this message
Paul Sladen (sladen) wrote :

After hitting this, dropping to a terminal (Ctrl-Alt-F1) allows login, followed by typing 'unity' to restart compiz.

Changed in compiz (Ubuntu):
status: New → Triaged
Paul Sladen (sladen)
description: updated
Revision history for this message
Travis Watkins (amaranth) wrote :

So I'm thinking the solution here is for unity to check to make sure this is a valid window before calling ->id() on it.

affects: compiz (Ubuntu) → unity (Ubuntu)
Changed in unity:
status: New → Triaged
importance: Undecided → High
Changed in unity (Ubuntu):
importance: Medium → High
Changed in unity:
milestone: none → 3.2.10
Michael Terry (mterry)
Changed in unity:
assignee: nobody → Michael Terry (mterry)
status: Triaged → In Progress
Changed in unity:
status: In Progress → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package unity - 3.2.12-0ubuntu1

---------------
unity (3.2.12-0ubuntu1) natty; urgency=low

  * New upstream release.
   - Window border doesn't get restored (LP: #691812)
   - When a menu is triggered from Alt+key, app name stays visible on panel
     (LP: #691765)
   - show the launcher on <Super> KeyPress, this will be needed when the
     shortcut will be implemented if we are in intellihide mode
   - Make sure an underscore is correctly placed under the corresponding
     accelerator-key. (LP: #683427)
   - Adding a dummy --replace option for compatibility reason (LP: #692569)
   - Compiz crashed with SIGSEGV in CompWindow::id() (LP: #694945)
   - Tooltip text not vertically centered (LP: #697791)
   - Maximizing a window horizontally or vertically removes the title bar
     (LP: #696780)
   - Mousewheel support for indicators (LP: #681428)
   - Avoid Quicklists being positioned so that they are partially offscreen at
     the bottom screen-edge. (LP: #691114)
   - Migrate awn, docky and cairo-dock dock launchers (LP: #692967)
   - Include manpages, and make them translatable. (LP: #684896)
   - Automaximize windows in Unity with some rules like blacklisting some
     applications, initial window size.
     It fixes also some bugs, like maximized window on first map not
     undecorated (LP: #667009, #669716, #693779, #691741)
   - Update libunity to conform to latest GIO VAPI breakage (LP: #679964)
   - Initial unity-atk module implementation (LP: #701680)
   - Panel autohide when on Quicklist (LP: #683261)
  * debian/control:
    - unity breaks on older bamf version (dbus protocol changed)
    - needs latest and greatest from dee
    - add libatk1.0-dev build-dep
  * CMakeList:
    - distro-patch to avoid building tests right now as building them is failing
      with the current vala/gir stack. THIS NEED TO BE REMOVED.
  * debian/rules:
    - don't --fail-missing as we don't want to install the vapi yet. The gir
      package will come next week.
  * debian/unity-common.install:
    - install the manpages
  * debian/libunity3.symbols:
    - updated
 -- Didier Roche <email address hidden> Fri, 14 Jan 2011 20:47:25 +0100

Changed in unity (Ubuntu Natty):
status: Triaged → Fix Released
Revision history for this message
sdaau (sd-imi) wrote :

Got the same bug while I was trying to run skencil, after installing via 'apt-get install skencil' in natty - the whole desktop crashed, and then restarted...

Revision history for this message
Lucian Adrian Grijincu (lucian.grijincu) wrote :

I got this while running "gitk" - 100% reproduction. Will try with the updated package.

Revision history for this message
quent57 (quent57) wrote :

I got the same bug with my up to date natty.

Revision history for this message
Gary M (garym) wrote :

I've reported the new problem in bug #743932, which is currently waiting for a retrace.

Revision history for this message
Michael Terry (mterry) wrote :

That link doesn't work, Gary? Is that the right bug number?

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.