gtk-window-decorator crashed with SIGSEGV in event_filter_func()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
This error has happend few seconds after start Ubuntu 12.10 B2
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: compiz-gnome 1:0.9.8.4-0ubuntu1
ProcVersionSign
Uname: Linux 3.5.0-16-generic i686
.tmp.unity.
ApportVersion: 2.6.1-0ubuntu1
Architecture: i386
CompizPlugins: [core,composite
CompositorRunning: compiz
Date: Tue Oct 2 10:32:48 2012
DistUpgraded: Fresh install
DistroCodename: quantal
DistroVariant: ubuntu
ExecutablePath: /usr/bin/
GraphicsCard:
Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
Subsystem: QUANTA Computer Inc Device [152d:0883]
MachineType: POSITIVO SW6H
ProcCmdline: /usr/bin/
ProcEnviron:
LANGUAGE=
PATH=(custom, no user)
LANG=pt_BR.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 11
SourcePackage: compiz
StacktraceTop:
?? () from /lib/i386-
event_filter_func ()
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: gtk-window-
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
XsessionErrors:
gnome-
gnome-
(indicator-
dmi.bios.date: 12/07/2011
dmi.bios.vendor: INSYDE
dmi.bios.version: UU262
dmi.board.
dmi.board.name: SW6H
dmi.board.vendor: POSITIVO
dmi.board.version: SIM
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: POSITIVO
dmi.chassis.
dmi.modalias: dmi:bvnINSYDE:
dmi.product.name: SW6H
dmi.product.
dmi.sys.vendor: POSITIVO
version.compiz: compiz 1:0.9.8.4-0ubuntu1
version.libdrm2: libdrm2 2.4.39-0ubuntu1
version.
version.
version.
version.
version.
version.
version.
version.
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1060171, 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.