gksu crashed with SIGSEGV in gdk_window_set_opacity()

[viktor]

Binary package hint: gksu

Crash on launching update-manager.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: gksu 2.0.2-2ubuntu2
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
CheckboxSubmission: 3d3139e272c419276633ca58f4d1fe69
CheckboxSystem: daed2f3d6643b4a84b4520a2427f8c2b
Date: Sat Apr 3 11:11:51 2010
ExecutablePath: /usr/bin/gksu
ProcCmdline: /usr/bin/gksu --desktop /usr/share/applications/update-manager.desktop -- /usr/sbin/synaptic --hide-main-window --non-interactive --parent-window-id 14680108 --update-at-startup
ProcEnviron:
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f9be2a62a11 <gdk_window_set_opacity+33>: cmp %rax,(%rdx)
 PC (0x7f9be2a62a11) ok
 source "%rax" ok
 destination "(%rdx)" (0x20736e6f74756f42) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gksu
StacktraceTop:
 gdk_window_set_opacity ()
 ?? () from /usr/lib/libgksu2.so.0
 g_main_context_dispatch ()
 ?? () from /lib/libglib-2.0.so.0
 g_main_loop_run () from /lib/libglib-2.0.so.0
Title: gksu crashed with SIGSEGV in gdk_window_set_opacity()
UserGroups: adm admin cdrom dialout lp lpadmin plugdev sambashare
XsessionErrors:
 (polkit-gnome-authentication-agent-1:1337): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (Do:1339): Wnck-CRITICAL **: wnck_set_client_type got called multiple times.

[Apport retracing service (apport)]

StacktraceTop:
 IA__gdk_window_set_opacity (window=0x7f9be3ba8609,
 fadeout_callback (fadeout=0xc43370) at libgksu.c:326
 g_main_context_dispatch ()
 ?? () from /lib/libglib-2.0.so.0
 g_main_loop_run () from /lib/libglib-2.0.so.0

[Charlie Kravetz (cjkgeek)]

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