I experienced the same problem as many have already mentioned - namely gnome-settings-daemon fails when accessing the GNOME GUI via vnc4server.
After a little experimentation and research, I discovered what I think is a solution (or at least an easy workaround).
What works for me is to add the argument "+extension XInputExtension" to the vnc4server invocation. A most basic example would be:
vnc4server :1 +extension XInputExtension
In other words, it seems as though the XInputExtension *is* compiled into vnc4server (contrary to what some indicated), but is not activated by default. Therefore, this explicit activation of the extension resolves the issue.
So far so good, now can anyone else confirm that this works for them too?
I experienced the same problem as many have already mentioned - namely gnome-settings- daemon fails when accessing the GNOME GUI via vnc4server.
After a little experimentation and research, I discovered what I think is a solution (or at least an easy workaround).
What works for me is to add the argument "+extension XInputExtension" to the vnc4server invocation. A most basic example would be:
vnc4server :1 +extension XInputExtension
In other words, it seems as though the XInputExtension *is* compiled into vnc4server (contrary to what some indicated), but is not activated by default. Therefore, this explicit activation of the extension resolves the issue.
So far so good, now can anyone else confirm that this works for them too?