gtk-window-decorator crashed with SIGSEGV in max_window_name_width()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
during work
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: compiz-gnome 1:0.9.7.
ProcVersionSign
Uname: Linux 3.2.0-20-generic x86_64
NonfreeKernelMo
.tmp.unity.
ApportVersion: 1.95-0ubuntu1
Architecture: amd64
CompizPlugins: [core,composite
CompositorRunning: compiz
CrashCounter: 1
Date: Fri Mar 23 16:29:35 2012
DistUpgraded: 2012-03-12 00:16:37,432 DEBUG enabling apt cron job
DistroCodename: precise
DistroVariant: ubuntu
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110911)
MachineType: ASUSTeK Computer Inc. K52Dr
ProcCmdline: /usr/bin/
ProcEnviron:
LANG=pl_PL.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: compiz
Title: gtk-window-
UpgradeStatus: Upgraded to precise on 2012-03-11 (11 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 01/27/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: K52Dr.213
dmi.board.
dmi.board.name: K52Dr
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: K52Dr
dmi.product.
dmi.sys.vendor: ASUSTeK Computer Inc.
version.compiz: compiz 1:0.9.7.
version.
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.32-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 #953368, 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.