vino-server using a lot of CPU and very sluggish after upgrade to 14.04

[Romano Giannetti]

The title says its all.

 PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
 8150 romano 20 0 64268 8800 5948 R 57.8 0.4 126:57.46 vino-se+
 8883 romano 20 0 632412 34788 6156 S 31.8 1.7 195:15.26 dropbox
 1420 root 20 0 9964 1940 940 S 8.5 0.1 36:28.15 cups-br+

It was working nicely in 13.10; now it feels very sluggish and the CPU usage is very high all the time.
Connecting with TigerVNC from a Windows machine, but a couple of fast test showed the same problem with other clients.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: vino 3.8.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic i686
ApportVersion: 2.14.1-0ubuntu3
Architecture: i386
CurrentDesktop: XFCE
Date: Wed Apr 23 09:17:05 2014
InstallationDate: Installed on 2013-04-30 (358 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
SourcePackage: vino
UpgradeStatus: Upgraded to trusty on 2014-04-21 (1 days ago)

[Sebastien Bacher (seb128)]

Thank you for your bug report. It could be because encryption is used by default now

Is it better if you turn encryption off using the command
"gsettings set org.gnome.Vino require-encryption false"

[Romano Giannetti (romano-giannetti)]

Encryption is already off due to https://bugs.launchpad.net/ubuntu/+source/vino/+bug/1281250 - otherwise vino is practically impossible to use (no clients apart from vinagre use the encryption that vino offer).

[Sebastien Bacher (seb128)]

k, not sure about the issue then, it might be worth reporting to upstream though

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[arwi (ar-wi)]

Had the same error on my Thinkpad with trusty on it. CPU usage was up to 100% when running vino-server. I checked strace and saw a lot of event polling.
Turned off my wifi connection completely by the switch on the right side of the device. Plugged in the ethernet cable. Restarted vino-server... and, well, vino-server runs smootly as it should.