RE: Remote login

["Duncan Garland" <duncan garland ntlworld com>]

Hi,

Did anybody ever solve this? I know a few people seemed to be having similar
problems.

I've just experimented a bit more and established that it works properly if
I plug a keyboard, mouse and screen into the Debian box during boot. I can
then remove the screen from the Debian box, plug it in to my PC (running XP
Pro) and use Tight VNC to start a Gnome session. The menu is not frozen.

I've got the Debian box configured so that it will boot without a keyboard,
screen, or mouse and if I log in with a non-graphics terminal emulator such
as putty then it's fine. The only problem is with gnome via VNC. It
obviously needs something extra.

The terminal output when it gnome session starts successfully is:

************************************************************

gnome-session
SESSION_MANAGER=local/debian1:/tmp/.ICE-unix/3501

** (gnome-settings-daemon:3509): WARNING **: numlock: XkbQueryExtension
returned an error

** (gnome-settings-daemon:3509): WARNING **: Neither XKeyboard not Xfree86's
keyboard extensions are available,
no way to support keyboard autorepeat rate settings

** (gnome-settings-daemon:3509): WARNING **: Unable to start a11y_keyboard
manager: XKB functionality is disabled.
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
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.

** (gnome-panel:3522): WARNING **: Failed to authenticate with GDM
The program 'gnome-settings-daemon' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 2613 error_code 3 request_code 20 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.)

** (gnome-settings-daemon:3599): WARNING **: numlock: XkbQueryExtension
returned an error

** (gnome-settings-daemon:3599): WARNING **: Neither XKeyboard not Xfree86's
keyboard extensions are available,
no way to support keyboard autorepeat rate settings

** (gnome-settings-daemon:3599): WARNING **: Unable to start a11y_keyboard
manager: XKB functionality is disabled.

** (gnome-screensaver:3619): WARNING **: screensaver already running in this
session
warning: could not initiate dbus
current dist not found in meta-release file
The program 'gnome-settings-daemon' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 2585 error_code 3 request_code 20 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.)

** (gnome-settings-daemon:3635): WARNING **: numlock: XkbQueryExtension
returned an error

** (gnome-settings-daemon:3635): WARNING **: Neither XKeyboard not Xfree86's
keyboard extensions are available,
no way to support keyboard autorepeat rate settings

** (gnome-settings-daemon:3635): WARNING **: Unable to start a11y_keyboard
manager: XKB functionality is disabled.

** (gnome-screensaver:3645): WARNING **: screensaver already running in this
session
could not send the dbus Inhibit signal: org.freedesktop.DBus.Error.NoReply:
Did not receive a reply. Possible causes include: the remote application did
not send a reply, the message bus security policy blocked the reply, the
reply timeout expired, or the network connection was broken.
The program 'gnome-settings-daemon' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 2602 error_code 3 request_code 20 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.)

** (gnome-settings-daemon:3660): WARNING **: numlock: XkbQueryExtension
returned an error

** (gnome-settings-daemon:3660): WARNING **: Neither XKeyboard not Xfree86's
keyboard extensions are available,
no way to support keyboard autorepeat rate settings

** (gnome-settings-daemon:3660): WARNING **: Unable to start a11y_keyboard
manager: XKB functionality is disabled.

** (gnome-screensaver:3678): WARNING **: screensaver already running in this
session

** (gnome-panel:3522): WARNING **: Failed to authenticate with GDM
The program 'gnome-settings-daemon' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 2603 error_code 3 request_code 20 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.)

** (gnome-settings-daemon:4153): WARNING **: numlock: XkbQueryExtension
returned an error

** (gnome-settings-daemon:4153): WARNING **: Neither XKeyboard not Xfree86's
keyboard extensions are available,
no way to support keyboard autorepeat rate settings

** (gnome-settings-daemon:4153): WARNING **: Unable to start a11y_keyboard
manager: XKB functionality is disabled.

** (gnome-screensaver:4163): WARNING **: screensaver already running in this
session
The program 'gnome-settings-daemon' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 2583 error_code 3 request_code 20 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.)

** (gnome-settings-daemon:4172): WARNING **: numlock: XkbQueryExtension
returned an error

** (gnome-settings-daemon:4172): WARNING **: Neither XKeyboard not Xfree86's
keyboard extensions are available,
no way to support keyboard autorepeat rate settings

** (gnome-settings-daemon:4172): WARNING **: Unable to start a11y_keyboard
manager: XKB functionality is disabled.

** (gnome-screensaver:4182): WARNING **: screensaver already running in this
session

************************************************************************

and everything seems to work.

Without the keyboard:

************************************************************************

duncan debian1:~$ gnome-session
SESSION_MANAGER=local/debian1:/tmp/.ICE-unix/3394

** (gnome-settings-daemon:3401): WARNING **: numlock: XkbQueryExtension
returned an error

** (gnome-settings-daemon:3401): WARNING **: Neither XKeyboard not Xfree86's
keyboard extensions are available,
no way to support keyboard autorepeat rate settings

** (gnome-settings-daemon:3401): WARNING **: Unable to start a11y_keyboard
manager: XKB functionality is disabled.
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

************************************************************************

and the application menu is frozen.

Does this mean anything to anybody? It's all Greek to me.

Thanks in advance.

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