gksu crashed with SIGSEGV in gdk_draw_pixbuf()

[dimmaq]

mat@mat-virtual-machine:~$ lsb_release -rd
Description: Ubuntu oneiric (development branch)
Release: 11.10
mat@mat-virtual-machine:~$ apt-cache policy gksu
gksu:
  Installed: 2.0.2-5ubuntu2
  Candidate: 2.0.2-5ubuntu2
  Version table:
 *** 2.0.2-5ubuntu2 0
        500 http://ru.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages
        100 /var/lib/dpkg/status
mat@mat-virtual-machine:~$

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gksu 2.0.2-5ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
Date: Mon Sep 19 21:23:57 2011
ExecutablePath: /usr/bin/gksu
ProcCmdline: gksudo --preserve-env --desktop /usr/share/applications/ubiquity-gtkui.desktop -- /usr/bin/ubiquity gtk_ui
SegvAnalysis:
 Segfault happened at: 0x7f62e8130ff8 <gdk_draw_pixbuf+120>: cmp %rax,(%rdx)
 PC (0x7f62e8130ff8) ok
 source "%rax" ok
 destination "(%rdx)" (0x10c38348fb894853) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gksu
StacktraceTop:
 gdk_draw_pixbuf () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
 ?? () from /usr/lib/libgksu2.so.0
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gksu crashed with SIGSEGV in gdk_draw_pixbuf()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

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