compiz crashed with SIGSEGV in CompWindow::id()

Bug #825040 reported by Jean-Baptiste Lallement on 2011-08-12
This bug affects 80 people
Affects Status Importance Assigned to Milestone
Fix Released
Canonical Desktop Experience Team
unity (Ubuntu)
Canonical Desktop Experience Team
Canonical Desktop Experience Team

Bug Description

Crashed on ALT-TAB

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: unity 4.8.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-8.10-generic 3.0.1
Uname: Linux 3.0.0-8-generic i686
Architecture: i386
CrashCounter: 1
Date: Fri Aug 12 10:03:36 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110209)
ProcCmdline: compiz
 Segfault happened at: 0x8080e74 <CompWindow::id()+4>: mov 0x2c(%eax),%eax
 PC (0x08080e74) ok
 source "0x2c(%eax)" (0x0000002c) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity
 CompWindow::id (this=0x0) at /build/buildd/compiz-
 UnityScreen::getWindowPaintList() () from /usr/lib/compiz/
 CompositeScreen::getWindowPaintList (this=0x8b05580) at /build/buildd/compiz-
 DecorWindow::windowNotify (this=0x939e978, n=CompWindowNotifyMap) at /build/buildd/compiz-
 CompWindow::windowNotify (this=0x939e650, n=CompWindowNotifyMap) at /build/buildd/compiz-
Title: compiz crashed with SIGSEGV in CompWindow::id()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Related branches

Jean-Baptiste Lallement (jibel) wrote :
Changed in unity (Ubuntu):
status: New → Confirmed
visibility: private → public
Changed in unity (Ubuntu):
assignee: nobody → Canonical Desktop Experience Team (canonical-dx-team)
Changed in unity (Ubuntu Oneiric):
importance: Undecided → High
Scott Lewin (sclewin) wrote :

I do not know if I experienced the same bug, but I got this crash during startup.

Anadon (joshua-r-marshall-1991) wrote :

same here, only my architecture is amd64

Also on login here.

pschonmann (pschonmann) wrote :

At startup too

Changed in unity (Ubuntu Oneiric):
importance: High → Critical
milestone: none → ubuntu-11.10-beta-1
col reilly (lupinehorror) wrote :

desktop appeared rather slowly...some icons missing. clicked the ubuntu icon and crash occurred (or thereabouts)

Jean-Baptiste Lallement (jibel) wrote :

valgrind trace

Jan Pieczkowski (physicalist) wrote :

Still happening in unity-4.8.0-0ubuntu2, directly on startup, with slightly different error message.
Offending command was:
"Segfault happened at: 0x43c4d0 <_ZN10CompWindow2idEv>: mov 0x58(%rdi), %rax [...] source "0x58(%rdi)" (0x00000000058) not located in a known VMA region"

Jean-Baptiste Lallement (jibel) wrote :

I removed the directory ~/.compiz and I have been able to login without a crash. Restore it and the crash is back.
I attach the content of that directory.

Doug McMahon (mc3man) wrote :

Using basically the diff from above (the indents seemed off..) have seen no sign of this compiz crash thru several cold boots, warm restarts and log outs/in
Previously didn't occur all the time here but was seen on most cold boots

Launchpad Janitor (janitor) wrote :

This bug was fixed in the package unity - 4.8.0-0ubuntu3

unity (4.8.0-0ubuntu3) oneiric; urgency=low

  * Backport r1373 to fix a segfault happening on theme updates (lp: #825587)
    (lp: #741652)
  * Backport r1380 to fix an alt-tab switcher segfault (lp: #825148)
  * Backport r1381 to fix a session start compiz segfault (lp: #825040)
 -- Sebastien Bacher <email address hidden> Thu, 18 Aug 2011 11:21:50 +0200

Changed in unity (Ubuntu Oneiric):
status: Confirmed → Fix Released
Doug McMahon (mc3man) wrote :

Even though the fix released seems fine I'd give some consideration to default disabling the Session Management plugin
At least here seems to provide no value and better off by having ~/.compiz/session empty

Jono Bacon (jonobacon) wrote :

This is marked fix released but I just experienced this crash with 4.8.0-0ubuntu4.

Jono Bacon (jonobacon) wrote :

I tried to change the bug status to Confirmed but I can't.

Changed in unity:
assignee: nobody → Canonical Desktop Experience Team (canonical-dx-team)
importance: Undecided → Critical
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers