pidgin crashed with SIGSEGV in g_type_check_instance_cast()

[ts]

login to ejabberd (xmpp) over ssh-tunnel didn't work because the tunne was down, when the tunnel was up again pidgin (should have) tried to login, but crashed.

n$ lsb_release -rd
Description: Ubuntu quantal (development branch)
Release: 12.10

$ apt-cache policy pidgin
pidgin:
  Installed: 1:2.10.6-0ubuntu2
  Candidate: 1:2.10.6-0ubuntu2
  Version table:
 *** 1:2.10.6-0ubuntu2 0
        500 http://de.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: pidgin 1:2.10.6-0ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
Uname: Linux 3.5.0-15-generic x86_64
ApportVersion: 2.5.2-0ubuntu4
Architecture: amd64
Date: Fri Sep 21 17:09:48 2012
ExecutablePath: /usr/bin/pidgin
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120811.1)
ProcCmdline: pidgin
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fb4184a9e8c <g_type_check_instance_cast+28>: mov (%rax),%rbp
 PC (0x7fb4184a9e8c) ok
 source "(%rax)" (0x700000008) not located in a known VMA region (needed readable region)!
 destination "%rbp" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: pidgin
StacktraceTop:
 g_type_check_instance_cast () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libdbusmenu-gtk.so.4
 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
Title: pidgin crashed with SIGSEGV in g_type_check_instance_cast()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm lpadmin 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 #1053944, 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.