gtk app (gajim) crashed with SIGSEGV in IA__gtk_accel_groups_activate()

[Muelli]

Binary package hint: python2.6

After trying to close two chat windows quickly.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/python2.6
Package: python2.6-minimal 2.6.2-0ubuntu1
ProcCmdline: /usr/bin/python -OO gajim.py
Signal: 11
SourcePackage: python2.6
StacktraceTop:
 IA__gtk_accel_groups_activate (object=0x3cafd80, accel_key=65307,
 IA__gtk_window_activate_key (window=0x3cafd80,
 gtk_window_key_press_event (widget=0x20e56e0,
 _gtk_marshal_BOOLEAN__BOXED (closure=0x2891ba0,
 IA__g_closure_invoke (closure=0x2891ba0,
Title: python2.6 crashed with SIGSEGV in IA__gtk_accel_groups_activate()
Uname: Linux 2.6.31-14-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy fuse kvm libvirtd lpadmin netdev plugdev powerdev scanner tty vboxusers video

[Muelli (ubuntu-bugs-auftrags-killer)]

Forwarded to https://bugzilla.gnome.org/show_bug.cgi?id=599971

[Apport retracing service (apport)]

StacktraceTop:gtk_accel_label_get_property (
?? ()
?? ()
?? ()
?? ()

[Apport retracing service (apport)]

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libgcc1: installed version 1:4.4.1-4ubuntu8, latest version: 1:4.3.3-5ubuntu4
libselinux1: installed version 2.0.85-2ubuntu2, latest version: 2.0.65-5build1
libstdc++6: installed version 4.4.1-4ubuntu8, latest version: 4.3.3-5ubuntu4
libc6: installed version 2.10.1-0ubuntu15, latest version: 2.9-4ubuntu6.1
dpkg: installed version 1.15.4ubuntu2, latest version: 1.14.24ubuntu1

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

[Muelli (ubuntu-bugs-auftrags-killer)]

Reopening as the stacktrace is actually good.