gtk-window-decorator crashed with SIGSEGV in g_type_check_instance_cast()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: compiz
Apport crash.
ProblemType: Crash
Architecture: i386
CompizPlugins: [core,ccp,
Date: Thu Sep 10 12:57:12 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/
MachineType: LENOVO 7417CTO
Package: compiz-gnome 1:0.8.2-0ubuntu16
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
PciDisplay: 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07)
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: /usr/bin/
ProcEnviron:
LANGUAGE=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
RelatedPackageV
xserver-xorg 1:7.4+3ubuntu5
libgl1-mesa-glx 7.6.0~git200908
libdrm2 2.4.13-1ubuntu1
xserver-
xserver-
SegvAnalysis:
Segfault happened at: 0x8bea68 <g_type_
PC (0x008bea68) ok
source "(%esi)" (0xaaaaaaaa) not located in a known VMA region (needed readable region)!
destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
g_type_
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
g_main_
Title: gtk-window-
Uname: Linux 2.6.31-10-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XorgConf: Error: [Errno 2] No such file or directory: '/etc/X11/
dmi.bios.date: 01/09/2009
dmi.bios.vendor: LENOVO
dmi.bios.version: 7UET56WW (2.02 )
dmi.board.name: 7417CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: 7417CTO
dmi.product.
dmi.sys.vendor: LENOVO
system: distro = Ubuntu, architecture = i686, kernel = 2.6.31-10-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 #326367, 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.