Cannot connect to remote desktop, vino eating cpu and not answering
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
vino (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Xenial |
Fix Released
|
High
|
Unassigned |
Bug Description
* Impact
vino eats cpu and doesn't work correctly when the upnp option is enabled
* Test case
- log into an unity session
- open vino settings
- check the upnp box
-> the process shouldn't start using cpu, if you have a router with upnp autoconfiguration it should get its table updated
* Regression potential
the change is limited to the upnp configuration option
-------
Seen this on 2 machines both running vino 3.8.1-0ubuntu9, exact same symptoms :
- One machine running Ubuntu 16.04.1 xenial LTS (from which I report this)
- One machine running Mint 18 Sarah (based on Ubuntu 16.04, showing same behaviour)
On both machines, vino does not work or works very erratically :
- The Vino icon doesn't appear in the task bar at all, or eventually appears after 20 minutes or so...
- uPNP port opening is *NOT* registered by router
- Port 5900 seems open
- It is not possible to remotely connect to the machine (server not responding)
- It *may* (or may not) start working after vino has been running for an extended period of time...
- If it eventually starts working, then, well, it works, but that seldom happens.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: vino 3.8.1-0ubuntu9
ProcVersionSign
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Aug 6 17:04:17 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-07-22 (15 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: vino
UpgradeStatus: No upgrade log present (probably fresh install)
description: | updated |
Changed in vino (Ubuntu): | |
importance: | Undecided → High |
status: | New → In Progress |
summary: |
- Cannot connect to remote desktop, vino not answering + Cannot connect to remote desktop, vino eating cpu and not answering |
Changed in vino (Ubuntu Xenial): | |
importance: | Undecided → High |
After some more analysis, I could confirm that the issue relates to uPNP. It never succeeds setting uPNP on my router/DSL box (an Orange "LiveBox"), but if I uncheck the uPNP checkbox, then vino opens up immediately and works... on the LAN.
As a side note, the uPNP issue does not relate to the router, as Skype or my son's games have no problem opening ports using uPNP on the same router box...