Red Hat Bugzilla – Bug 50212
nautilus doesn't start on any display besides :0
Last modified: 2007-03-26 23:47:25 EDT
nautilus-188.8.131.52-1 fails to start on any display besides :0. This is
easily reproduced; change the default display number in gdm.conf, and
nautilus will hang on every login before it even displays anything. It
seems to get stuck waiting for select() ...
Works for me if I add a display in gdm, or change the only display to 1. Maybe
my interpretation of "change the default display number" is different from yours?
Exactly what is the line in gdm.conf that you have?
If I create a new profile and run startx -- :1, nautilus won't start; if I
strace it from the console, it seems to hang on a select call (lots of strings
beginning with 'GIOP' are being read() at the time, if that's useful info.)
The same profile starts nautilus flawlessly every time on :0.
This is all with nautilus-184.108.40.206-1.
I should add that having a display running on :0 doesn't seem to affect how
nautilus behaves on other displays.
Where did you get nautilus-220.127.116.11-1? Our current is nautilus-1.0.4-25.
Does it happen with whatever is latest in rawhide?
nautilus-18.104.22.168-1 was from rawhide (18 july 2001.)
i'll do a clean install of roswell this weekend and see if that fixes it.
Roswell fixed it. Thanks
Actually, I lied -- it's still broken. If I create users A, B, and C and log in
simultaneously on :0, :1, and :2, nautilus only starts on :0. Each user's
profile works properly when logged in on :0.
The multiple-users thing is a fam problem. Alex was looking into that,
so I've assigned him the bug.
*** This bug has been marked as a duplicate of 50580 ***