On Wed, May 20, 2009 at 4:24 AM, Kevin Kofler <kevin.kofler@xxxxxxxxx> wrote: > > Looks like gnome-settings-daemon is not running in your VNC session. > > Kevin Kofler > Thanks Kevin, I think you are right. I manually started gnome-settings-daemon in a vnc session like this: /usr/libexec/gnome-settings-daemon --gconf-prefix=/apps/gdm/simple-greeter/settings-manager-plugins Everything works fine. I don't know what the param means, I just did a ps ax|grep gnome-settings-daemon and it showed this. But if I started it like this: /usr/libexec/gnome-settings-daemon The theme will initially change to what I've chosen, with some warnings: ** (gnome-settings-daemon:2745): WARNING **: XKB extension not available ** (gnome-settings-daemon:2745): WARNING **: Neither XKeyboard not Xfree86's keyboard extensions are available, no way to support keyboard autorepeat rate settings ** (gnome-settings-daemon:2745): WARNING **: Connection failed Then switched back to nodoka with an error message after a little while: 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 557 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.) -- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
