gksu crashed with SIGSEGV in gdk_window_set_opacity()

[Jo Becaus]

Binary package hint: gksu

same as previous but for lang= be

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
Date: Wed Apr 7 19:09:34 2010
ExecutablePath: /usr/bin/gksu
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
ProcCmdline: /usr/bin/gksu --desktop /usr/share/applications/update-manager.desktop -- /usr/sbin/synaptic --hide-main-window --non-interactive --parent-window-id 50331687 -o Synaptic::closeZvt=true --progress-str Een\ ogenblik\ geduld,\ dit\ kan\ even\ duren. --finish-str De\ update\ is\ voltooid --set-selections-file /tmp/tmpAKiG_3
ProcEnviron:
 LANG=nl_BE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f36f71c4a11 <gdk_window_set_opacity+33>: cmp %rax,(%rdx)
 PC (0x7f36f71c4a11) ok
 source "%rax" ok
 destination "(%rdx)" (0x2072656577206544) 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 lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 IA__gdk_window_set_opacity (window=0x7f36f83109ed,
 fadeout_callback (fadeout=0x1dee660)
 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.