[FreeNX-kNX] Debian squeeze dbus issues
Bob Tracy
rct at gherkin.frus.com
Thu May 7 19:23:06 UTC 2009
I'm currently running FreeNX server 0.7.3 on an Alpha with the Debian
"squeeze" distro. Things had been working fine until recent Debian
updates were applied. Now when I access the machine with a FreeNX
session, "gnome-settings-daemon" refuses to start because of dbus
timeouts. (Session log attached.)
Here's how I start a Gnome session in node.conf:
COMMAND_START_GNOME="/usr/bin/dbus-launch --exit-with-session /usr/bin/gnome-session"
Logging in on the console still seems to work ok. The only immediately
noticeable difference is yet another layer of indirection as far as how
the session is started. Based on "ps" output, the console session seems
to be started with ssh-agent thusly:
ssh-agent /usr/bin/dbus-launch --exit-with-session x-session-manager
where "x-session-manager" is a symbolic link to
"/etc/alternatives/x-session-manager" which in turn is a symbolic link
to "/usr/bin/gnome-session".
Some of the "recent Debian updates" I mentioned above were updates to
various Gnome apps and libraries, so that may have something to do with
the problems I'm seeing. Any thoughts as to whether a rebuild of the
FreeNX server binaries might be required?
--
------------------------------------------------------------------------
Bob Tracy | "Talk is cheap because supply exceeds demand."
rct at frus.com | -- Bill Kennedy
------------------------------------------------------------------------
-------------- next part --------------
NXAGENT - Version 3.3.0
Copyright (C) 2001, 2007 NoMachine.
See http://www.nomachine.com/ for more information.
Info: Agent running with pid '4367'.
Session: Starting session at 'Thu May 7 11:41:21 2009'.
Info: Proxy running in server mode with pid '4367'.
Info: Waiting for connection from '127.0.0.1' on port '5000'.
Info: Accepted connection from '127.0.0.1'.
Warning: Connected to remote version 3.0.0 with local version 3.3.0.
Info: Connection with remote proxy completed.
Info: Using ADSL link parameters 512/24/1/0.
Info: Using agent parameters 5000/10/50/0/0.
Info: Using cache parameters 4/4096KB/16384KB/16384KB.
Info: Using pack method 'adaptive-7' with session 'unix-gnome'.
Info: Using ZLIB data compression 1/1/32.
Info: Using ZLIB stream compression 4/4.
Info: Using cache file '/home/rct/.nx/cache-unix-gnome/C-39DB6BF8162ACD5CFF99DBA283EE1D82'.
Info: Listening to X11 connections on display ':1000'.
Info: Established X client connection.
Info: Using shared memory parameters 1/1/1/4096K.
Info: Using alpha channel in render extension.
Info: Not using local device configuration changes.
Session: Session started at 'Thu May 7 11:41:33 2009'.
Info: Screen [0] resized to geometry [1024x732].
Warning: No data received from remote proxy within 30 seconds.
Session: Terminating session at 'Thu May 7 12:37:33 2009'.
Info: Watchdog running with pid '6642'.
Info: Waiting the watchdog process to complete.
Session: Session terminated at 'Thu May 7 12:37:44 2009'.
ial 144 error_code 133 request_code 131 minor_code 6)
(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.)
[1241714496,000,xklavier.c:xkl_engine_start_listen/] The backend does not require manual layout management - but it is provided by the applicationI: caps.c: Limited capabilities successfully to CAP_SYS_NICE.
I: caps.c: Dropping root privileges.
I: caps.c: Limited capabilities successfully to CAP_SYS_NICE.
N: main.c: Called SUID root and real-time and/or high-priority scheduling was requested in the configuration. However, we lack the necessary privileges:
N: main.c: We are not in group 'pulse-rt', PolicyKit refuse to grant us the requested privileges and we have no increase RLIMIT_NICE/RLIMIT_RTPRIO resource limits.
N: main.c: For enabling real-time/high-priority scheduling please acquire the appropriate PolicyKit privileges, or become a member of 'pulse-rt', or increase the RLIMIT_NICE/RLIMIT_RTPRIO resource limits for this user.
The program 'gnome-settings-daemon' received an X Window System error.
This probably reflects a bug in the program.
The error was 'XI_BadClass (invalid Class parameter)'.
(Details: serial 140 error_code 133 request_code 131 minor_code 6)
(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.)
[1241714503,000,xklavier.c:xkl_engine_start_listen/] The backend does not require manual layout management - but it is provided by the application
** (gnome-power-manager:4414): WARNING **: DBUS error: Could not get owner of name 'org.gnome.ScreenSaver': no such name
** (gnome-power-manager:4414): DEBUG: proxy is NULL, maybe the daemon responsible for org.gnome.ScreenSaver is not running?
** (gnome-power-manager:4414): WARNING **: This machine is not identified as a laptop.system.formfactor is unknown.
** (gnome-power-manager:4414): WARNING **: This machine is not identified as a laptop.system.formfactor is unknown.
** (gnome-power-manager:4414): DEBUG: This machine is not identified as a laptop.system.formfactor is unknown.
** (gnome-power-manager:4414): DEBUG: We are not a laptop, so not even trying
The program 'gnome-settings-daemon' received an X Window System error.
This probably reflects a bug in the program.
The error was 'XI_BadClass (invalid Class parameter)'.
(Details: serial 140 error_code 133 request_code 131 minor_code 6)
(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.)
[1241714512,000,xklavier.c:xkl_engine_start_listen/] The backend does not require manual layout management - but it is provided by the applicationInitializing gnome-mount extension
** (gnome-panel:4405): WARNING **: Failed to authenticate with GDM
(gnome-panel:4405): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -15 and height 24
The program 'gnome-settings-daemon' received an X Window System error.
This probably reflects a bug in the program.
The error was 'XI_BadClass (invalid Class parameter)'.
(Details: serial 140 error_code 133 request_code 131 minor_code 6)
(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.)
[1241714530,000,xklavier.c:xkl_engine_start_listen/] The backend does not require manual layout management - but it is provided by the applicationThe program 'gnome-settings-daemon' received an X Window System error.
This probably reflects a bug in the program.
The error was 'XI_BadClass (invalid Class parameter)'.
(Details: serial 140 error_code 133 request_code 131 minor_code 6)
(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.)
[1241714538,000,xklavier.c:xkl_engine_start_listen/] The backend does not require manual layout management - but it is provided by the applicationThe program 'gnome-settings-daemon' received an X Window System error.
This probably reflects a bug in the program.
The error was 'XI_BadClass (invalid Class parameter)'.
(Details: serial 140 error_code 133 request_code 131 minor_code 6)
(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.)
[1241714545,000,xklavier.c:xkl_engine_start_listen/] The backend does not require manual layout management - but it is provided by the applicationThe program 'gnome-settings-daemon' received an X Window System error.
This probably reflects a bug in the program.
The error was 'XI_BadClass (invalid Class parameter)'.
(Details: serial 140 error_code 133 request_code 131 minor_code 6)
(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.)
[1241714552,000,xklavier.c:xkl_engine_start_listen/] The backend does not require manual layout management - but it is provided by the application
(gnome-panel:4405): Gdk-WARNING **: gdk_xsettings_watch_cb(): Couldn't find window to unwatch
The program 'gnome-settings-daemon' received an X Window System error.
This probably reflects a bug in the program.
The error was 'XI_BadClass (invalid Class parameter)'.
(Details: serial 140 error_code 133 request_code 131 minor_code 6)
(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.)
[1241714560,000,xklavier.c:xkl_engine_start_listen/] The backend does not require manual layout management - but it is provided by the application1241714561.334892 Session manager: disconnected...
07/05/2009 11:42:42 Autoprobing TCP port
07/05/2009 11:42:42 Autoprobing selected port 5900
07/05/2009 11:42:42 Advertising security type: 'TLS' (18)
07/05/2009 11:42:42 Advertising authentication type: 'No Authentication' (1)
07/05/2009 11:42:42 Advertising security type: 'No Authentication' (1)
** (gnome-settings-daemon:4524): WARNING **: Failed to acquire org.gnome.SettingsDaemon
** (gnome-settings-daemon:4524): WARNING **: Could not acquire name
The program 'gnome-settings-daemon' received an X Window System error.
This probably reflects a bug in the program.
The error was 'XI_BadClass (invalid Class parameter)'.
(Details: serial 140 error_code 133 request_code 131 minor_code 6)
(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.)
[1241714566,000,xklavier.c:xkl_engine_start_listen/] The backend does not require manual layout management - but it is provided by the application1241714566.797750 Session manager: disconnected...
The program 'gnome-settings-daemon' received an X Window System error.
This probably reflects a bug in the program.
The error was 'XI_BadClass (invalid Class parameter)'.
(Details: serial 140 error_code 133 request_code 131 minor_code 6)
(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.)
[1241714572,000,xklavier.c:xkl_engine_start_listen/] The backend does not require manual layout management - but it is provided by the application
** (gnome-panel:4405): WARNING **: Failed to authenticate with GDM
** (gnome-panel:4405): WARNING **: Failed to authenticate with GDM
(...)
More information about the FreeNX-kNX
mailing list