zenity crashed with SIGSEGV in g_cclosure_marshal_VOID()

[oursuheAndrea Traverso]

It occurred when i was installing wine fonts by means on winetricks on xubuntu 12.04 beta 2

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: zenity 3.4.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic i686
ApportVersion: 2.0.1-0ubuntu4
Architecture: i386
Date: Tue Apr 17 07:56:45 2012
ExecutablePath: /usr/bin/zenity
InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120327.1)
ProcCmdline: zenity --title Winetricks\ -\ choose\ a\ wineprefix --text What\ do\ you\ want\ to\ do? --list --radiolist --column --column --column --height 500 --width 1010 --hide-column 2 FALSE help View\ help FALSE apps Install\ an\ app FALSE benchmarks Install\ a\ benchmark FALSE games Install\ a\ game TRUE main Select\ the\ default\ wineprefix FALSE unattended Enable\ silent\ install FALSE showbroken Show\ broken\ apps\ (e.g.\ those\ with\ DRM\ problems)
ProcCwd: /home/andrea
ProcEnviron:
 LANGUAGE=it:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
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, void) () 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
 g_signal_emit () 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 #969031, 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.