gksu crashed with SIGSEGV in gdk_window_set_opacity()

[sebz]

Binary package hint: gksu

lsb_release -rd

Description: Ubuntu lucid (development branch)
Release: 10.04

ProblemType: Crash
Architecture: i386
Date: Sun Jan 24 20:06:42 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/gksu
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release Candidate i386 (20091020.3)
Package: gksu 2.0.2-2ubuntu1
ProcCmdline: /usr/bin/gksu --desktop /usr/share/applications/update-manager.desktop -- /usr/usernamein/synaptic --hide-main-window --non-interactive --parent-window-id 75497511 -o Synaptic::closeZvt=true --progress-str Veuillez\ patienter,\ cela\ peut\ prendre\ du\ temps. --finish-str La\ mise\ à\ jour\ est\ terminée --set-selections-file /tmp/tmpF34SbI
ProcEnviron:
 LANG=fr_FR.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-10.14-generic
SegvAnalysis:
 Segfault happened at: 0x225c8e <gdk_window_set_opacity+46>: mov (%esi),%eax
 PC (0x00225c8e) ok
 source "(%esi)" (0x616c2f65) 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()
Uname: Linux 2.6.32-10-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

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