[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#452003: marked as done (x11vnc: Option -noxinerama not recognized)

Your message dated Mon, 19 Nov 2007 18:31:41 -0800
with message-id <4742470D.30503@cogweb.net>
and subject line Bug#452003: x11vnc: Option -noxinerama not  recognized
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: x11vnc
Version: 0.9.3.dfsg.1-1
Severity: minor

# x11vnc -auth /home/liontooth/.Xauthority -display :0 -noxinerama -ncache 10 -scale 0.6

19/11/2007 10:20:52 *** unrecognized option(s) ***
19/11/2007 10:20:52     [1]  -noxinerama
19/11/2007 10:20:52 For a list of options run: x11vnc -opts
19/11/2007 10:20:52 or for the full help: x11vnc -help

# x11vnc -opts | grep noxinerama

x11vnc -help | grep noxinerama
-noxinerama            glued together via XINERAMA, and that screen is
                       noxinerama      disable -xinerama mode.
                       xinerama noxinerama xtrap noxtrap xrandr noxrandr

I actually don't currently use multi-head, but get this:

19/11/2007 10:30:06 Xinerama is present and active (e.g. multi-head).
19/11/2007 10:30:06 Xinerama: enabling -xwarppointer mode to try to correct
19/11/2007 10:30:06 Xinerama: mouse pointer motion. XTEST+XINERAMA bug.
19/11/2007 10:30:06 Xinerama: Use -noxwarppointer to force XTEST.
19/11/2007 10:30:06 fb read rate: 78 MB/sec
19/11/2007 10:30:06 screen setup finished.

I'm actually just tryint to turn off the multiple desktops that currently get created -- seems to be a new feature in 0.9.
In principle that's great, but it should also be possible to turn it off, and -noxinerama I thought might do it (or not).

So there's a bug in not recognizing a documented option, and a question about how to disable the new multiple desktops feature.
I realize the package is sadly orphaned ...


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux (SMP w/2 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages x11vnc depends on:
ii  libavahi-client3        0.6.21-2         Avahi client library
ii  libavahi-common3        0.6.21-2         Avahi common library
ii  libc6                   2.6.1-1          GNU C Library: Shared libraries
ii  libjpeg62               6b-14            The Independent JPEG Group's JPEG 
ii  libssl0.9.8             0.9.8g-2         SSL shared libraries
ii  libvncserver0           0.9.3.dfsg.1-1   API to write one's own vnc server
ii  libx11-6                2:1.0.3-7        X11 client-side library
ii  libxdamage1             1:1.1.1-3        X11 damaged region extension libra
ii  libxext6                1:1.0.3-2        X11 miscellaneous extension librar
ii  libxfixes3              1:4.0.3-2        X11 miscellaneous 'fixes' extensio
ii  libxinerama1            1:1.0.2-1        X11 Xinerama extension library
ii  libxrandr2              2:1.2.2-1        X11 RandR extension library
ii  libxtst6                1:1.0.2-1        X11 Testing -- Resource extension 
ii  zlib1g                  1: compression library - runtime

x11vnc recommends no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
While it's correct that -noxinerama is not recognized, the reason for my
the odd display -- ten screens long, and not the other desktops, but two
screens showing only the background image, several black screens, and a
duplicated main screen -- the reason for this is the

    -ncache 10

setting, a feature still in beta, and predicted to have issues. I've
reported upstream. As my main problem is not a packaging issue, I'm closing.

It's not a good idea, on the other hand, to strongly recommend using
ncache, as the current version does.

--- End Message ---

Reply to: