gtk-window-decorator crashed with SIGABRT in raise()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Just installed precise. I've no idea what happened.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: compiz-gnome 1:0.9.7.
ProcVersionSign
Uname: Linux 3.2.0-17-
.tmp.unity.
ApportVersion: 1.93-0ubuntu2
Architecture: i386
CompizPlugins: [core,bailer,
CompositorRunning: compiz
Date: Tue Feb 28 01:40:02 2012
DistUpgraded: Log time: 2012-02-28 01:06:12.573384
DistroCodename: precise
DistroVariant: ubuntu
ExecutablePath: /usr/bin/
GraphicsCard:
Intel Corporation N10 Family Integrated Graphics Controller [8086:a011] (prog-if 00 [VGA controller])
Subsystem: Acer Incorporated [ALI] Device [1025:0349]
Subsystem: Acer Incorporated [ALI] Device [1025:0349]
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120201.1)
MachineType: Acer AO532h
ProcCmdline: /usr/bin/
ProcEnviron:
LANGUAGE=es_CL:es
PATH=(custom, no user)
LANG=es_CL.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 6
SourcePackage: compiz
StacktraceTop:
raise () from /lib/i386-
abort () from /lib/i386-
?? () from /lib/i386-
__assert_fail () from /lib/i386-
?? () from /usr/lib/
UpgradeStatus: Upgraded to precise on 2012-02-28 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 01/30/2010
dmi.bios.vendor: Acer
dmi.bios.version: V1.17
dmi.board.
dmi.board.name: AO532h
dmi.board.vendor: Acer
dmi.board.version: V1.17
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.
dmi.modalias: dmi:bvnAcer:
dmi.product.name: AO532h
dmi.product.
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.7.
version.libdrm2: libdrm2 2.4.30-1ubuntu1
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 #939227, 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.