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
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
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
** 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
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
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
** 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.
7 matches
Mail list logo
