group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1610547@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package vino - 3.8.1-0ubuntu9.1

---------------
vino (3.8.1-0ubuntu9.1) xenial; urgency=medium

  * debian/patches/05_use-system-miniupnpc.patch:
    - use correct arguments for upnp calls, fixes vino server eating
      cpu and not responding once the corresponding option is enabled
      (lp: #1610547)

 -- Sebastien Bacher <seb128@xxxxxxxxxx>  Wed, 10 Aug 2016 11:03:23
+0200

** Changed in: vino (Ubuntu Xenial)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1610547

Title:
  Cannot connect to remote desktop, vino eating cpu and not answering

Status in vino package in Ubuntu:
  Fix Released
Status in vino source package in Xenial:
  Fix Released

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
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vino/+bug/1610547/+subscriptions