[Pkg-tigervnc-devel] Bug#879866: tigervnc-xorg-extension: QueryConnect connection w/o running vncconfig never timeouts

Pierre Dinh-van pierre-deb at qsdf.org
Thu Oct 26 16:21:00 UTC 2017


Package: tigervnc-xorg-extension
Version: 1.7.0+dfsg-7
Severity: normal

Dear Maintainer,

   * What led up to the situation?

I set up libvnc.so from tigervnc-xorg-extension for my stretch
workstations by adding a config file
/usr/share/X11/xorg.conf.d/99-vnc.conf with in it :


Section "Module"
	Load  "vnc"
EndSection
Section "Screen"
	Identifier "Screen0"
	Device     "Card0"
	Monitor    "Monitor0"

	Option "SecurityTypes" "VncAuth"
	Option "QueryConnect"
	Option "QueryConnectTimeout" "30"
	Option "IdleTimeout" "60"
	Option "UserPasswdVerifier" "VncAuth"
	Option "PasswordFile" "/etc/vncpasswd"
EndSection

   * What exactly did you do (or not do) that was effective (or
     ineffective)?

So the VNC server is launched when Xorg is started by my lightdm. I also
have a vncconfig -nowin which get started for the user directly after
login. So if our helpdesk is connecting to the client, the user should
first allow the remote VNC connection. The problem happens if a vnc
connection is tried while vncconfig is not running (for example, when
only lightdm is running on the display, because the user didn't logged in).

   * What was the outcome of this action?

In this case, the client reports after authentication :
"Unable to query the local user to accept the connection."

Fine, cause vncconfig is not started at this point.

All the further tries of connecting to the vnc sessions ends with :
"Another connection is currently being queried"

It doesn't seems to timeout at any time, until the X server is restarted.
If the user logs in, vncconfig is started but the client stills get the
previous message.

   * What outcome did you expect instead?

If no vncconfig is running, the server shouldn't go in the state of
"another connection is currently being queried".

In our case, it means that if a workstation gets by error an incoming
vnc connection before the user logs in, if the users needs our remote
help later on, it will not be possible for us to connect.

I tried it with the following clients from stretch, and they all give
the same symptoms :

- vinagre
- tigervnc-client
- gvncviewer
- xtightvncviewer


I tried to update tigervnc-xorg-extension to sid, but it seems to be the
same version as on stretch.

-- System Information:
Debian Release: 9.2
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages tigervnc-xorg-extension depends on:
ii  libaudit1          1:2.6.7-2
ii  libbsd0            0.8.3-1
ii  libc6              2.24-11+deb9u1
ii  libgcc1            1:6.3.0-18
ii  libgnutls30        3.5.8-5+deb9u3
ii  libjpeg62-turbo    1:1.5.1-2
ii  libpam0g           1.1.8-3.6
ii  libstdc++6         6.3.0-18
ii  xserver-xorg-core  2:1.19.2-1+deb9u2
ii  zlib1g             1:1.2.8.dfsg-5

Versions of packages tigervnc-xorg-extension recommends:
ii  tigervnc-common  1.7.0+dfsg-7

tigervnc-xorg-extension suggests no packages.

-- no debconf information



More information about the Pkg-tigervnc-devel mailing list