I use XDMCP a lot. I recently tried running nautilus remotely over it, and
discovered that it dies instantly on startup. The problem, I would guess,
is that the object broker isn't getting forwarded to the remote display.
Looks like Yet Another Reason KDE and GMC Are Better Than Nautilus.
I have succesfully run Nautilus over the network through ssh login. I am using the
current IA64 beta.
Doesn't work for me either during s390 testing
Are you running your whole session remotely, or just Nautilus while you are also
logged in elsewhere. GNOME doesn't like two open sessions at once, at the moment.
Whole session. That's kinda by definition when you're doing XDMCP, after all....
This is still true with RH 7.2 release + all errata. nautilus works only
intermittently over XDMCP.
Here's what I experienced this afternoon. I had two machines, thing1 and
thing2. thing1 was configured with gdm listening to XDMCP direct queries, and I
was logged in on thing2 in X. I brought up xnest -query thing1, and it
connected to thing1 and I logged in, selecting gnome. gnome started up in the
nested X server on thing2, but nautilus displayed on thing1. When I then exited
out of xnest and lathered, rinsed, repeated, nautilus displayed in xnest on
thing2 the second time.
At this point we are moving to new development on GNOME 2; it attempts to
address logging in more than once on separate machines in a more comprehensive way.
Backporting the architecture changes required to handle this to GNOME 1 isn't
planned, but things should work or be fairly easy to fix once we migrate to GNOME 2.
*** Bug 55240 has been marked as a duplicate of this bug. ***