Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 41119

Summary: Gaim wont work on this gentoo-dev-sources-2.6.3_rc1
Product: Gentoo Linux Reporter: neuron
Component: [OLD] Core systemAssignee: Gaim Bugs Crew <gaim-bugs>
Status: RESOLVED INVALID    
Severity: critical    
Priority: High    
Version: unspecified   
Hardware: x86   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description neuron 2004-02-10 08:35:27 UTC
Upgraded to gentoo-dev-sources-2.6.3_rc2, realized my gaim wasn't working, recompiled it quite a lot of times trying to figure out what was wrong.

it starts if I rm -rf ~/.gaim, but not if I cp my old accounts.xml working.

strace shows:
fcntl64(4, F_GETFL)                     = 0 (flags O_RDONLY)
fstat64(4, {st_mode=S_IFIFO|0600, st_size=0, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40ab4000
_llseek(4, 0, 0xbfff2b2c, SEEK_CUR)     = -1 ESPIPE (Illegal seek)
read(4,

vmware wasn't working in 2.6.3, so I rebooted back into 2.6.2 and to my suprise gaim worked fine there.  Note that I recompiled gaim with -march=athlon-xp -O2 -pipe -fomit-frame-pointer and it still didn't work on 2.6.3.  And I'm using reiserfs.

Reproducible: Always
Steps to Reproduce:
1. boot gentoo-dev-sources-2.6.3_rc2
2. start gaim with accounts.xml in place.

Actual Results:  
gaim fails to start.

Expected Results:  
started

Portage 2.0.50-r1 (default-x86-1.4, gcc-3.3.2, glibc-2.3.3_pre20040207-r0,
2.6.2-gentoo)
=================================================================
System uname: 2.6.2-gentoo i686 AMD Athlon(tm)
Gentoo Base System version 1.4.3.13
distcc 2.12.1 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled]
Autoconf: sys-devel/autoconf-2.59
Automake: sys-devel/automake-1.8.2
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CFLAGS="-march=athlon-xp -O3 -pipe -fomit-frame-pointer -msse -m3dnow
-mfpmath=sse,387 -funroll-loops"
CHOST="i686-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config
/usr/kde/3.2/share/config /usr/kde/3/share/config /usr/share/config
/usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/
/usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/
/usr/share/texmf/xdvi/ /var/bind /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
CXXFLAGS="-march=athlon-xp -O3 -pipe -fomit-frame-pointer -msse -m3dnow
-mfpmath=sse,387 -funroll-loops"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache sandbox"
GENTOO_MIRRORS="http://212.219.247.13/sites/www.ibiblio.org/gentoo/
http://212.219.247.10/sites/www.ibiblio.org/gentoo/
http://mirrors.sec.informatik.tu-darmstadt.de/gentoo
http://mirror.pudas.net/gentoo http://212.219.247.21/sites/www.ibiblio.org/gentoo/"
MAKEOPTS="-j1"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage"
USE="3dnow X aalib aavm alsa apm avi berkdb bonobo cdr composite crypt cups dga
directfb dvd encode foomaticdb gdbm gif gpm gtk gtk2 gtkhtml guile imlib java
jpeg libg++ libwww mad mmx motif mozilla moznocompose moznoirc moznomail mpeg
mtrr ncurses nls nptl oggvorbis opengl pdflib perl png python qt quicktime
readline ruby samba sdl slang spell sse ssl svga tcltk tcpd tetex truetype x86
xml2 xmms xv xvid zlib"
Comment 1 neuron 2004-02-10 10:31:06 UTC
typo'd my notes, bug is in kernel gentoo-dev-sources-2.6.3_rc1, rc2 is untested.
Comment 2 Don Seiler (RETIRED) gentoo-dev 2004-02-10 12:33:11 UTC
So if you remove your .gaim folder, can you start gaim and re-create your accounts from scratch and then have it usable again?
Comment 3 neuron 2004-02-10 13:47:13 UTC
tried some more, if I rm -rf .gaim it works.
if I start gaim with standard settings it works.
if I cp my accounts.xml over it doesen't work.

however the same accounts.xml works on older kernels.

(yeah I know, this is an odd one ;) ).
Comment 4 Don Seiler (RETIRED) gentoo-dev 2004-02-11 13:40:54 UTC
So you can blow away your .gaim folder, start gaim, and manually re-add your accounts and use gaim just fine?
Comment 5 neuron 2004-02-11 17:13:10 UTC
no, I dunno what screws up, the length of the file perhaps, but something makes gaim crash (and on that kernel only).

I could try adding one account and see if that works.
When I tested I readded all of em.
Comment 6 Don Seiler (RETIRED) gentoo-dev 2004-02-12 14:40:27 UTC
Well all of my boxes are development-sources-2.6.2 and gaim works fine for me.  I'd like to find some more people with this problem.
Comment 7 Don Seiler (RETIRED) gentoo-dev 2004-02-12 14:53:39 UTC
gentoo dev johnm doesn't think it can be kernel related.  He suggests you emerge and make use of memtest86 or memtest86+ to see if there is something up with your memory.  He is using gentoo-dev-sources-2.6.3_rc2-r1.
Comment 8 neuron 2004-02-13 04:45:23 UTC
gaim runs fine on 2.6.2, but not on 2.6.3-rc1 Don Seiler.

and I dobut it's a memory problem, when I can reboot between 2.6.2 and 2.6.3 and "turn the problem on and off" like that very easily.

That's what makes me think it's a kernel bug, especially when the strace shows a seek error.

And this happens every time in 2.6.3 and never in 2.6.2.

If you still want me to run a memtest I will, but I wont be able to do that until saturday probably.
Comment 9 Robert Davis 2004-02-16 08:38:40 UTC
Reiser3 or 4?  4 is still unstable for some people.  It could be the kernel in the reiserfs code (most likely) or even the IDE code (less likely).  You could also try the same vanilla 2.6 kernel.  It might be a patch in gentoo-dev.
Comment 10 neuron 2004-02-16 09:08:07 UTC
reiser3, and I thought it might be that, which is why I filed it in kernel bugs ;)
Comment 11 Robert Davis 2004-02-16 14:30:59 UTC
Running 2.6.3-rc2-mm1 now with no problems with gaim and also vmware w/update50.
Comment 12 neuron 2004-02-19 05:30:00 UTC
This was an error on the filesystem inside a loopback device.  Some fixes in reiserfs in 2.6.3 must have changed from ignoring the error to not reporting it and hanging on it or something.