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

[Balázs Kisterenyei]

This bug happened with Precise daily build 13 March 2012. No fglrx was installed, and all available updates were applied to the system by enabling all repositories and all possible update types (proposed, backported, etc.).

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: compiz-gnome 1:0.9.7.0+bzr3035-0ubuntu1
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
CasperVersion: 1.309
CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CompositorRunning: compiz
Date: Tue Mar 13 23:13:51 2012
DistUpgraded: Fresh install
DistroCodename: precise
DistroVariant: ubuntu
ExecutablePath: /usr/bin/gtk-window-decorator
GraphicsCard:
 Advanced Micro Devices [AMD] nee ATI RS780M/RS780MN [Mobility Radeon HD 3200 Graphics] [1002:9612] (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Device [1025:0148]
 Advanced Micro Devices [AMD] nee ATI RV620 [Mobility Radeon HD 3400 Series] [1002:95c4] (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Device [1025:0148]
LiveMediaBuild: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120313)
MachineType: Acer TravelMate 5530
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdline: /usr/bin/gtk-window-decorator
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: initrd=/ubninit file=/cdrom/preseed/hostname.seed boot=casper quiet splash -- BOOT_IMAGE=/ubnkern
SegvAnalysis:
 Segfault happened at: 0x419534 <max_window_name_width+36>: cmpq $0x0,0x2d8(%rax)
 PC (0x00419534) 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: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 12/30/2009
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: V1.26
dmi.board.name: Olan
dmi.board.vendor: Acer
dmi.board.version: Rev
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.26:bd12/30/2009:svnAcer:pnTravelMate5530:pvr0100:rvnAcer:rnOlan:rvrRev:cvnAcer:ct10:cvrN/A:
dmi.product.name: TravelMate 5530
dmi.product.version: 0100
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.7.0+bzr3035-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.30-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.1-0ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.1-0ubuntu3
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.