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 570178 - Multiple X Screens and VNC Problem
Multiple X Screens and VNC Problem
Status: RESOLVED WONTFIX
Product: vino
Classification: Applications
Component: Server
2.24.x
Other All
: Normal normal
: ---
Assigned To: Vino Maintainer(s)
Vino Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2009-02-02 06:50 UTC by Jason Bell
Modified: 2020-11-12 12:24 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description Jason Bell 2009-02-02 06:50:44 UTC
Please describe the problem:
I have a machine (details to follow) that has 2 x dual head video cards.  I recently upgraded the machine to fedora 10 in which I can no longer remote desktop (using vnc) properly to be able to see and control all X Screens (4 in total).

I am currently trying to use "Remote Desktop (Gnome)" [vino] in which appears to work fine, but only allows me to control the primary display screen.  I have also tried x0vncserver and x11vnc with similar results.

I am using 2 nVidia Quadro FX1700 video cards, using nvidia-setting to configure the 4 displays using xinerama.  Note: if I use Separate Screens, I can only control the first screen, if I use Twinview, I am able to control the first 2 screens, but not the other 2.

This issue also occurs for a single dual screen, if using separate X Screens.

Also note that I need to be able to connect to this "desktop" via a windows machine, using something like realvnc or ultravnc (I have tried both).

