Had this problem on 2 different installations of gentoo, 1 compiled from source, one built from the Gentoo 1.4 CD's with GRP. Both used the same CFLAGS CFLAGS="-O3 -march=i686 -funroll-loops -pipe" Once xfree86 is updated to 4.3.0-r3, ksmserver segfaults every time as soon as it starts on boot. Rebuilding kde (updating to version 3.1.4) doesn't change this, even if the rebuild occurs after the new xfree is emerged (so presumably it's not a library dependancy) Reverting back to the 4.3.0-r2 binary package solves the problem immediately. I haven't tried building 4.3.0-r2 from source yet to see if it's a build issue. Reproducible: Always Steps to Reproduce: 1. Install xfree from GRP (version 4.3.0-r2) 2. Install KDE (source or GRP) 3. Upgrade xfree to version 4.3.0-r3 Actual Results: KDM boots fine. KDE boots until the very last step "Starting the session manager", and the ksmserver segfaults Computer is a PII 350, 256MB RAM. This was done both with X on an NFS share and on a local drive (I tested to make sure NFS wasn't the problem)
Went back to my source build and masked out the xfree 4.3.0-r3 package. Compiled, 4.3.0-r2 and everythings fine now on that build as well. So, it's not faulty compiler, it's definitely the xfree ebuild that's faulty. I have binary packages of the problem ebuilds if anybody wants a copy. One idiosynchracy of my setup, is that I'm running x in a chroot environment. Given that this looks like a library issue though, it's probably not relevant. l8r, Liam
I have JUST emerged Gentoo in a shining new Athlon XP 2600 (Barton) 512 MB RAM, 120GB HD, Radeon 9200SE, ASUS A7N8X-X. After fiddling a bit to enable hardware acceleration, I made X load fine using windowmaker, emerged mozilla and kde 3.1.4. XFree is 4.3.0-r3. KDE was compiled using QT 3.2.2-r1. And although kdm is working, and the first time configuration wizard works, KDE always crashes whenever I try to login. application can be called and used under WM, though. I think it is related to this bug. I reemerged everything (emerge -e world) using "-O2 -march=athlon-xp -pipe" , to no avail.
Interestingly, my compile box (not the box it's running on, the box it's compiled on) is also an Athlon-XP... although, for obvious reasons, I'm not using the xp compile flags, only the i686 ones. So if this is unreproducible on other systems, that may be the common thread.
Same on a P3-500 (compaq ipaq non-legacy free) 128M 8.xGB HD CFLAGS="-march=pentium3 -Os -pipe" glibc-2.3.2-r3 gcc-3.2.3-r2 xfree-4.3.0-r3 however, I compiled kde from source using -r3 no-chroot, nfs etc. kde (live cvs build) running on another box works using kdm from that box (xdmcp).
I am having exactly the same problem - I have a Duron 750, running KDE 3.1.4, XFree86 4.3.0-r3, glibc 2.3.2-r3. I am using an ATI Radeon 7500 (is it possible that it's got something to do with the display drivers?). This unit was built entirely from source beginning at stage 1, so there must be a bug somewhere. CFLAGS="-03 -march=athlon -funroll-loops -pipe" You said that XFree86 4.3.0-r2 worked?
It shouldn't be the driver, because this is not working on a i810 (the above compaq ipaq) Nor does it look to be CFLAGS (unless in common flags which are -O2 and -pipe)
> You said that XFree86 4.3.0-r2 worked? Yes: on my boxes, xfree86-4.3.0-r2 works and xfree86-4.3.0-r3 doesn't.
Confirmed -- reverting to xfree-4.3.0-r2 using the ebuild resolves the problem and X starts normally. This bug is legit. Hope somebody fixes it! I'm not a programmer :).
Sorry, that should have read "KDE starts normally".
This bug was also reported via the KDE bugzilla (for KDE 3.2): http://bugs.kde.org/show_bug.cgi?id=62040 There's also a backtrace which indicates that this crash happens inside the X libs. It also seems like this happens only if the DNS domainname can't be resolved, ie. getdomainname(2) returns an error.
Reported as http://bugs.xfree86.org/show_bug.cgi?id=1096
Hi, a fix for this should already be in patchset 2.1.24 and higher of 4.3.0-r3, if you care to remerge. grep for getaddrinfo in the ChangeLog if you want to know more info. grep PATCH_VER /usr/portage/x11-base/xfree/xfree-4.3.0-r3.ebuild to check the patchset version you would get, and do the same to the ebuild in /var/db/pkg to see which patchset version you have. However 4.3.0-r4 will be coming out soon so you might want to hold off if this isn't having a big impact.
