Hi,
I've got a problem while using vnc to view a fedora 11 hosted gnome desktop, the gnome theme isn't what I chose but nodoka. If I open the appearance dialogbox from system->preference, the gnome theme instantly changed to what I selected no matter which tab of this dialogbox activated. And when I close the dialogbox, the theme changed back to nodoka. If I did this a second time, a crash about notification-daemon will happen. I've attached the crash report. There is no problem while loging on locally.
The vnc server runs on fedora 11 with tigervnc-server-0.0.90-0.7.20090427svn3789.fc11.i586, kernel 2.6.29.3-140.fc11.i586. The vnc client runs on fedora 10 with vnc vnc-4.1.3-1.fc10.i386.
Anyone has the same problem?
On Thu, 2009-05-14 at 16:44 +0800, aaron lwe wrote:
Hi,
I've got a problem while using vnc to view a fedora 11 hosted gnome desktop, the gnome theme isn't what I chose but nodoka. If I open the appearance dialogbox from system->preference, the gnome theme instantly changed to what I selected no matter which tab of this dialogbox activated. And when I close the dialogbox, the theme changed back to nodoka. If I did this a second time, a crash about notification-daemon will happen. I've attached the crash report. There is no problem while loging on locally.
The vnc server runs on fedora 11 with tigervnc-server-0.0.90-0.7.20090427svn3789.fc11.i586, kernel 2.6.29.3-140.fc11.i586. The vnc client runs on fedora 10 with vnc vnc-4.1.3-1.fc10.i386.
Anyone has the same problem?
Out of curiousity, are you seeing Bug#497592 (vncserver desktop error message of "could not acquire name on session bus")?
Thanks, James
aaron lwe wrote:
I've got a problem while using vnc to view a fedora 11 hosted gnome desktop, the gnome theme isn't what I chose but nodoka. If I open the appearance dialogbox from system->preference, the gnome theme instantly changed to what I selected no matter which tab of this dialogbox activated. And when I close the dialogbox, the theme changed back to nodoka. If I did this a second time, a crash about notification-daemon will happen. I've attached the crash report. There is no problem while loging on locally.
Looks like gnome-settings-daemon is not running in your VNC session.
Kevin Kofler
On Wed, May 20, 2009 at 4:24 AM, Kevin Kofler kevin.kofler@chello.at 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.)
-
aaron lwe -
James Laska -
Kevin Kofler