unity-window-decorator crashed with SIGSEGV in gdk_window_get_events()

[Symbol]

Binary package hint: compiz

Alt-dragging rhythmbox is a good way to trigger this bug--the window titlebar disappears followed shortly by a compiz crash.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: compiz-gnome 1:0.9.4-0ubuntu7
ProcVersionSignature: Ubuntu 2.6.38-7.36-generic 2.6.38
Uname: Linux 2.6.38-7-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 270.30 Fri Feb 25 14:34:55 PST 2011
 GCC version: gcc version 4.5.2 (Ubuntu/Linaro 4.5.2-6ubuntu4)
Architecture: amd64
CompizPlugins: [core,bailer,detection,composite,opengl,decor,grid,move,place,vpswitch,mousepoll,imgpng,gnomecompat,resize,compiztoolbox,regex,snap,session,wall,animation,workarounds,expo,ezoom,staticswitcher,fade,scale,unityshell]
CompositorRunning: compiz
Date: Sat Mar 19 19:41:56 2011
DistUpgraded: Log time: 2011-03-19 18:06:16.561191
DistroCodename: natty
DistroVariant: ubuntu
DkmsStatus:
 nvidia-current, 270.30, 2.6.38-7-generic, x86_64: installed
 nvidia-current, 270.30, 2.6.35-28-generic, x86_64: installed
ExecutablePath: /usr/bin/unity-window-decorator
GraphicsCard:
 nVidia Corporation GF104 [GeForce GTX 460] [10de:0e22] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:835c]
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
InstallationMedia_: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
JockeyStatus: xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, Enabled, In use)
ProcCmdline: /usr/bin/unity-window-decorator
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-7-generic root=UUID=32827e0a-d28e-4db5-b285-76b7061eb27b ro quiet splash vt.handoff=7
ProcVersionSignature_: Ubuntu 2.6.38-7.36-generic 2.6.38
Renderer: Unknown
SegvAnalysis:
 Segfault happened at: 0x7f30819c94ce <gdk_window_get_events+14>: mov (%rbx),%rdx
 PC (0x7f30819c94ce) ok
 source "(%rbx)" (0x700186c0) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
 gdk_window_get_events () from /usr/lib/libgdk-x11-2.0.so.0
 event_filter_func ()
 ?? () from /usr/lib/libgdk-x11-2.0.so.0
 ?? () from /usr/lib/libgdk-x11-2.0.so.0
 ?? () from /usr/lib/libgdk-x11-2.0.so.0
Title: unity-window-decorator crashed with SIGSEGV in gdk_window_get_events()
UpgradeStatus: Upgraded to natty on 2011-03-19 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 11/16/2010
dmi.bios.vendor: Intel Corp.
dmi.bios.version: BAP6710H.86A.0037.2010.1116.2134
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DP67BA
dmi.board.vendor: Intel Corporation
dmi.board.version: AAG10219-202
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorp.:bvrBAP6710H.86A.0037.2010.1116.2134:bd11/16/2010:svn:pn:pvr:rvnIntelCorporation:rnDP67BA:rvrAAG10219-202:cvn:ct3:cvr:
version.compiz: compiz 1:0.9.4-0ubuntu7
version.libdrm2: libdrm2 2.4.23-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.1-0ubuntu3
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg: xserver-xorg 1:7.6~3ubuntu11
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu6

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #725284, 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.