From Bugzilla Helper: User-Agent: Mozilla/4.78 [en] (X11; U; Linux 2.4.9-7 i686) Description of problem: If I launch a 2nd Xsession on one display, Nautilus opens in the first screen. When that 2nd Xsession ends, Nautilus stays open in the first but all of the side-bars crash. Possibly related, the 2nd Xsession has no desktop icons. Other gnome startup apps work OK. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Start from a default .gnome with "start-here" (May occur from non-default .gnome as well) 2. Login to an X session. 3. Start a 2nd X session: startx -- :1 4. Switch to the first X session: Ctrl-Alt-F7 5. Go back and log out of X session 2 Actual Results: At step 3, things look OK, but no Nautilus. At step 4: there it is in screen :0 At step 5: that 2nd nautilus is now unhappy. Expected Results: X session :1 should work just like X session :0 Additional info: Probably doesn't affect many people since most people only do one Xsession.
I have the same problem. Any time a user is logged in to the same server more than once, all nautilus sessions start on the first X session created. All subsequent sessions are useless as there is no file manager. Is there a workaround for this? I have several users that need to be logged in on more than one terminal at a time. What's more, I haven't been able to figure out how to switch gnome back to gmc (it doesn't seem to be in the toolkit anyway).
I found that deleting the /tmp/orbit-username directory prevents this problem. So, the proper workaround would probably be to set a different ORBit directory or a different ORBit username, but I don't think that is possible. (If not, it should be.) I don't know the consequences of regularly deleting /tmp/orbit-user, but it might work. A possible ugly hack would be to create a set of ORBit lib files with /tmp/orbit- changed, and set LD_LIBRARY_PATH for the 2nd server.
I'm told that this is relatively easy to get working now (there is a way to convince bonobo-activation to make a component per-display). But there's still some engineering involved.
I ran into the bug using Xnest. In /etc/X11/gdm/gdm.conf, I set: [xdmcp] Enable=1 and then ran: Xnest -query hostname :1 & I logged onto the display manager using gnome. The nautilus window appeared in the main window, not the nested window. The nautilus program seems stable, though. That is, no crashes.
*** This bug has been marked as a duplicate of 54719 ***