Ok, it seems that the starting method of vino-server is changed with Jaunty, or something similar. With the new method, the vino-server process (without any arguments) is always started by Startup Applications, even if the option in System->Preferences->Remote Desktop is disabled; enabling this just instructs the existing vino-server to listen to the 5900 port and accept connections. With the old method, I think, System->Preferences->Remote Desktop used to enable its own vino-server process (the process with arguments). Because of a bug in the upgrade procedure, for the old users, both of the processes are there, causing the problem with the cpu.
Comparing a new user created after the upgrade to Jaunty (not presenting any bug) and the old one, created before the upgrade (with the bug), I found a feasable workaround. To adopt the new method: 1) delete the .desktop file which refers to vino-server in the folder ~/.config/gnome-session/saved-session; and 2) enable "Remote Desktop" in Startup Applications; 3) restart the session (logout & login). -- vino-server eats a lot of cpu time with d-bus requests https://bugs.launchpad.net/bugs/371356 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
