compiz crashed "out of the blue"

[Dennis]

Was trying to get the fglrx post-updates installed a few hours ago but failed miserably; this is probably related. I think most/all debug info is part of this report.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: compiz-gnome 1:0.9.7.0~bzr2995-0ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-16.25-generic 3.2.6
Uname: Linux 3.2.0-16-generic x86_64
NonfreeKernelModules: fglrx
.tmp.unity.support.test.0:

ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CompizPlugins: [core,composite,opengl,decor,compiztoolbox,move,regex,place,mousepoll,imgpng,wall,grid,snap,resize,vpswitch,session,animation,gnomecompat,fade,scale,expo,workarounds,ezoom,unityshell]
CompositorRunning: compiz
CrashCounter: 1
Date: Sat Feb 18 11:59:23 2012
DistUpgraded: Log time: 2012-02-02 12:06:43.160763
DistroCodename: precise
DistroVariant: ubuntu
ExecutablePath: /usr/bin/gtk-window-decorator
GraphicsCard:
 Advanced Micro Devices [AMD] nee ATI Turks [Radeon HD 6670] [1002:6758] (prog-if 00 [VGA controller])
   Subsystem: Giga-byte Technology Device [1458:2545]
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
JockeyStatus:
 xorg:fglrx_updates - ATI/AMD proprietary FGLRX graphics driver (post-release updates) (Proprietary, Disabled, Not in use)
 xorg:fglrx - ATI/AMD proprietary FGLRX graphics driver (Proprietary, Enabled, In use)
MachineType: Gigabyte Technology Co., Ltd. H61M-S2V-B3
ProcCmdline: /usr/bin/gtk-window-decorator
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-16-generic root=UUID=c4c05193-6a85-4e9a-b8f9-47e34e37ad10 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x4194c4 <max_window_name_width+36>: cmpq $0x0,0x2d8(%rax)
 PC (0x004194c4) ok
 source "$0x0" ok
 destination "0x2d8(%rax)" (0x000002d8) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
 max_window_name_width ()
 update_window_decoration_size ()
 ?? ()
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gtk-window-decorator crashed with SIGSEGV in max_window_name_width()
UpgradeStatus: Upgraded to precise on 2012-02-13 (5 days ago)
UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare sudo www-data
dmi.bios.date: 08/04/2011
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F5
dmi.board.name: H61M-S2V-B3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd08/04/2011:svnGigabyteTechnologyCo.,Ltd.:pnH61M-S2V-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-S2V-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: H61M-S2V-B3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.7.0~bzr2995-0ubuntu4
version.fglrx-installer: fglrx-installer N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.30-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 8.0~rc2-0ubuntu5
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 8.0~rc2-0ubuntu5
version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.99.901+git20120126-0ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2

[Apport retracing service (apport)]

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 #932251, 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.