compiz.real crashed with SIGSEGV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu |
New
|
Undecided
|
Unassigned |
Bug Description
my ubuntu 910 was uprade from 9 0 4
ProblemType: Crash
Architecture: i386
CompizPlugins: [core,move,
Date: Mon Nov 16 18:34:01 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/
MachineType: IBM 2668CC2
Package: compiz-core 1:0.8.4-0ubuntu2
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
PciDisplay: 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc M22 [Mobility Radeon X300] [1002:5460]
ProcCmdLine: root=UUID=
ProcCmdline: /usr/bin/
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
RelatedPackageV
xserver-xorg 1:7.4+3ubuntu7
libgl1-mesa-glx 7.6.0-1ubuntu4
libdrm2 2.4.14-1ubuntu1
xserver-
xserver-
SegvAnalysis:
Segfault happened at: 0x8055c3c: mov (%ebx),%ebx
PC (0x08055c3c) ok
source "(%ebx)" (0x000001f0) not located in a known VMA region (needed readable region)!
destination "%ebx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: compiz
Stacktrace:
#0 0x08055c3c in ?? ()
No symbol table info available.
Cannot access memory at address 0xbfea7dec
StacktraceTop: ?? ()
ThreadStacktrace:
.
Thread 1 (Thread 1940):
#0 0x08055c3c in ?? ()
No symbol table info available.
Cannot access memory at address 0xbfea7dec
Title: compiz.real crashed with SIGSEGV
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers
dmi.bios.date: 07/07/2006
dmi.bios.vendor: IBM
dmi.bios.version: 1YET64WW (1.28 )
dmi.board.name: 2668CC2
dmi.board.vendor: IBM
dmi.board.version: Not Available
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: IBM
dmi.chassis.
dmi.modalias: dmi:bvnIBM:
dmi.product.name: 2668CC2
dmi.product.
dmi.sys.vendor: IBM
system: distro = Ubuntu, architecture = i686, kernel = 2.6.31-14-generic
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 #448601, 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.