I agree that the cleanest way is to watch the GConf key and start a process based on its changes: it's how other GConf settings work, for example all gnome-settings-daemon settings.
Perhaps it would be clearer to simply name the watcher "vino-watcher" or "vino-launcher" so that users could easily guess what the process is about? This could also be made a more generic service such as "gconf- launcher" as other apps might need the feature. Alternatively, dbus could start such a program, so replacing GConf via DBus would save us a "gconf-launcher" process. -- When remote desktop access is disabled, vino-session will still run https://bugs.launchpad.net/bugs/141160 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
