Description of Problem:
I can only run one KDE session at once on this multi-user machine.
Steps to Reproduce:
1. Due to another bug, I am using gdm instead of kdm, since kdm doesn't
manage remote displays at all. Set up gdm so that xdmcp is allowed. Go to
2. On another machine, 'X -query roswell' to get a login window.
3. Log in on both machines, one after the other, with KDE sessions
(different non-root users).
The 'initialising system services' checkpoint is never passed, and
eventually the KDE splashscreen goes away, and that's it.
Both sessions start up normally.
If I close the successfully session and try again on the failed one, it works.
This is a major regression!
Does it work if you remove the various "rm /tmp/foo" commands from
After I put 'alias rm=:' at the top, yes, I could log in a second time.
..but I think that must have been chance. I tried again, with a similar
situation (two signal-blocked kdeinit processes from another user lying around)
and couldn't log in. I had to killall -9 kdeinit first, and then I could log in
file, with the original unmodified /usr/bin/startkde.
However, when I did log in that time, kicker didn't appear. I logged out and
back in again, and it did.
This defect is considered MUST-FIX for Fairfax
untested fix in 2.2-1
Tested; didn't work.
It's sgi_fam related. 'chkconfig sgi_fam off; service xinetd restart' has
made the problem go away for now.
I also tried this: enable sgi_fam, start xinetd, log in on display 1, log in
as a different user on display 2, it locks. Stop xinetd, it carries on again.
This is a fam problem - the same is true for anything else using fam (e.g.
Let me know if you can't fix this in time for the 7.2 release; in that case
I'll recompile kdelibs without fam support.
A more detailed how-to-reproduce than the one earlier in this report:
1. chkconfig sgi_fam on; service xinetd restart
2. useradd jim; useradd joe
3. As user jim: switchdesk KDE
4. As user joe: switchdesk KDE
5. Go to runlevel 3
6. As user jim: startx -- :0
7. Wait for session to start.
8. As user joe: startx -- :1
9. Wait for session to start. (It won't.)
Ok. Stupid bug in famd. Upgrading to fam-2.6.4-9 should fix this.
*** Bug 51319 has been marked as a duplicate of this bug. ***
*** Bug 50212 has been marked as a duplicate of this bug. ***