subject:"\[Desktop\-packages\] \[Bug 1610547\] Re\: Cannot connect to remote desktop, vino eating cpu and not answering"

[Desktop-packages] [Bug 1610547] Re: Cannot connect to remote desktop, vino eating cpu and not answering

2016-08-22 Thread Launchpad Bug Tracker

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   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 Desktop
Packages, which is subscribed to vino in Ubuntu.
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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1610547] Re: Cannot connect to remote desktop, vino eating cpu and not answering

2016-08-16 Thread Sebastien Bacher

Great, thanks for testing!

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vino in Ubuntu.
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 Committed

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1610547] Re: Cannot connect to remote desktop, vino eating cpu and not answering

2016-08-16 Thread Swâmi Petaramesh

Hi there,

The fix works for me and solves the issues on both machines on which I
had encountered it (an Ubuntu 16.04 and a Mint 18).

I cam confirm that uPNP now works properly, and I can connect to the
remote desktops.

Thank you very much.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vino in Ubuntu.
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 Committed

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1610547] Re: Cannot connect to remote desktop, vino eating cpu and not answering

2016-08-11 Thread Mathew Hodson

** Changed in: vino (Ubuntu Xenial)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vino in Ubuntu.
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 Committed

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1610547] Re: Cannot connect to remote desktop, vino eating cpu and not answering

2016-08-11 Thread Brian Murray

Hello Swâmi, or anyone else affected,

Accepted vino into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/vino/3.8.1-0ubuntu9.1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vino in Ubuntu.
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 Committed

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1610547] Re: Cannot connect to remote desktop, vino eating cpu and not answering

2016-08-10 Thread Launchpad Bug Tracker

This bug was fixed in the package vino - 3.8.1-0ubuntu11

---
vino (3.8.1-0ubuntu11) yakkety; urgency=medium

  * debian/control.in:
- build-depends on libgnutls28-dev rather libgnutls-dev, the binary
  has been renamed in yakkery to follow Debian

 -- Sebastien Bacher   Wed, 10 Aug 2016 15:18:41
+0200

** Changed in: vino (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vino in Ubuntu.
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

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1610547] Re: Cannot connect to remote desktop, vino eating cpu and not answering

2016-08-10 Thread Sebastien Bacher

** Summary changed:

- Cannot connect to remote desktop, vino not answering
+ Cannot connect to remote desktop, vino eating cpu and not answering

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vino in Ubuntu.
https://bugs.launchpad.net/bugs/1610547

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

Status in vino package in Ubuntu:
  In Progress

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1610547] Re: Cannot connect to remote desktop, vino eating cpu and not answering

[Desktop-packages] [Bug 1610547] Re: Cannot connect to remote desktop, vino eating cpu and not answering

[Desktop-packages] [Bug 1610547] Re: Cannot connect to remote desktop, vino eating cpu and not answering

[Desktop-packages] [Bug 1610547] Re: Cannot connect to remote desktop, vino eating cpu and not answering

[Desktop-packages] [Bug 1610547] Re: Cannot connect to remote desktop, vino eating cpu and not answering

[Desktop-packages] [Bug 1610547] Re: Cannot connect to remote desktop, vino eating cpu and not answering

[Desktop-packages] [Bug 1610547] Re: Cannot connect to remote desktop, vino eating cpu and not answering

7 matches

Site Navigation

Mail list logo

Footer information