gksu crashed with SIGSEGV in gdk_window_set_opacity()

[Geo_2005]

Binary package hint: gksu

telminal closed

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gksu 2.0.2-2ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-8.13-generic 2.6.35-rc5
Uname: Linux 2.6.35-8-generic i686
Architecture: i386
Date: Sat Jul 17 10:41:47 2010
ExecutablePath: /usr/bin/gksu
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
ProcCmdline: gksu --description /usr/share/applications/synaptic.desktop /usr/sbin/synaptic
ProcEnviron:
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xc5c26e <gdk_window_set_opacity+46>: mov (%esi),%eax
 PC (0x00c5c26e) ok
 source "(%esi)" (0x61706573) not located in a known VMA region (needed readable region)!
 destination "%eax" 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:1720): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

[Apport retracing service (apport)]

StacktraceTop:
 IA__gdk_window_set_opacity (window=0x61706573, opacity=0.5)
 fadeout_callback (fadeout=0x9126ae8) at libgksu.c:326
 g_idle_dispatch (source=0x91269f0, callback=0x9098af8,
 g_main_context_dispatch (context=0x90a1560)
 g_main_context_iterate (context=0x90a1560,

[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.