FS#2365 - gaim crashes after a while

Attached to Project: Arch Linux
Opened by Glenn Matthys (RedShift) - Sunday, 13 March 2005, 12:25 GMT
Last edited by Dale Blount (dale) - Sunday, 13 March 2005, 16:35 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To dorphell (dorphell)
Architecture not specified
Severity Medium
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

After a while gaim crashes with these messages on the terminal:

Gaim has segfaulted and attempted to dump a core file.
This is a bug in the software and has happened through
no fault of your own.

It is possible that this bug is already fixed in CVS.
If you can reproduce the crash, please notify the gaim
maintainers by reporting a bug at
http://gaim.sourceforge.net/bug.php

Please make sure to specify what you were doing at the time,
and post the backtrace from the core file. If you do not know
how to get the backtrace, please get instructions at
http://gaim.sourceforge.net/gdb.php. If you need further
assistance, please IM either RobFlynn or SeanEgn and
they can help you.
Aborted

Even when I'm doing nothing (it's just sitting in the systray), gaim crashes.
Using MSN protocol. I have this on every computer. Note that the issue only occurs after 1.1.1 (I think).
This task depends upon

Closed by  dorphell (dorphell)
Tuesday, 05 April 2005, 00:36 GMT
Reason for closing:  Fixed
Comment by dorphell (dorphell) - Sunday, 13 March 2005, 16:50 GMT
I suggest you follow what that says. This does not sound like an arch-related bug. Report it to them.

p.s. you may want to be more specific than "after a while, it barfs"
Comment by arjan timmerman (blaasvis) - Monday, 14 March 2005, 08:22 GMT
there is a know problem with 1.1.3 see also gaim.sf.net. It is related to glib2.6.

Are you running 1.1.4 ?
Comment by Glenn Matthys (RedShift) - Monday, 14 March 2005, 12:02 GMT
Yes I am running 1.1.4. I've seen bug reports @ gaim for 1.1.3, I posted it here to find out if other people were experiencing the same issue so it's not an over-optimizing fault or stuff like that.

Dorphell: the only thing it does after a while is barfing.
Comment by Damir Perisa (damir.perisa) - Sunday, 03 April 2005, 15:36 GMT
<daperi> 2365: bugsquashing day decision: it's definitely not a packaging problem and has to be solved upstream

probably it will be in 1.2.0

Loading...