I have also tried to follow bug (http://bugzilla.gnome.org/show_bug.cgi?id=346258) and try suggested fixes with no success.


Version-Release number of selected component (if applicable): Fedora 10 (running latest updates, as of (2-2-2009)


Steps to reproduce:
1.	Updated install of Fedora 10 (Cannot confirm this bug is present in other distro's of Linux)

2.    Configure multiple screens (using nvidia-settings [nvidia drivers from RPM Fusion] with xinerama support using separate X Screens)	

3.	Configure Remote desktop using the following settings:

Sharing

    *      Allow other users to view your desktop (enabled)
    *      Allow other users to control you desktop (enabled) 

Security

    *      Ask you for confirmation (disabled) 
    *      Required the user to enter a password (password configured)  



Actual results:
Can only control Primary Screen, i.e., no mouse control on X screens other than primary.

Expected results:
Full control of all X Screens

Does this happen every time?
Yes

Other information:
Details on the hardware tested are as follows:

Dell Precision T3400
2.4GHz quad-core Core 2 (Q6600)
Dual 512MB PCIe x16 nVidia Quadro FX1700 video cards
2GB of Memory
320GB SATA HDD (3.0Gb/s, 7.2k RPM)
Gigabit NIC 
16X max DVD+/-RW Drive
Running Fedora 10 (x86_64 Version)

current xorg.conf

cat /etc/X11/xorg.conf
# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings:  version 1.0  (buildmeister@builder62)  Sat Jan 24 18:47:49 PST 2009

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 0 0
    Screen      1  "Screen1" 2304 0
    Screen      2  "Screen2" 1280 0
    Screen      3  "Screen3" 3328 0
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
EndSection

Section "Files"
    FontPath        "/usr/share/fonts/default/Type1"
EndSection

Section "Module"
    Load           "dbe"
    Load           "extmod"
    Load           "type1"
    Load           "freetype"
    Load           "glx"
EndSection

Section "ServerFlags"
    Option         "Xinerama" "1"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/input/mice"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
    Identifier     "Keyboard0"
    Driver         "kbd"
    Option         "XkbLayout" "us"
    Option         "XkbModel" "pc105"
EndSection

Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "HP L1755"
    HorizSync       30.0 - 83.0
    VertRefresh     56.0 - 76.0
    Option         "DPMS"
EndSection

Section "Monitor"
    Identifier     "Monitor1"
    VendorName     "Unknown"
    ModelName      "CRT-0"
    HorizSync       28.0 - 55.0
    VertRefresh     43.0 - 72.0
    Option         "DPMS"
EndSection

Section "Monitor"
    Identifier     "Monitor2"
    VendorName     "Unknown"
    ModelName      "CRT-1"
    HorizSync       30.0 - 83.0
    VertRefresh     56.0 - 76.0
    Option         "DPMS"
EndSection

Section "Monitor"
    Identifier     "Monitor3"
    VendorName     "Unknown"
    ModelName      "CRT-1"
    HorizSync       28.0 - 55.0
    VertRefresh     43.0 - 72.0
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "Quadro FX 1700"
    BusID          "PCI:1:0:0"
    Screen          0
EndSection

Section "Device"
    Identifier     "Device1"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "Quadro FX 1700"
    BusID          "PCI:2:0:0"
    Screen          0
EndSection

Section "Device"
    Identifier     "Device2"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "Quadro FX 1700"
    BusID          "PCI:1:0:0"
    Screen          1
EndSection

Section "Device"
    Identifier     "Device3"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "Quadro FX 1700"
    BusID          "PCI:2:0:0"
    Screen          1
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "TwinView" "0"
    Option         "TwinViewXineramaInfoOrder" "CRT-0"
    Option         "metamodes" "CRT-0: 1280x1024 +0+0"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen1"
    Device         "Device1"
    Monitor        "Monitor1"
    DefaultDepth    24
    Option         "TwinView" "0"
    Option         "TwinViewXineramaInfoOrder" "CRT-0"
    Option         "metamodes" "CRT-0: nvidia-auto-select +0+0"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen2"
    Device         "Device2"
    Monitor        "Monitor2"
    DefaultDepth    24
    Option         "TwinViewXineramaInfoOrder" "CRT-0"
    Option         "TwinView" "0"
    Option         "metamodes" "CRT-1: 1024x768 +0+0"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen3"
    Device         "Device3"
    Monitor        "Monitor3"
    DefaultDepth    24
    Option         "TwinView" "0"
    Option         "metamodes" "CRT-1: nvidia-auto-select +0+0"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection
Comment 1 Cyril Jaquier 2009-04-25 13:56:02 UTC
I have a similar issue since I upgraded to Jaunty 9.04 (Gnome 2.26). I have a single graphic cards but two monitors and TwinView.

I see my two screens but I can only interact with one. It seems that my mouse events are taken into account but one of the 2 screens does not seem to refresh. The behavior is a bit weird. Connecting with the same computer/VNC client to this machine worked perfectly with Intrepid (Gnome 2.24).
Comment 2 Cyril Jaquier 2009-05-11 19:59:17 UTC
(In reply to comment #1)
> I have a similar issue since I upgraded to Jaunty 9.04 (Gnome 2.26). I have a
> single graphic cards but two monitors and TwinView.
> 
> I see my two screens but I can only interact with one. It seems that my mouse
> events are taken into account but one of the 2 screens does not seem to
> refresh. The behavior is a bit weird. Connecting with the same computer/VNC
> client to this machine worked perfectly with Intrepid (Gnome 2.24).
> 

The fix proposed in [1] solved my issue.

[1] https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/353126
Comment 3 Charlie Brej 2009-06-10 19:19:46 UTC
Upgraded to Fedora 11 and seeing this issue. I don't think the things that Cyril is experiencing are related as those look related to compiz.

I have a separate desktops setup with two monitors. Connecting to machine:1 shows screen 1 but mouse movements are sent to screen 0. Clicks and movements are both functional but acted on the wrong screen. Connecting to screen 0 works as expected.
Comment 4 Jason Bell 2010-01-14 05:51:23 UTC
I thought I would provide an update to this issue.

I have recently installed Fedora 12 and found this issue to still be occurring... (As of Dec 2009)

The interesting thing is that it appears to be working fine with the Nouveau driver (ie works find across 2 separate screens), but using the nVidia driver causes the issue to occur.

So it appears the using the nvidia drivers is causing the problem...  The unfortunate fact is that the nvidia drivers are required for using multiple cards for multi-screen configurations.

Regards,
Jason.
Comment 5 André Klapper 2020-11-12 12:24:36 UTC
Vino is not under active development anymore and unmaintained.

Please use gnome-remote-desktop instead.

Closing this report as WONTFIX to reflect reality.