I noticed that I forgot to attach the server output described above. Here it is.
** Description changed: Binary package hint: vino On lucid, when you set the /desktop/gnome/remote_access/network_interfaces gconf key to "lo", Vino - will accept VNC connection only for the first desktop session. If you + will accept VNC connections only for the first desktop session. If you switch user, opening a new session as a different one, it is impossible to connect to that session. It works as expected when the network_interfaces gconf key is not set. = Step to reproduce = 1. On the target machine, open a session as one user, then switch to a second user. - 2. From another machine, witness that you can cannot to both session by - VNC: + 2. From another machine, witness that you can cannot connect to both + session by VNC: - $ vncviewer target:0 # VNC client screen remain black (session is locked), but connection is possible - $ vncviewer target:1 # Connection ok + $ vncviewer target:0 # VNC client screen remain black (session is locked), but connection is possible + $ vncviewer target:1 # Connection ok 3. On the target machine, set the - /desktop/gnome/remote_access/network_interface gconf to default to "lo". - I think you need to reboot the machine at that point, as it seems that - Vino continue to accept connection on non-lo interfaces (but that is not - german to this bug). + /desktop/gnome/remote_access/network_interface gconf key to default to + "lo". I think you need to reboot the machine at that point, as it seems + that Vino continue to accept connection on non-lo interfaces (but that + is not german to this bug). 4. Try to connect remotely using ssh tunneling: - $ vncviewer -via target localhost:0 # VNC client screen remain black (session is locked), but connection otherwise work - $ vncviewer -via target localhost:1 # Connection is refused + $ vncviewer -via target localhost:0 # VNC client screen remain black (session is locked), but connection otherwise work + $ vncviewer -via target localhost:1 # Connection is refused = Expected behavior = Vino should allow incoming connection to the current foreground session, whether directly or through an ssh tunnel when network_interfaces is set to "lo". - vino package is version 2.28.2-0ubuntu2. ** Attachment added: "vino-server.output" https://bugs.launchpad.net/ubuntu/+source/vino/+bug/707705/+attachment/1912026/+files/vino-server.output -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/707705 Title: Vino not accepting incoming connection to more than a single desktop session when the "network_interfaces=lo" option is set -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
