gksu crashed with SIGSEGV in gdk_window_set_opacity()

[apradoc]

Binary package hint: gksu

Upgrade from 10.0.4
Chromium browser and ugly site with flash :-P

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 i686
NonfreeKernelModules: nvidia
Architecture: i386
CheckboxSubmission: 9da8eba0b3f9dbf8a9dfa4b9c0f85aa1
CheckboxSystem: daed2f3d6643b4a84b4520a2427f8c2b
Date: Mon Apr 5 10:17:37 2010
ExecutablePath: /usr/bin/gksu
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
ProcCmdline: /usr/bin/gksu --desktop /usr/share/applications/synaptic.desktop /usr/sbin/synaptic
ProcEnviron:
 LANG=es_VE.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x64eadc <gdk_window_set_opacity+44>: mov (%esi),%edx
 PC (0x0064eadc) ok
 source "(%esi)" (0x616c2f65) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gksu
StacktraceTop:
 gdk_window_set_opacity () from /usr/lib/libgdk-x11-2.0.so.0
 ?? () from /usr/lib/libgksu2.so.0
 ?? () from /lib/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/libglib-2.0.so.0
 ?? () from /lib/libglib-2.0.so.0
Title: gksu crashed with SIGSEGV in gdk_window_set_opacity()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (polkit-gnome-authentication-agent-1:1445): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (Do:1466): Wnck-CRITICAL **: wnck_set_client_type got called multiple times.

[Apport retracing service (apport)]

StacktraceTop:
 IA__gdk_window_set_opacity (window=0x616c2f65, opacity=0.5)
 fadeout_callback (fadeout=0x899d2f8) at libgksu.c:326
 ?? () from /lib/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/libglib-2.0.so.0
 ?? () 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 182629, 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.