GNOME Bugzilla – Bug 153652
Non-homogenous monitor size with Xinerama issue
Last modified: 2020-11-12 12:24:38 UTC
I'm using a Xinerama display, with 2 oddly-sized screens, a bit like that: |-----|XXXXX | |-----| | | | |-----|-----| i.e. the area marked XXXXX doesn't exist (it's above my rightmost monitor). The problem is that Vino isn't Xinerama-aware, and just think there's a big rectangular display comprising the XXXXX area. Furthermore, it seems the virtual content of that area is constantly changing, so Vino continuously sends new garbage to the VNC client. No need to say that this completely kills interactivity through my slow link. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.8-1-686 Locale: LANG=fr_FR.UTF-8@euro, LC_CTYPE=fr_FR.UTF-8@euro Versions of packages vino depends on: ii gconf2 2.8.0-1 GNOME configuration database syste ii libart-2.0-2 2.3.16-6 Library of functions for 2D graphi ii libatk1.0-0 1.8.0-2 The ATK accessibility toolkit ii libaudiofile0 0.2.6-4 Open-source version of SGI's audio ii libbonobo2-0 2.8.0-1 Bonobo CORBA interfaces library ii libbonoboui2-0 2.8.0-1 The Bonobo UI library ii libc6 2.3.2.ds1-16 GNU C Library: Shared libraries an ii libesd-alsa0 [libesd0] 0.2.34-1 Enlightened Sound Daemon (ALSA) - ii libgconf2-4 2.8.0-1 GNOME configuration database syste ii libgcrypt11 1.2.0-6 LGPL Crypto library - runtime libr ii libglade2-0 1:2.4.0-1 Library to load .glade files at ru ii libglib2.0-0 2.4.6-2 The GLib library of C routines ii libgnome-keyring0 0.4.0-1 GNOME keyring services library ii libgnome2-0 2.8.0-1 The GNOME 2 library - runtime file ii libgnomecanvas2-0 2.7.1-1 A powerful object-oriented display ii libgnomeui-0 2.8.0-1 The GNOME 2 libraries (User Interf ii libgnomevfs2-0 2.8.1-1 The GNOME virtual file-system libr ii libgnutls11 1.0.16-8 GNU TLS library - runtime library ii libgpg-error0 1.0-1 library for common error values an ii libgtk2.0-0 2.4.10-1 The GTK+ graphical user interface ii libice6 4.3.0.dfsg.1-7 Inter-Client Exchange library ii libjpeg62 6b-9 The Independent JPEG Group's JPEG ii liborbit2 1:2.10.2-1.1 libraries for ORBit2 - a CORBA ORB ii libpango1.0-0 1.6.0-1 Layout and rendering of internatio ii libpopt0 1.7-5 lib for parsing cmdline parameters ii libsm6 4.3.0.dfsg.1-7 X Window System Session Management ii libtasn1-2 0.2.10-4 Manage ASN.1 structures (runtime) ii libx11-6 4.3.0.dfsg.1-7 X Window System protocol client li ii libxext6 4.3.0.dfsg.1-7 X Window System miscellaneous exte ii libxml2 2.6.11-3 GNOME XML library ii libxtst6 4.3.0.dfsg.1-7 X Window System event recording an ii xlibs 4.3.0.dfsg.1-7 X Window System client libraries m ii zlib1g 1:1.2.1.2-1 compression library - runtime -- no debconf information
We've two options: 1) Treat each monitor as a separate screen. This means Vino would open a separate port for each monitor and you'd have to have a vncviewer window for each one. The VNC protocol doesn't have multiscreen support - that's why you'd have to treat it as two different displays, effectively. 2) Just ignore the parts of the screen which aren't actually visible on any monitors. Initialize them to black and never update them. (2) is probably the best plan. Sounds trivial but if we also want to stop asking the X server for the contents of the invisible parts it would actually require quite a bit of work.
I'm not sure if I should file a new bug for this, but I'll try my luck here. I have a xinerama setup with two 19" lcd. 2x 1280x1024. With vino 2.13.5 I get a screen the right size (2560x1024), but the right half of it is black. And to make matters worse, when I move the mouse on the left, visible part on the client - the mouse is actually on the right part on the server. Makes it 100% unusable with xinerama setups. The only vnc server I have tried that works is x11vnc, though I have to use an option to make it work ( http://www.karlrunge.com/x11vnc/#faq-xinerama ). You could perhaps take a look there, and see how they have done it? I would really, really like to be able to use vino on my computer :) Thanks.
Vino is not under active development anymore and unmaintained. Please use gnome-remote-desktop instead. Closing this report as WONTFIX to reflect reality.