compiz crashed with SIGSEGV in __strlen_sse2_bsf()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Had been using the system for ~45mins. I logged into my Gmail (on Chromium) and clicked on one new email item. This caused the screen to flicker, revert to the background image, and then redisplay my desktop. The Apport crash dialog then popped up
$ lsb_release -rd
Description: Ubuntu oneiric (development branch)
Release: 11.10
$ apt-cache policy compiz
compiz:
Installed: 1:0.9.5.0-0ubuntu1
Candidate: 1:0.9.5.0-0ubuntu1
Version table:
*** 1:0.9.5.0-0ubuntu1 0
500 http://
100 /var/lib/
$ apt-cache policy unity
unity:
Installed: 4.4.0-0ubuntu1
Candidate: 4.4.0-0ubuntu1
Version table:
*** 4.4.0-0ubuntu1 0
500 http://
100 /var/lib/
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: unity 4.4.0-0ubuntu1
ProcVersionSign
Uname: Linux 3.0.0-7-generic i686
Architecture: i386
Date: Thu Jul 28 09:35:06 2011
ExecutablePath: /usr/bin/compiz
ProcCmdline: compiz
ProcEnviron:
LANGUAGE=en_GB:en
LANG=en_GB.UTF-8
SHELL=
SegvAnalysis:
Segfault happened at: 0x1363666 <__strlen_
PC (0x01363666) ok
source "(%edi)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%xmm1" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
__strlen_sse2_bsf () at ../sysdeps/
SimpleLauncher
BamfLauncherIc
LauncherContro
g_cclosure_
Title: compiz crashed with SIGSEGV in __strlen_sse2_bsf()
UpgradeStatus: Upgraded to oneiric on 2011-07-27 (0 days ago)
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video
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 #814639, 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.