gtk-window-decorator crashed with SIGABRT in raise()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
The bug occurred when I was writing documents in LiberOffice.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: compiz-gnome 1:0.9.7.
ProcVersionSign
Uname: Linux 3.2.0-16-generic x86_64
.tmp.unity.
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CompizPlugins: [core,composite
CompositorRunning: compiz
Date: Sun Mar 11 18:52:26 2012
DistUpgraded: Log time: 2012-03-02 22:56:54.956231
DistroCodename: precise
DistroVariant: ubuntu
DuplicateOf: https:/
ExecutablePath: /usr/bin/
GraphicsCard:
NVIDIA Corporation Device [10de:0df1] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Acer Incorporated [ALI] Device [1025:0370]
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MachineType: Acer Aspire 4741
ProcCmdline: /usr/bin/
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 6
SourcePackage: compiz
StacktraceTop:
raise () from /lib/x86_
abort () from /lib/x86_
?? () from /lib/x86_
__assert_fail () from /lib/x86_
?? () from /usr/lib/
Title: gtk-window-
UpgradeStatus: Upgraded to precise on 2012-03-03 (8 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 04/28/2011
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: V1.31
dmi.board.
dmi.board.name: JE40_CP
dmi.board.vendor: Acer
dmi.board.version: V1.31
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: Aspire 4741
dmi.product.
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.7.
version.ia32-libs: ia32-libs 20090808ubuntu33
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 #932243, 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.