gtk-window-decorator crashed with SIGSEGV in max_window_name_width()

[y.srinivas]

crashed while opening wine1.4 application in ubuntu 12.04

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: compiz-gnome 1:0.9.7.0~bzr2995-0ubuntu5
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
CompizPlugins: [core,bailer,detection,composite,opengl,decor,move,mousepoll,imgpng,grid,unitymtgrabhandles,gnomecompat,vpswitch,compiztoolbox,place,wall,regex,snap,resize,session,animation,workarounds,expo,fade,ezoom,scale,unityshell]
CompositorRunning: compiz
CrashCounter: 1
CurrentDmesg:
 [ 32.431254] wlan0: no IPv6 routers present
 [ 35.847681] iwlwifi 0000:04:00.0: Tx aggregation enabled on ra = a0:21:b7:8b:ab:80 tid = 0
 [ 146.619787] gtk-window-deco[2102]: segfault at 2d8 ip 00000000004194c4 sp 00007fffd9238670 error 4 in gtk-window-decorator[400000+1e000]
Date: Mon Mar 12 12:54:22 2012
DistUpgraded: Log time: 2012-03-11 15:41:50.949317
DistroCodename: precise
DistroVariant: ubuntu
ExecutablePath: /usr/bin/gtk-window-decorator
GraphicsCard:
 Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:046e]
 NVIDIA Corporation Device [10de:0df1] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:046e]
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MachineType: Dell Inc. XPS L501X
ProcCmdline: /usr/bin/gtk-window-decorator
ProcEnviron:
 LANGUAGE=en_IN:en
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-18-generic root=UUID=b0ebf7c2-4236-4f87-accc-5ccb2585211c 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_cclosure_marshal_VOID__OBJECTv () 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-03-11 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 11/26/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A04
dmi.board.name: 00CKNG
dmi.board.vendor: Dell Inc.
dmi.board.version: A04
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A04
dmi.modalias: dmi:bvnDellInc.:bvrA04:bd11/26/2010:svnDellInc.:pnXPSL501X:pvrA04:rvnDellInc.:rn00CKNG:rvrA04:cvnDellInc.:ct8:cvrA04:
dmi.product.name: XPS L501X
dmi.product.version: A04
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.7.0~bzr2995-0ubuntu5
version.ia32-libs: ia32-libs 20090808ubuntu33
version.libdrm2: libdrm2 2.4.30-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.1-0ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.1-0ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu6
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 #948580, 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.