zenity crashed with SIGSEGV in g_closure_invoke()

[dasunsrule32]

gnome-shell froze, so I had to ctrl+alt+backspace. Logged back in and this popped up. Thanks.

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 x86_64
NonfreeKernelModules: openafs nvidia
ApportVersion: 2.0.1-0ubuntu4
Architecture: amd64
Date: Tue Apr 10 08:21:44 2012
ExecutablePath: /usr/bin/zenity
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: zenity --list --checklist --text Choose_Java_versions_to_DELETE_(if_any)! --column Choose --column Version FALSE /usr/lib/jvm/java-6-sun FALSE /usr/lib/jvm/java-6-sun-1.6.0.26 FALSE /usr/lib/jvm/java-6-sun-1.6.0.30
ProcEnviron:
 TERM=screen-bce
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x40e33d: testb $0x8,0x5e(%rdi)
 PC (0x0040e33d) ok
 source "$0x8" ok
 destination "0x5e(%rdi)" (0x0000005e) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: zenity
StacktraceTop:
 ?? ()
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: zenity crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to precise on 2012-02-24 (53 days ago)
UserGroups:

[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 #979019, 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.