Found the root cause: I was sharing the .purple configuration directory
between two Ubuntu installations (symlink between homes), Feisty and
Gutsy. When I recreated the Pidgin configuration from scratch in Gutsy,
the crashes stopped reproducing.
In more detail, I found that the accounts.xml file
not a glib bug
** Changed in: glib2.0 (Ubuntu)
Status: Incomplete = Invalid
--
[gutsy] Pidgin 2.1.0 crashes on the freshly updated libc6
https://bugs.launchpad.net/bugs/130852
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
thank you for the update, this use is not supported, you should have the
configuration corresponding to the version of ubuntu you are using,
closing the bug
** Changed in: pidgin (Ubuntu)
Status: Incomplete = Invalid
--
[gutsy] Pidgin 2.1.0 crashes on the freshly updated libc6
No, running Pidgin under valgrind does not crash. I use this as a
workaround to be able to use Pidgin (albeit quite slow) :).
--
[gutsy] Pidgin 2.1.0 crashes on the freshly updated libc6
https://bugs.launchpad.net/bugs/130852
You received this bug notification because you are a member of Ubuntu
reassigning to glib2.0, g_free is called before. please investigate if
that call is valid. we had a glib2.0 update these days as well.
** Changed in: glib2.0 (Ubuntu)
Sourcepackagename: glibc = glib2.0
--
[gutsy] Pidgin 2.1.0 crashes on the freshly updated libc6
Thanks for your bug report. Could you try to get a valgrind log for the
crash (you can follow the instructions on
https://wiki.ubuntu.com/Valgrind)?
** Changed in: glib2.0 (Ubuntu)
Importance: Undecided = Medium
Assignee: (unassigned) = Ubuntu Desktop Bugs
Status: New = Incomplete
