On Wed, Mar 11, 2009 at 04:40, Chris Coulson
<email address hidden>wrote:
> Yes, if you manually start vino-server then enable it in Remote Desktop
> Preferences afterwards, this sets the AutostartCondition to true and
> causes gnome-session to start another instance. This instance
> immediately exits though because there is already one running, which
> triggers this endless cycle of restarts you're seeing.
Not quite what happened. I had started vino-server manually, then quit it.
Then, separately, I re-enabled the automatic support that I had initially
disabled (via gconftool).
So: when starting vino manually, it works fine; when started through Remote
Desktop/gconf, it works but uses all the CPU.
On Wed, Mar 11, 2009 at 04:40, Chris Coulson
<email address hidden>wrote:
> Yes, if you manually start vino-server then enable it in Remote Desktop
> Preferences afterwards, this sets the AutostartCondition to true and
> causes gnome-session to start another instance. This instance
> immediately exits though because there is already one running, which
> triggers this endless cycle of restarts you're seeing.
Not quite what happened. I had started vino-server manually, then quit it.
Then, separately, I re-enabled the automatic support that I had initially
disabled (via gconftool).
So: when starting vino manually, it works fine; when started through Remote
Desktop/gconf, it works but uses all the CPU.