After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 668187 - Server hangs when using alternative port and the default port is taken by libvirt
Server hangs when using alternative port and the default port is taken by lib...
Status: RESOLVED FIXED
Product: vino
Classification: Applications
Component: Server
3.2.x
Other Linux
: Normal normal
: ---
Assigned To: Vino Maintainer(s)
Vino Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2012-01-18 15:33 UTC by Kamil Páral
Modified: 2013-03-13 22:48 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Kamil Páral 2012-01-18 15:33:21 UTC
I use libvirt to manage my virtual machines. By default it uses port 5900 to display VM's graphics [1]. Sometimes I start vino-server only after starting some VMs. Then obviously vino-server fails to bind to port 5900. Because of that I have used dconf-editor to set

/desktop/gnome/remote-access/alternative-port 8900
/desktop/gnome/remote-access/use-alternative-port true

Now vino-server correctly binds to port 8900. However, here's the quirk:

1. If I start vino-server prior to any VM, everything works. I can connect using VNC viewer (to port 8900). Even when I start some VM afterwards (and it binds port 5900), I can still connect to vino-server.
2. If I start some VM first (which binds port 5900) and vino-server second (which binds port 8900), I can't connect to the vino-server. It is completely stuck and it is not possible to connect to it. There is something very fishy.

This issue is very inconvenient, because I often encounter this use case:
start vino-server -> start VM -> connect to vino-server (OK) -> work, work, work -> vino-server crashes -> vino-server is automatically restarted -> I can no longer connect to vino-server


Fedora 16 x86_64

[1] https://bugzilla.redhat.com/show_bug.cgi?id=782814
Comment 1 Jonathan Kamens 2012-09-12 19:04:01 UTC
I just posted a patch in https://bugzilla.redhat.com/show_bug.cgi?id=856772 .
Comment 2 Jonathan Kamens 2013-03-12 23:42:26 UTC
Hello? Does anybody care about this bug? Is anybody maintaining Vino? I gave you a patch to fix this bug SIX MONTHS AGO? Hello?
Comment 3 David King 2013-03-13 22:48:49 UTC
I pushed the patch to master as commit f15611181dd2db61422e411e26ec52a91ff10515, thanks!