Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 38485 - GAIM 0.72 crashes in common situations. 0.74 doesn't crash in the same situations.
Summary: GAIM 0.72 crashes in common situations. 0.74 doesn't crash in the same situat...
Status: RESOLVED WORKSFORME
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gaim Bugs Crew
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-01-16 22:57 UTC by Decade
Modified: 2004-01-22 05:40 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Decade 2004-01-16 22:57:28 UTC
GAIM 0.72 crashes while doing many common tasks, such as selecting certain people's names in the buddy list. I haven't played with it enough to determine a pattern.

Rather, we've decided to install GAIM 0.74, which doesn't crash for us as far as we can tell, but isn't marked stable. Therefore, if we are forgetful and "emerge -u world", we downgrade to GAIM 0.72 and the program is less stable.

I'm guessing it's less trouble to mark GAIM 0.74 stable than to bother with GAIM 0.72.

Reproducible: Always
Steps to Reproduce:
1. Sign on.
2. Build a decently diverse buddy list.
3. Select everybody's name systematically in the buddy list.

Second problem:
1. emerge -u world
Actual Results:  
Program crashed, eventually. 
 
Second problem: 
Downgrade to less stable GAIM. 

Expected Results:  
1. Not crash. Show buddy info or something. I haven't quizzed the actual user 
yet. 
 
2. Not downgrade. We're happier with this version. 

Portage 2.0.49-r21 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r3, 
2.4.22-gentoo-r2) 
================================================================= 
System uname: 2.4.22-gentoo-r2 i686 AMD Athlon(tm) XP 2500+ 
Gentoo Base System version 1.4.3.10 
distcc 2.11.1 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) 
[disabled] 
ACCEPT_KEYWORDS="x86" 
AUTOCLEAN="yes" 
CFLAGS="-O2 -march=athlon-xp -pipe" 
CHOST="i686-pc-linux-gnu" 
COMPILER="gcc3" 
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.1/share/config /usr/kde/3/share/config /usr/share/config /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /var/qmail/control" 
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" 
CXXFLAGS="-O2 -march=athlon-xp -pipe" 
DISTDIR="/usr/portage/distfiles" 
FEATURES="autoaddcvs ccache sandbox" 
GENTOO_MIRRORS="ftp://ftp.ucsb.edu/pub/mirrors/linux/gentoo/" 
MAKEOPTS="-j2" 
PKGDIR="/usr/portage/packages" 
PORTAGE_TMPDIR="/var/tmp" 
PORTDIR="/usr/portage" 
PORTDIR_OVERLAY="" 
SYNC="rsync://rsync.gentoo.org/gentoo-portage" 
USE="X apm arts avi berkdb bonobo cdr crypt cups directfb encode esd foomaticdb 
gdbm gif gpm gtk2 imlib java jpeg kde libg++ libwww mad mikmod motif mozilla 
mpeg mysql ncurses nls oggvorbis opengl oss pam pdflib perl png postgres python 
qt quicktime readline sdl slang spell ssl svga tcpd tetex truetype x86 xml2 
xmms xv zlib"
Comment 1 Don Seiler (RETIRED) gentoo-dev 2004-01-17 20:29:07 UTC
Yes I'm starting a push to mark 0.75-r5 stable on most platforms.  Please try that version and let me know how it behaves for you.

Thanks.
Comment 2 Don Seiler (RETIRED) gentoo-dev 2004-01-20 11:14:28 UTC
Decade can you rsync and try gaim-0.75-r5?  Please post back here and let me know how it works out for you.
Comment 3 Decade 2004-01-22 01:11:09 UTC
After a few hours of use, my user still hasn't complained about instability with gaim-0.75-r5. I doubt that he's using any advanced features yet.

However, if you don't change GAIM not to depend on encryption, you should mark gaim-encryption stable before marking gaim-0.75-r5 stable. I emerged gaim-0.75-r5 by "KEYWORDS_ACCEPT='~x86' emerge gaim" and gaim-encryption-2.21 came along, too.
Comment 4 Don Seiler (RETIRED) gentoo-dev 2004-01-22 05:40:39 UTC
Yes gaim-encryption is part of the plan also.

I'm going to close this out then.  Re-open if problems pop back up.