freenx-team team mailing list archive
-
freenx-team team
-
Mailing list archive
-
Message #00360
[Bug 399758] Re: Free-nx, gnome-settings-daemon and Jaunty not working correctly
*** This bug is a duplicate of bug 409621 ***
https://bugs.launchpad.net/bugs/409621
"downgrading libxklavier to version 3.9-0ubuntu1 fixes the crash.. i don't think it's a freenx bug or a gnome-setting-daemon bug."
spiorf, Thank you! It works for me!
--
Free-nx, gnome-settings-daemon and Jaunty not working correctly
https://bugs.launchpad.net/bugs/399758
You received this bug notification because you are a member of FreeNX
Team, which is the registrant for FreeNX Server.
Status in FreeNX open source NX Server: New
Bug description:
A nxclient session to a Jaunty server does not display themes correctly. The gnome-settings-daemon does not start correctly. When any program is started from the command line the following error is reported:
Xlib: extension "Generic Event Extension" missing on display ":1000.0".
Xlib: extension "Generic Event Extension" missing on display ":1000.0".
Xlib: extension "Generic Event Extension" missing on display ":1000.0".
Xlib: extension "Generic Event Extension" missing on display ":1000.0".
Xlib: extension "Generic Event Extension" missing on display ":1000.0".
Furthermore entering gnome settings daemon from the command line throws this error:
** (gnome-settings-daemon:21810): WARNING **: Unable to start xrandr manager: unhandled X error while getting the range of screen sizes
The program 'gnome-settings-daemon' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadClass, invalid event class'.
(Details: serial 155 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.)
Disabling the xrandr plugin does not alleviate the error.
References