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

[jaaziel isaac loera garcia]

it happens when i open and close stellarium, compiz crashes and windows decorations dessapear.

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

ApportVersion: 1.94.1-0ubuntu1
Architecture: amd64
CompizPlugins: [core,bailer,detection,composite,opengl,decor,compiztoolbox,imgpng,grid,unitymtgrabhandles,regex,animation,move,place,resize,gnomecompat,mousepoll,vpswitch,session,snap,wall,expo,workarounds,ezoom,fade,scale,unityshell]
CompositorRunning: compiz
CrashCounter: 1
Date: Thu Mar 8 13:42:00 2012
DistUpgraded: Log time: 2012-03-05 01:19:02.687818
DistroCodename: precise
DistroVariant: ubuntu
ExecutablePath: /usr/bin/gtk-window-decorator
GraphicsCard:
 Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Toshiba America Info Systems Device [1179:fd90]
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 003: ID 10f1:1a2a Importek
MachineType: TOSHIBA Satellite L635
ProcCmdline: /usr/bin/gtk-window-decorator
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-18-generic root=UUID=298dec0d-34fb-4d69-879e-7fd6e9ba48f1 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-07 (1 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 11/09/2011
dmi.bios.vendor: INSYDE
dmi.bios.version: 2.40
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnINSYDE:bvr2.40:bd11/09/2011:svnTOSHIBA:pnSatelliteL635:pvrPSK60U-006001:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Satellite L635
dmi.product.version: PSK60U-006001
dmi.sys.vendor: TOSHIBA
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-0ubuntu5
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.