© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
demo site
(Get the code!)
I have the same problem on a HTPC running Jaunty. I don't need to VNC into the machine for this to happen. A day or two of uptime will eventually make the vino-server process start eating CPU resources up all by itself.
A quick and dirty way to fix this is to just kill -9 the process. I keep screen running on the machine with top running in a window. I'll ssh in, screen -x, and just hit "k" within top, specify the PID of the vino-server process, and send the 9 signal to kill it. I haven't figured out why, but the process ends up restarting within a second of killing it. However, it isn't eating CPU resources when it restarts.