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
This happens whenever I do stuff with the system tray. I had a lot of problems with stalonetray, but I also had it happen with the tray in AWN.
ProblemType: Crash
Architecture: amd64
CompizPlugins: [core,ccp,
CrashCounter: 1
Date: Thu Sep 3 19:24:11 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/
MachineType: Dell Inc. Inspiron 1525
NonfreeKernelMo
Package: compiz-gnome 1:0.8.2-0ubuntu16
PccardctlIdent:
PccardctlStatus:
PciDisplay: 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a02] (rev 0c)
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: /usr/bin/
ProcEnviron:
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.12+
xserver-
xserver-
SegvAnalysis:
Segfault happened at: 0x7f269b56c8b4 <g_type_
PC (0x7f269b56c8b4) ok
source "(%rdi)" (0xaaaaaaaaaaaa
destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
g_type_
?? () from /usr/lib/
?? () from /usr/lib/
g_main_
?? () from /usr/lib/
Title: gtk-window-
Uname: Linux 2.6.31-9-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XorgConf: Error: [Errno 2] No such file or directory: '/etc/X11/
dmi.bios.date: 03/10/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 0U990C
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Inspiron 1525
dmi.sys.vendor: Dell Inc.
system: distro = Ubuntu, architecture = x86_64, kernel = 2.6.31-9-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 #404703, 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.