compiz crashed with SIGSEGV in PrivateWindow::updateStartupId()

Bug #764903 reported by Bertrand Presles on 2011-04-18
This bug affects 1 person
Affects Status Importance Assigned to Milestone
unity (Ubuntu)

Bug Description

Binary package hint: unity

It's probably related to #759363, but has I'm still experiencing it with latest update, this issue needs a better fix than the one commited.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: unity 3.8.8-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic
Uname: Linux 2.6.38-8-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Mon Apr 18 19:16:11 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: compiz
 Segfault happened at: 0x7f786ced6e56: movlpd (%rdi),%xmm1
 PC (0x7f786ced6e56) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%xmm1" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity
 ?? () from /lib/x86_64-linux-gnu/
 PrivateWindow::updateStartupId() ()
 CompScreen::handleEvent(_XEvent*) ()
 PrivateCompositeScreen::handleEvent(_XEvent*) () from /usr/lib/compiz/
 CompScreen::handleEvent(_XEvent*) ()
Title: compiz crashed with SIGSEGV in PrivateWindow::updateStartupId()
UpgradeStatus: Upgraded to natty on 2011-04-01 (17 days ago)
UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin plugdev sambashare tape video

Bertrand Presles (bpresles) wrote :
Sebastien Bacher (seb128) wrote :

did you build compiz yourself? "fix commited" means the fix is in the vcs but not uploaded to ubuntu yet, it should be tomorrow

Bertrand Presles (bpresles) wrote :

It's just that considering the date of the commit (15th April) and the today's date (18th April), I presumed the update was already issued. So my mistake, sorry. :)

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers