Version:            (using KDE KDE 3.4.1)
Installed from:    Gentoo Packages
Compiler:          gcc version 3.3.5-20050130 (Gentoo 3.3.5.20050130-r1, ssp-3.3.5.20050130-1, pie-8.7.7.1) Package gcc-3.3.5.20050130-r1
OS:                Linux

I'm having the same problem as bug 102046 (but I guess adding comments to a bug marked as 'resolved' doesn't get an response); at least, I get hangs at login using KDE 3.4.1 with gentoo, and killing klauncher allows the login to proceed.  (Further details in the gentoo bug I filed: <http://bugs.gentoo.org/show_bug.cgi?id=99866>.)

Unfortunately, even though I have debug symbols in my KDE build, if I try to attach gdb to the hung klauncher process (I do 'ps uxaww | grep klauncher' to get the pid, 'gdb /usr/kde/3.4/bin/klauncher', then in gdb 'attach nnnn' where nnnn is the pid), I just get this:

Attaching to program: /usr/kde/3.4/bin/klauncher, process nnnn
Failed to read a valid object file image from memory.
0xXXXXXXXX in ?? ()

where 0xXXXXXXX is some random hex value.  The resulting stack trace (from 'where') is garbage (just hex values, some of which are obviously wrong, like 0x0a).

*PLEASE* advise on what I can do to help track this down.  It completely prevents me from using KDE 3.4.1.  (There's no problem in KDE 3.3.2, so I'm using that.)