/usr/lib/gaim/libjabber.so crashed in jabber_get_next_id()

[Alex Muntada]

I was closing my IRC and Jabber connections and suddenly Gaim crashed (never happened before).

I'm going to add the full crash report, but the segmentation fault happens in libjabber.so, near the jabber_get_next_id() call.

It seems that this issue has not been previously reported, after searching in launchpad.

[Alex Muntada (alex.muntada)]

It happened again, so I'm attaching also the crash report.

As in the previous crash, I was quickly disabling (i.e. closing) the accounts after pressing Ctrl-A, then Gaim seemed to freeze for a few seconds and finally crash.

[Alex Muntada (alex.muntada)]

It happened again, but this time on an other computer: my laptop.

This time, I wasn't closing all my connections quickly, so this doesn't
seem to be the problem. However, I was trying to disable a Jabber
connection that couldn't be established (I think that server had been
some hardware problems recently). While trying to remember if
this could've been happening the other 2 times when Gaim crashed,
it seems probable that the same Jabber server could be down too.
Thus, this issue could be related to Jabber server unavailability at
the time the user presses the enable/disable checkbox.

Hope that this helps narrowing the search. Let me know if I can
provide further details.

[Alex Muntada (alex.muntada)]

Confirmed: I closed all my active connections, so I have only enabled the one that cannot reach the Jabber server I was talking about before. Then, tried to disable that and Gaim crashed again. Hence, this issue is related to Jabber servers unavailability.

BTW, this will be my last crash attachment unless someone else asks me to upload more.

[Alex Muntada (alex.muntada)]

Since I couldn't find a similar bug open in gaim.sf.net, I submitted a new bug report there and added the upstream link.

[Sebastien Bacher (seb128)]

Thank you for forwarding that upstream

[Alex Muntada (alex.muntada)]

I've confirmed that this issue has been addressed in Gaim 2.0.0 beta5 (Feisty Herd 1), as pointed by upstream.

Should I mark this ticket as Fixed or should it be backported to Edgy?

[Sebastien Bacher (seb128)]

Marking as fixed since it's fixed with the feisty version, for backports we can open a backport task. We will probably not backport that fix to feisty though, it has only one duplicate at the moment and we can't backport every single fix, that would be too much work

[Alex Muntada (alex.muntada)]

Someone else already filed a request (bug #74770) to backport Gaim 2.0.0 beta5 to Edgy.