pidgin crashed with SIGSEGV in g_datalist_id_set_data_full()

[Knatchwa]

Binary package hint: pidgin

When closing out of Pidgin on Jaunty 9.04 using AMD64 system I ended up seeing the problem report. Initially it was a delay in closing the program until now.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Disassembly: 0x100000000:
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/pidgin
Package: pidgin 1:2.5.5-1ubuntu1
ProcCmdline: pidgin
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: pidgin
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/libglib-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_datalist_id_set_data_full ()
 g_object_unref () from /usr/lib/libgobject-2.0.so.0
Title: pidgin crashed with SIGSEGV in g_datalist_id_set_data_full()
Uname: Linux 2.6.28-9-generic x86_64
UserGroups: adm admin audio cdrom dialout fuse lpadmin netdev plugdev sambashare video

[Apport retracing service (apport)]

StacktraceTop:?? ()
g_hash_table_remove_internal (hash_table=0x244c140,
weak_refs_notify (data=<value optimized out>)
IA__g_datalist_id_set_data_full (
IA__g_object_unref (_object=<value optimized out>)

[Knatchwa (rl-marr)]

Seems to usually happen after Pidgin has been open for most of the day, while transmission is running, usually can tell there will be a crash when it takes to long to quit out of the program. Yet it does not happen everytime only when it is open for extended periods of time. Anyone else dealing with this, or only me? For that matter do you suggest another program to use that is not Pidgin for your im?

[Rolf Leggewie (r0lf)]

does this ever occur in lucid or later?

[Rolf Leggewie (r0lf)]

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

[Rolf Leggewie (r0lf)]

We're closing this bug since it is has been some time with no response from the original bug reporter. However, if the issue still exists in the latest development version of Ubuntu and you are the original reporter please feel free to reopen with the requested information. If you are not the original reporter, please don't reopen this one but instead file a new bug and reference this one.