Tried opening AMSN from Launch Bar and compiz crashed. Just updated from 10.10 a few mins ago.

Bug #750037 reported by mcnamara_edward@hotmail.com on 2011-04-04
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
unity (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: unity

Ok, I updated from 10.10 Meercat on my Sony Vaio VPCW211AD and to my delight, the launch car on the right of the screen appears to be displayed just fine and I think it is displayed 3D which I couldn't do with Unity in 10.10. Anyways, I just tried to launch AMSN which was an install that carried over from when I was using 10.10 and it said that Compiz reported some error and crashed.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: unity 3.8.2-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic i686
Architecture: i386
Date: Mon Apr 4 16:04:36 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x807ffe7 <_ZN10CompWindow2idEv+7>: mov 0x2c(%eax),%eax
 PC (0x0807ffe7) 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
StacktraceTop:
 CompWindow::id() ()
 CompScreen::handleEvent(_XEvent*) ()
 PrivateCompositeScreen::handleEvent(_XEvent*) () from /usr/lib/compiz/libcomposite.so
 CompScreen::handleEvent(_XEvent*) ()
 PrivateGLScreen::handleEvent(_XEvent*) () from /usr/lib/compiz/libopengl.so
Title: compiz crashed with SIGSEGV in CompWindow::id()
UpgradeStatus: Upgraded to natty on 2011-04-04 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #747439, so 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. Please continue to report any other bugs you may find.

visibility: private → public
tags: removed: need-i386-retrace
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers