RE: Remote login
- From: "Duncan Garland" <duncan garland ntlworld com>
- To: "David Harel" <hareldvd gmail com>, "Guy Rouillier" <guyr-ml1 burntmail com>
- Cc: gnome-list gnome org
- Subject: RE: Remote login
- Date: Sun, 14 Feb 2010 14:27:20 -0000
I'm using Debian Lenny
-----Original Message-----
From: gnome-list-bounces gnome org
[mailto:gnome-list-bounces gnome org]On Behalf Of David Harel
Sent: 14 February 2010 13:36
To: Guy Rouillier
Cc: gnome-list gnome org
Subject: Re: Remote login
Guy Rouillier wrote:
> 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.
I use either Ubuntu or Gentoo and I never had this problem, I take it
you use Redhat?
>
> Have you ever connected to a graphical UI directly on this box to
> verify that it is set up to run a GUI?
Typically I would set some kind of X11 implementation on the local
desktop machine and using ssh -X (or the equivalent) I would connect to
the remote host.
Not all the desktop of the remote machine will be available on the
desktop of the local machine. Typically I would launch specific
applications on the remote that will show the display on the local and
in that case I typically like the local desktop to rule.
>
> 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.
I was not successful with vncserver as plane user. Always as root.
>
> 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.
I believe that X11 protocol is more efficient than image transfer as VNC
does.
>
> 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.
Never tried that. Sounds interesting. Will try it next time I have to
use this kind of setting.
>
> 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 gnome org
>>> [mailto:gnome-list-bounces gnome org]On Behalf Of Duncan Garland
>>> Sent: 30 January 2010 16:45
>>> To: gnome-list gnome org
>>> 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 gnome org
>>> http://mail.gnome.org/mailman/listinfo/gnome-list
>>>
>>> _______________________________________________
>>> gnome-list mailing list
>>> gnome-list gnome org
>>> http://mail.gnome.org/mailman/listinfo/gnome-list
>>>
>>
>
>
--
Regards.
David Harel,
==================================
Home office +972 77 7657645
Cellular: +972 54 4534502
Snail Mail: Amuka
D.N Merom Hagalil
13802
Israel
Email: hareldvd ergolight-sw com
_______________________________________________
gnome-list mailing list
gnome-list gnome org
http://mail.gnome.org/mailman/listinfo/gnome-list
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]