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 598796 - Vino doesn't handle multiple xservers properly.
Vino doesn't handle multiple xservers properly.
Status: RESOLVED WONTFIX
Product: vino
Classification: Applications
Component: Server
2.26.x
Other Linux
: Normal normal
: ---
Assigned To: Vino Maintainer(s)
Vino Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2009-10-17 21:01 UTC by Paul Klapperich
Modified: 2020-11-12 12:24 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Paul Klapperich 2009-10-17 21:01:21 UTC
I filed this with Ubuntu here: https://bugs.launchpad.net/ubuntu/+source/vino/+bug/394318
And was told to refile upstream. I have not tried onn Gnome 2.28.

Upgraded from Ubuntu 8.10 to Ubunttu 9.04, where it used to work fine. Running dual monitor on separate xservers. When I connect to port 5901, the connection stalls on the first try and is refused on successive attempts. Connections to port 5900 show the contents of screen ':0.0' but controls EITHER ':0.0' or ':0.1', depending on location of cursor local cursor. (When cursor on display :0.0, connected client controls display :0.0. When cursor on display :0.1, connected client controls :0.1, though client ALWAYS views :0.0's contents.)

Expected behavior (expressed in Gnome 2.24):
Connecting to 5900 shows and controls :0.0; connecting to 5901 shows and controls :0.1. This should occur regardless of the location of the local machine cursor (moving the local mouse shouldn't change where a connected client's mouse clicks are registered. Additionally, there should never be a case where connected clients see the contents of one display but controls another.

vino 2.26.1-0ubuntu1
nvidia-180-kernel-source 180.44-0ubuntu1
display 0.0 is vga, 0.1 is svideo
uname: 2.6.28-13-generic i686

I know some bugs in vino can be nVidia binary driver specific. I have not tried using 2 VGA monitors and an OSS driver as I do not have a second display handy and S-Video only works in the binary driver.
Comment 1 G K 2011-08-06 01:13:24 UTC
Continues with gnome-3

Another related downstream bug
  Vino with two X-servers may cause X to crash while competing for the mouse
  https://bugzilla.redhat.com/show_bug.cgi?id=705643

$ rpm -qa | egrep -i "vino|kernel-2|gnome-shell|mutter"
gnome-shell-3.0.2-4.fc15.x86_64
vino-3.0.2-2.fc15.x86_64
kernel-2.6.40-4.fc15.x86_64
mutter-3.0.2.1-1.fc15.x86_64

$ uname -a
Linux sirius.localdomain 2.6.40-4.fc15.x86_64 #1 SMP Fri Jul 29 18:46:53 UTC
2011 x86_64 x86_64 x86_64 GNU/Linux

$ lspci | egrep -i "Radeon HD"
01:00.0 VGA compatible controller: ATI Technologies Inc Mobility Radeon HD 3400
Series
01:00.1 Audio device: ATI Technologies Inc RV620 Audio device [Radeon HD 34xx
Series]
Comment 2 André Klapper 2020-11-12 12:24:27 UTC
Vino is not under active development anymore and unmaintained.

Please use gnome-remote-desktop instead.

Closing this report as WONTFIX to reflect reality.