Hi, Thanks for all your replies. I use a simple ssh terminal at work as well and that's what I'll be using most of the time here. However, it would be nice to get the GUI Desktop up now and again. I've got a simple terminal running (SecureCRT). I've had the Gnome Desktop up and running when I've had a keyboard and a mouse connected directly to the box. I had to make a couple of changes to get the box to boot at all without a keyboard and mouse attached. I forget what they were for the moment, but the instructions were clearly documented and it was obviously a common problem. I suspect the VNC issue relates to Gnome looking in the wrong place for the keyboard and mouse. Most of the messages seems to relate to the keyboard and mouse, but it's not obvious to a Gnome novice what I'm supposed to do about it. I was running the vns4server as an ordinary user, but I've just tried it as root. It doesn't help, and the system complains bitterly if you start a gnome session as a priviledged user. Another possible source of the problem is that I haven't done anything to change the standard booting of the Gnome Desktop. ie Whatever it did to bring up the Desktop when the monitor, keyboard and mouse were directly attached. That might be why some of the messages refer to a windows manager already running. Any more ideas? Thanks Duncan -----Original Message----- From: gnome-list-bounces@xxxxxxxxx [mailto:gnome-list-bounces@xxxxxxxxx]On Behalf Of Guy Rouillier Sent: 13 February 2010 21:04 To: gnome-list@xxxxxxxxx Subject: Re: Remote login Sorry, I did not see the original email. I'm top-posting because most of what I have to say relates to the OP. I've used vnc successfully numerous times, but not in quite awhile; in a work environment simple ssh terminals are used most often, and at home I've switched to running VMs. First off, from the original post, I'm not sure that the server has been properly set up to run X (and hence Gnome.) "could not find XKB extension": XKB is the keyboard and is required in any practical configuration. Have you ever connected to a graphical UI directly on this box to verify that it is set up to run a GUI? Next, I've usually set /etc/vncserver (as root) to automatically start up the required user sessions. You appear to be running vncserver as a regular user. I suppose that works but I have no experience running it that way. Finally, if the server is properly configured and you want to run a GUI, vnc is the right way to go in my opinion. Remote X (cygwin) sends individual windowing commands over the wire and will hence be considerably slower than vnc. The proper way to initialize vnc is to log in via an ssh terminal to start your GUI session. Then you log out and back in via vnc, which should attach directly to your GUI session. On 2/13/2010 2:44 PM, David Harel wrote: > > > Duncan Garland wrote: >> Hi, >> >> No replies in two weeks. Was it a stupid question? Is this the wrong >> list? > Not a stupid question at all. >> Am I completely on the wrong track trying to use a vnc viewer to remotely >> view a gnome session? > I would not use VNC here even though it is possible. Typically I would > use text only interface using ssh (putty.exe will do). > In addition you can install cygwin: http://x.cygwin.com/ and run X11 > apps but I never tried it using ssh session. >> I'll dig some more, but I think I must be googling the wrong keywords >> because I didn't get anywhere last time. >> >> All the best. >> >> Duncan >> >> -----Original Message----- >> From: gnome-list-bounces@xxxxxxxxx >> [mailto:gnome-list-bounces@xxxxxxxxx]On Behalf Of Duncan Garland >> Sent: 30 January 2010 16:45 >> To: gnome-list@xxxxxxxxx >> Subject: Remote login >> >> >> Hi, >> >> I'm trying login to a Debian Lenny box from a Window XP box. I've got >> dumb >> terminal acess working properly, but I'd like to be able to access my >> desktop as well. >> >> I've installed vnc4server on the Debian, and tightvncviewer on the >> Windows >> box. If I run vnc4server -geometry 1280x1024 -depth 24 on the Debian, >> login >> in via tightvncviewer and type gnome-session, it works after a fashion. >> >> The Desktop comes up, and I can access items such as the wastebasket. >> However, I can't access the top menu with Applications, Places and >> System on >> it. It's frozen. >> >> I'm sure this must be easy to correct, but I don't normally get >> involved in >> this sort of thing and I don't really understand the terminology. >> There are >> quite a few error messages on startup: >> >> duncan@debian1:~$ gnome-session >> SESSION_MANAGER=local/debian1:/tmp/.ICE-unix/4085 >> ** Message: another SSH agent is running at: >> /tmp/ssh-fwxDXn3909/agent.3909 >> >> ** (gnome-settings-daemon:4092): WARNING **: numlock: XkbQueryExtension >> returned an error >> >> ** (gnome-settings-daemon:4092): WARNING **: Neither XKeyboard not >> Xfree86's >> keyboard extensions are available, >> no way to support keyboard autorepeat rate settings >> >> ** (gnome-settings-daemon:4092): WARNING **: Unable to start >> a11y_keyboard >> manager: XKB functionality is disabled. >> >> ** (gnome-settings-daemon:4092): WARNING **: Failed to open file >> '/etc/gnome/config/General.ad': No such file or directory >> Window manager warning: Failed to read saved session file >> /home/duncan/.metacity/sessions/default0.ms: >> Failed to open file '/home/duncan/.metacity/sessions/default0.ms': No >> such >> file or directory >> Window manager warning: Log level 32: could not find XKB extension. >> Window manager warning: Screen 0 on display ":1.0" already has a window >> manager; try using the --replace option to replace the current window >> manager. >> Window manager warning: Failed to read saved session file >> /home/duncan/.metacity/sessions/default0.ms: >> Failed to open file '/home/duncan/.metacity/sessions/default0.ms': No >> such >> file or directory >> Window manager warning: Log level 32: could not find XKB extension. >> Window manager warning: Screen 0 on display ":1.0" already has a window >> manager; try using the --replace option to replace the current window >> manager. >> Initializing gnome-mount extension >> seahorse nautilus module initialized >> >> Does anybody know how to fix this? >> >> The other issue is that this method requires me to have already logged >> in as >> myself using the dumb terminal. It would be useful to be able to >> access the >> default login desktop screen which appear if I plug in a screen directly. >> How do I do that? >> >> Is there an idiot's guide to this sort of thing? >> >> Many thanks >> >> Duncan >> >> _______________________________________________ >> gnome-list mailing list >> gnome-list@xxxxxxxxx >> http://mail.gnome.org/mailman/listinfo/gnome-list >> >> _______________________________________________ >> gnome-list mailing list >> gnome-list@xxxxxxxxx >> http://mail.gnome.org/mailman/listinfo/gnome-list >> > -- Guy Rouillier _______________________________________________ gnome-list mailing list gnome-list@xxxxxxxxx http://mail.gnome.org/mailman/listinfo/gnome-list _______________________________________________ gnome-list mailing list gnome-list@xxxxxxxxx http://mail.gnome.org/mailman/listinfo/gnome-list
