zenity crashed with SIGSEGV in g_cclosure_marshal_VOID()

[Majestyx]

i will i start the awoken-icon-theme-customization - then crashes

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: zenity 3.4.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-20.33-generic-pae 3.2.12
Uname: Linux 3.2.0-20-generic-pae i686
ApportVersion: 2.0.1-0ubuntu2
Architecture: i386
Date: Thu Apr 12 19:23:23 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/zenity
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120328)
ProcCmdline: zenity --title=AWOKEN\ 2.4\ Customization\ script --list --text=Select\ an\ option\ from\ below:\\t\\t\\t\\t\\t\\t\\t --radiolist --column --column TRUE Take\ a\ look\ at\ the\ README\ pdf\ with\ instructions FALSE Customize\ Clear\ version FALSE Customize\ Dark\ version FALSE Customize\ White\ version FALSE Colorize\ the\ iconset FALSE Remove\ a\ colored\ iconset FALSE Quit --height=400
ProcEnviron:
 SHELL=/bin/bash
 TERM=xterm
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
SegvAnalysis:
 Segfault happened at: 0x80551ad: testb $0x8,0x32(%eax)
 PC (0x080551ad) ok
 source "$0x8" ok
 destination "0x32(%eax)" (0x00000032) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: zenity
StacktraceTop:
 ?? ()
 g_cclosure_marshal_VOID(int0_t) () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: zenity crashed with SIGSEGV in g_cclosure_marshal_VOID()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

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