Only one user cannot connect with ThinLinc client, but most others can

Hello, I am a newbie to ThinLinc, great application though!

So all users can connect as expected to this new Redhat 8.5 server i set up the other day.
Using the latest ThinLinc version downloaded a couple days ago.

This one user rmorin, cannot connect, I deleted his .Xauthoruty file, I get same issue. The error in the xinit.log for this user is below, any help appreciated. Thanks

xauth: file /var/opt/thinlinc/sessions/rmorin/10/Xauthority does not exist
tl-xinit: Waiting for Xserver to accept connections…

Xvnc ThinLinc release 4.14.0 build 2408 - built Jan 26 2022 10:15:02
Copyright (C) 1999-2022 TigerVNC Team and many others (see README.rst)
See https://www.tigervnc.org for information on TigerVNC.
Underlying X server release 12013000

(II) Initializing extension VNC-EXTENSION

Thu Mar 31 10:48:03 2022
vncext: VNC extension running!
vncext: Listening for VNC connections on local interface(s), port 5910
vncext: created VNC server for screen 0
(II) Initializing extension Generic Event Extension
(II) Initializing extension SHAPE
(II) Initializing extension MIT-SHM
(II) Initializing extension XInputExtension
(II) Initializing extension XTEST
(II) Initializing extension BIG-REQUESTS
(II) Initializing extension SYNC
(II) Initializing extension XKEYBOARD
(II) Initializing extension XC-MISC
(II) Initializing extension XFIXES
(II) Initializing extension RENDER
(II) Initializing extension RANDR
(II) Initializing extension COMPOSITE
(II) Initializing extension DAMAGE
(II) Initializing extension MIT-SCREEN-SAVER
(II) Initializing extension DOUBLE-BUFFER
(II) Initializing extension RECORD
(II) Initializing extension DPMS
(II) Initializing extension Present
(II) Initializing extension DRI3
(II) Initializing extension X-Resource
(II) Initializing extension XVideo
(II) Initializing extension XVideo-MotionCompensation
(II) Initializing extension GLX
(II) IGLX: Loaded and initialized swrast
(II) GLX: Initialized DRISWRAST GL provider for screen 0
The XKEYBOARD keymap compiler (xkbcomp) reports:

Warning: Unsupported high keycode 372 for name ignored
X11 cannot support keycodes above 255.
This warning only shows for the first high keycode.
Errors from xkbcomp are not fatal to the X server
Connections: accepted: 127.0.0.1::35212
VNCSConnST: closing 127.0.0.1::35212: Clean disconnection
EncodeManager: Framebuffer updates: 0
EncodeManager: Total: 0 rects, 0 pixels
EncodeManager: 0 B (1:-nan ratio)
Connections: closed: 127.0.0.1::35212
ComparingUpdateTracker: 0 pixels in / 0 pixels out
ComparingUpdateTracker: (1:-nan ratio)
tl-xinit: Xserver ready for clients.
— System information —
ThinLinc 4.14.0
Linux apoc.hardent.com 4.18.0-348.20.1.el8_5.x86_64 #1 SMP Tue Mar 8 12:56:54 EST 2022 x86_64 x86_64 x86_64 GNU/Linux
Red Hat Enterprise Linux release 8.5 (Ootpa)
LSB Version: :core-4.1-amd64:core-4.1-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-4.1-amd64:desktop-4.1-noarch:languages-4.1-amd64:languages-4.1-noarch:printing-4.1-amd64:printing-4.1-noarch
— End system information —
xsetroot: unable to open display ā€˜localhost:10.0’
Cannot find xsri. Background image support not available.
xsetroot: unable to open display ā€˜localhost:10.0’
Failed to open display
/opt/thinlinc/libexec/xprop: unable to open display ā€˜localhost:10.0’
Openbox-Message: Failed to open the display from the DISPLAY environment variable.
Running /opt/thinlinc/etc/xstartup.d/01-tl-kinit.sh (Obtaining Kerberos ticket)
Unable to init server: Could not connect: Connection refused
Unable to init server: Could not connect: Connection refused
Unable to init server: Could not connect: Connection refused
/opt/thinlinc/libexec/tl-run-xstartup-feedback: warning: Unable to initialize GTK+
/opt/thinlinc/libexec/tl-run-xstartup-feedback: warning: Won’t present xstartup.d feedback
/opt/thinlinc/libexec/xprop failed: stderr:
/opt/thinlinc/libexec/xprop: unable to open display ā€˜localhost:10.0’

Unable to fetch SSO attribute TL_SENSITIVE_PARAMS
/opt/thinlinc/libexec/xprop failed: stderr:
/opt/thinlinc/libexec/xprop: unable to open display ā€˜localhost:10.0’

Unable to fetch SSO attribute TL_SENSITIVE_PARAMS
Running /opt/thinlinc/etc/xstartup.d/02-tl-dbus-launch.sh (Starting session D-Bus server)
Existing session D-Bus server found.
Setting initial D-Bus and systemd environment…
Running /opt/thinlinc/etc/xstartup.d/11-tl-set-title (Setting client window title)
Running /opt/thinlinc/etc/xstartup.d/12-tl-default-keyboard (Configuring default keyboard layout)
Setting default keyboard layout to ā€œusā€
Cannot open display ā€œlocalhost:10.0ā€
Running /opt/thinlinc/etc/xstartup.d/15-tl-shadow-notify (Enabling notifications when the session is shadowed)
Can’t open display: localhost:10.0
Running /opt/thinlinc/etc/xstartup.d/20-tl-select-profile.sh (Choosing a profile)
Unable to init server: Could not connect: Connection refused
Unable to init server: Could not connect: Connection refused
Unable to init server: Could not connect: Connection refused
/opt/thinlinc/libexec/tl-select-profile: warning: Unable initialize GTK+
/opt/thinlinc/libexec/tl-select-profile: warning: Can’t show introduction text
/opt/thinlinc/libexec/tl-select-profile: warning: Using first available profile as fallback
Running /opt/thinlinc/etc/xstartup.d/30-tl-xdg-user-dirs (Translating standard folders)
Running /opt/thinlinc/etc/xstartup.d/40-tl-mount-localdrives (Mounting local drives)
Running /opt/thinlinc/etc/xstartup.d/41-tl-lp-redir-launch (Setting up printer port redirection)
Unable to open DISPLAY, exiting …
Running /opt/thinlinc/etc/xstartup.d/43-tl-pulseaudio-launch.sh (Starting session PulseAudio server)
Unable to open DISPLAY, exiting …

Thu Mar 31 10:48:06 2022
Connections: accepted: 127.0.0.1::35314
SConnection: Client needs protocol version 3.8
Failed to start session PulseAudio server
SConnection: Client requests security type VncAuth(2)
VNCSConnST: Replacing existing connection
VNCSConnST: Server default pixel format depth 24 (32bpp) little-endian rgb888
Running /opt/thinlinc/etc/xstartup.d/50-tl-wait-smartcard (Waiting for smart card connection)
Client has no smartcard capability
Stopping initial window manager…
Openbox-Message: Failed to open the display from the DISPLAY environment variable.
Done.
Executing profile: gnome
Using XDG session: gnome
Updating D-Bus and systemd environment…
Ignoring invalid environment variable: ā€˜BASH_FUNC_which%%’
Executing XDG session command: gnome-session
Profile command exited with exit code 143
Running /opt/thinlinc/etc/xlogout.d/tl-kdestroy.sh
kdestroy: No credentials cache found while destroying cache
Running /opt/thinlinc/etc/xlogout.d/tl-umount-localdrives
tl-xinit: client terminated and returned 0
tl-xinit: Terminating X server…
VNCSConnST: closing 127.0.0.1::35314: Server shutdown
EncodeManager: Framebuffer updates: 1
EncodeManager: Tight:
EncodeManager: Solid: 1 rects, 786.432 kpixels
EncodeManager: 16 B (1:196609 ratio)
EncodeManager: Total: 1 rects, 786.432 kpixels
EncodeManager: 16 B (1:196609 ratio)
ComparingUpdateTracker: 0 pixels in / 0 pixels out
ComparingUpdateTracker: (1:-nan ratio)
tl-xinit: X server has terminated
tl-xinit: deleting …/11.1648736915.ended
tl-xinit: Session terminated. Exiting.

Hello @robmorin

ā€œlocalhost:10.0ā€ indicates that DISPLAY is over tcp which ThinLinc normally doesn’t use, not sure what’s going on here or how you ended up in this situation, perhaps you’ve modified the DISPLAY env variable of this user?

Regards,
Martin

Hey Martin, thanks for the reply. Indeed the user had in his bashrc profile display=127.0.0.1:10.0

So thinlinc does not use TCP? So no users should have thier display variable set? I am going to migrate from tiger NC to thinlinc on all Ubuntu and redhat servers, just want to make sure I should tell users not to set thier display variables. Thanks very much. Have a great day!

Hello,

Correct. Do not set these manually as it can lead to issues within ThinLinc.

Best regards,
Martin

1 Like