Someone else already filed a request (bug #74770) to backport Gaim 2.0.0
beta5 to Edgy.
--
/usr/lib/gaim/libjabber.so crashed in jabber_get_next_id()
https://launchpad.net/bugs/71848
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bug
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
** Changed in: gaim (Ubuntu)
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?
** Changed in: gaim (Ubuntu)
Status: Unconfirmed => Confirmed
--
/usr/lib/gaim/libjabber.so crashed in jab
Thank you for forwarding that upstream
--
/usr/lib/gaim/libjabber.so crashed in jabber_get_next_id()
https://launchpad.net/bugs/71848
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
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.
** Bug watch added: SourceForge.net Tracker #1605319
http://sourceforge.net/support/tracker.php?aid=1605319
** Also affects: gaim (upstream) via
http://sourceforge.net/s
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 attachmen
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
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.
** Attachment added: "2nd complete crash report"
http://librarian.lau
** Attachment added: "Complete crash report"
http://librarian.launchpad.net/5070428/_usr_bin_gaim.1001.crash
--
/usr/lib/gaim/libjabber.so crashed in jabber_get_next_id()
https://launchpad.net/bugs/71848
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mai
