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

Bug#602934: marked as done (tightvncserver: Xtightvnc creates a broken socket under /tmp/.X11-unix/)

Your message dated Sat, 10 Sep 2022 22:44:03 +0200
with message-id <6f0b0f7f8235c8c1b4bec107320ed4930f81601b.camel@g-e-u-e-r.de>
and subject line Re: tightvncserver: Xtightvnc creates a broken socket under /tmp/.X11-unix/
has caused the Debian Bug report #602934,
regarding tightvncserver: Xtightvnc creates a broken socket under /tmp/.X11-unix/
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
602934: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602934
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: tightvncserver
Version: 1.3.9-6.1+b1
Severity: normal


Xtightvnc/tightvncserver creates a broken socket under /tmp/.X11-unix/

It should create /tmp/.X11-unix/X<displaynumber>

Example

vncserver :10

Should create /tmp/.X11-unix/X10

However it creates /tmp/.X11-unix/X1

vncserver  :19 creates X1
vncserver  :99 creates X9
vncserver :100 creates X10

And so on.

Thet socket /tmp/.X11-unix/X<displaynumber> is also never removed.

This creates a bug when using displaynumbers 1-0,10-19,20-29 and so on.

Makes restarting of Xtightvnc with the same displaynumber impossible.

Example

$ vncserver :11

New 'X' desktop is freedeb:11

Starting applications specified in /home/cryptr/.vnc/xstartup
Log file is /home/cryptr/.vnc/freedeb:11.log

$ ls /tmp/.X11-unix/
X1

$ vncserver -kill :11

$ ls /tmp/.X11-unix/
X1

$ vncserver :11
Couldn't start Xtightvnc; trying default font path.
Please set correct fontPath in the vncserver script.
Couldn't start Xtightvnc process.

_XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: server already running

Fatal server error:
Cannot establish any listening sockets - Make sure an X server isn't already running
_XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: server already running

Fatal server error:
Cannot establish any listening sockets - Make sure an X server isn't already running

$


Workaround (ugly but works):

rm /tmp/.X11-unix/X*
vncserver :11

I could not find anything in the tightvncserver script that removed or created the sockets so I assume it is in Xtightvnc.

/Lars

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: kfreebsd-i386 (i686)

Kernel: kFreeBSD 8.1-1-686
Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/dash

Versions of packages tightvncserver depends on:
ii  libc0.1                 2.11.2-7         Embedded GNU C Library: Shared lib
ii  libjpeg62               6b1-1            The Independent JPEG Group's JPEG 
ii  libx11-6                2:1.3.3-3        X11 client-side library
ii  libxext6                2:1.1.2-1        X11 miscellaneous extension librar
ii  perl                    5.10.1-15        Larry Wall's Practical Extraction 
ii  x11-common              1:7.5+7          X Window System (X.Org) infrastruc
ii  x11-utils               7.5+4            X11 utilities
ii  xauth                   1:1.0.4-1        X authentication utility
ii  zlib1g                  1:1.2.3.4.dfsg-3 compression library - runtime

Versions of packages tightvncserver recommends:
ii  x11-xserver-utils             7.5+2      X server utilities
ii  xfonts-base                   1:1.0.1    standard fonts for X

Versions of packages tightvncserver suggests:
pn  tightvnc-java                 <none>     (no description available)

-- no debconf information

--- End Message ---
--- Begin Message --- 
On Sat, 2021-08-21 at 22:19 +0200, Sven Geuer wrote:
> Control: tags -1 = unreproducible,moreinfo
> 
> Hi Lars,
> 
> On Tue, 09 Nov 2010 17:24:20 +0100 Lars <cryptr@cryptr.net> wrote:
> > Package: tightvncserver
> > Version: 1.3.9-6.1+b1
> > Severity: normal
> > 
> > 
> > Xtightvnc/tightvncserver creates a broken socket under /tmp/.X11-
> unix/
> > 
> > It should create /tmp/.X11-unix/X<displaynumber>
> > 
> > Example
> > 
> > vncserver :10
> > 
> > Should create /tmp/.X11-unix/X10
> > 
> > However it creates /tmp/.X11-unix/X1
> > 
> > vncserver  :19 creates X1
> > vncserver  :99 creates X9
> > vncserver :100 creates X10
> > 
> > And so on.
> > 
> > Thet socket /tmp/.X11-unix/X<displaynumber> is also never removed.
> > 
> > [...]
> 
> I cannot reproduce this issue with tighghvncserver 1:1.3.10-3.
> 
> Do you still see it? If yes, please provide more details about your
> enviroment.
> 
> Sven

I close this bug as it is unreproducible and no evidence has been
provided it still exists.

Sven

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
Reply to: