Re: Problem starting a remote session...
Re: Problem starting a remote session...
- Subject: Re: Problem starting a remote session...
- From: "Mark J. Reed" <email@hidden>
- Date: Fri, 7 Oct 2005 19:30:54 -0400
The problem is that when you start up your local X session, you're
starting a window manager with it - presuambly quartz-wm.
Gnome-session on the remote comptuer is also trying to start a window
manager, and you can only have one, hence the crash.
I don't think the Gnome window manager will work very well on the
Apple X11 rootless display anyway. Do you really need an entire
session on the Linux server ,or can you just run the apps you want
directly without starting up the full gnome session manager?
On 10/7/05, Steven Hamblin <email@hidden> wrote:
>
> Hello,
>
> I'm trying to use X11 so that I can run a remote session from my lab's Linux
> boxes - i.e., I'm trying to use my Powerbook to login to the Linux machine
> in the lab and start a session, which if I recall correctly would make my
> powerbook the 'server' and the Linux machine the 'client'. (I'm sorry, I've
> just starting really getting into the *nix side of things, so forgive my
> lack of detailed knowledge).
>
> I'm using OS X 10.4.2, and the Linux machine is running Fedora. Apparently,
> it's also using GNOME (which I used Fink to install on my machine). Having
> said that, I cobbled together a few instructions that I was following,
> without really understanding what half of them did, and it went like this:
>
> After starting X11.app on my machine, I did an ssh into the other machine:
> ssh -X myname@labcomputer, which worked fine. Then, I typed:
> gnome-session[enter], and got the following pile of blah in the xterm
> window,
>
> SESSION_MANAGER=local/labcomputer:/tmp/.ICE-unix/22385
> Window manager warning: Log level 32: could not find XKB extension.
> Window manager warning: Screen 0 on display "localhost:10.0" already has a
> window manager
> Window manager warning: Log level 32: could not find XKB extension.
> Window manager warning: Screen 0 on display "localhost:10.0" already has a
> window manager
> The program 'nautilus' received an X Window System error.
> This probably reflects a bug in the program.
> The error was 'BadAtom (invalid Atom parameter)'.
> (Details: serial 257 error_code 5 request_code 18 minor_code 0)
> (Note to programmers: normally, X errors are reported asynchronously;
> that is, you will receive the error a while after causing it.
> To debug your program, run it with the --sync command line
> option to change this behavior. You can then get a meaningful
> backtrace from your debugger if you break on the gdk_x_error() function.)
>
> On my end, the Fedora splash screen shows up, gets halfway through loading,
> and then does nothing and I have to click on it to make it go away.
>
> Could someone with more experience in these matters point in the right
> direction to untangle this? I definitely appreciate any assistance that
> might be offered.
>
>
> Cheers,
>
> Steven Hamblin
> --
> Master of Arts student
> Department of Psychology, University of Alberta.
> Office: P-319F, Biological Sciences
> Phone: 492-6681 e-mail: email@hidden
>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> X11-users mailing list (email@hidden)
>
> This email sent to email@hidden
>
--
Mark J. Reed <email@hidden>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden