I'm using KDM as my display manager. I have a user who is configured to start,
by default, the fluxbox window manager when he logs in (ie, ~/.Xclients-default
contains "exec fluxbox"). When this user logs into kdm the first time, kdm
starts the X server (stippled grey background comes up), and then crashes out of
X back into kdm. When this user then logs into kdm the second time, kdm
correctly starts up X and fluxbox.
This appears to be a race condition with kdm misordering X authentication setup
the first time, since the X server log file contains, after the first failed X
startup, lots of messages which look like:
AUDIT: Fri Aug 16 06:14:33 2002: 930 X: client 2 rejected from local host
Presumably, kdm is execing ~/.Xclients-default before all the Xauth stuff is
correctly configured.... This is on a relatively slow machine (K6-III 600), so
it might be due to the slow CPU.
This is still true in beta5
This bug appears to be universal. I see a similar thing on a faster system
(Athlon 650). On a stock beta5 system, I created a user, logged in as that
user, and ran switchdesk and selected twm. I then tried to log in through kdm.
It started the X server, painted the background blue, then failed to start twm.
No errors were logged this time.
kdm is completely unusable because of this bug -- it apparently cannot start any
environment except KDE / GNOME
This still happens with kdebase-3.0.3-6
Furthermore, now that I've started testing out KDE, it appears to be universal
even for KDE / GNOME. The very first time I boot my system, logins to kdm work
but fail to start the environment (KDE / GNOME / any wm). All subsequent logins
will work, until I reboot.
as i know it's fixed in current fc3 (or fc2)