Restarting vino remotely
So I had to restart my home box the other day then realized while away that I forgot to launch vino-session, so I am unable to VNC to my local desktop. This seems to work me into a corner, as while I can still ssh into the computer, I cannot start vino-session from the remote ssh session because of DISPLAY issues. It insists on running from the local desktop. I've been researching since yesterday and haven't found any suggestions that work. Some posts mention xhost +localhost but when I try that I get: X connection to localhost:10.0 broken (explicit kill or server shutdown). I've also tried setting the DISPLAY variable to localhost:0 and localhost:0.0 as well as using the --display= command line parameter of vino-session to no avail. This isn't a critical issue but kinda inconvenient and bound to happen again. So I figured I'd ask the list: faced with a situation like this, what's the best way to bootstrap your way back into being able to VNC into your local desktop (localhost:0)? Thanks! = Fix most Windows problems here: http://vtbsd.net/winhelp/ Sick of ads/pop-ups/spam in AIM/Yahoo/MSN? http://www.jabber.org/ Q: Because it reverses the logical flow of conversation. A: Why is putting a reply at the top of the message frowned upon? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Restarting vino remotely
On Mon, Nov 08, 2004 at 07:15:16AM -0800, Scott I. Remick wrote: So I had to restart my home box the other day then realized while away that I forgot to launch vino-session, so I am unable to VNC to my local desktop. This seems to work me into a corner, as while I can still ssh into the computer, I cannot start vino-session from the remote ssh session because of DISPLAY issues. It insists on running from the local desktop. I've been researching since yesterday and haven't found any suggestions that work. Some posts mention xhost +localhost but when I try that I get: X connection to localhost:10.0 broken (explicit kill or server shutdown). That means your ssh(1) session isn't doing X11 forwarding. ssh has he capability to pose as an X server, usually on localhost:10.0 and transparently forwards all X session traffic over an encrypted tunnel back to your desktop display, but only if you enable it. I've also tried setting the DISPLAY variable to localhost:0 and localhost:0.0 as well as using the --display= command line parameter of vino-session to no avail. Don't do that. First of all, as you've already discovered, it doesn't work. Secondly, you're telling X windows to display on the screen of the remote machine, which won't be a whole lot of use to you. Instead, read about the '-X' and '-Y' options in ssh(1) and the equivalent 'ForwardX11' directive in ssh_config(5). Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgpxjZo6H5Sh3.pgp Description: PGP signature
Re: Restarting vino remotely
--- Matthew Seaman [EMAIL PROTECTED] wrote: That means your ssh(1) session isn't doing X11 forwarding. ssh has he capability to pose as an X server, usually on localhost:10.0 and transparently forwards all X session traffic over an encrypted tunnel back to your desktop display, but only if you enable it. Hmm, well actually it IS enabled in the client I'm using but I'm not understanding why I'd need it. I'm using PuTTY, and under the session config in Connection - SSH - Tunnels the option for Enable X11 forwarding is checked with the X display location set to localhost:0. However, this is leftover from my days of experimenting with Cygwin (which I did have working but decided was too much of a pain). What I do these days is forward port 5900 over SSH for the sake of VNC and so the X11 forwarding isn't necessary. Secondly, you're telling X windows to display on the screen of the remote machine, which won't be a whole lot of use to you. Well my goal here is to restart vino-session, which is command-line and simply needs to spawn into the background, so I don't need to see it. And it seems to ONLY run from the screen of the host system, so (on the contrary) getting vino-session to run on its screen seems to be precisely what I'd want. I feel like I'm misunderstanding something fundamental here, or else I'm not communicating my situation very well. Instead, read about the '-X' and '-Y' options in ssh(1) and the equivalent 'ForwardX11' directive in ssh_config(5). Well I'm not using FreeBSD's ssh as I mentioned, I looked at -X though and saw it was just for the X11 forwarding that I already said I've got enabled in the SSH client I AM using (PuTTY) and I see no mention of -Y in the ssh man page to see what the equivalent PuTTY option might be. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
