What to do in this situation? I can’t terminate the session with tlctl, because it should be done automatically
Any ideas?
8 posts - 4 participants
]]>I run a computer club at my school. I am looking to have a TL server at home, and access the server from the school computers (we are NOT admins) using the web access (port 300). I tried reverse proxying port 300 using Fossorial Pangolin, but was not able to access the server (aka it said redirection failed). How do i do this, optimally without using port forwarding (it is OK because i trust my students enough to let know the city i live in but it’d be better not to use it for load and security reasons)?
10 posts - 3 participants
]]>on the journey moving to Linux, looking for a remote solution
Mint latest fresh install
openssh-server installed.
port 22 opened - can ssh to the machine
ThinLinc server ( .deb) installed
/opt/thinlinc/sbin/tl-setup ends with a
2026-02-19 18:26:57,804: Configuring CUPS…
2026-02-19 18:26:57,804: Adding ‘nearest’ printer queue…
2026-02-19 18:27:02,852: Adding ‘thinlocal’ printer queue…
2026-02-19 18:27:07,795: Done
2026-02-19 18:27:14,425: Traceback (most recent call last):
2026-02-19 18:27:14,425: File “/opt/thinlinc/modules/thinlinc/tlsetup/firewall.py”, line 77, in Oooo0o0oO0
2026-02-19 18:27:14,425: “yes” if iI111iiIi11i [ o0o . name ] . get_active ( ) else “no” )
2026-02-19 18:27:14,425: ~~~~~~~~~~~~~^^^^^^^^^^^^^^
2026-02-19 18:27:14,425: KeyError: ‘OpenSSH’
Any hints are highly appreciated
Thanks
Oskar
3 posts - 2 participants
]]>type=AVC msg=audit(1770892256.261:1384): avc: denied { getattr } for pid=35078 comm=“tl-session” name=“/” dev=“pidfs” ino=1 scontext=system_u:system_r:thinlinc_session_t:s0 tcontext=system_u:object_r:pidfs_t:s0 tclass=filesystem permissive=0
Otherwise from a user perspective, the sessions were behaving as expected.
For now I simply added a policy to allow this, but I’m interested to know if this is a common issue and if there’s a better way to address this.
5 posts - 3 participants
]]>/var/log/vsmagent.log.
From what I can tell, process 123 indeed doesn’t exist anymore, for a good reason: it corresponds to the previous tl-session, which from a user perspective ended as expected.
The log entry seems to be generated by an obfuscated /opt/thinlinc/modules/thinlinc/vsm/handler_verifysessions.py.
What could be reasons for ThinLinc believing that the previous session should be alive?
2 posts - 2 participants
]]>@samuel initially suggested using the info returned by loginctl list-sessions for detecting potentially conflicting sessions (see comment 18). I understand that you’ll be implementing this differently, but can you clarify the logic you intended to apply on the info obtained from loginctl?
Thanks!
11 posts - 3 participants
]]>2 posts - 2 participants
]]>It is working exactly as expected for the web client access, but does not work with the native client. (Version 4.19)
After the password, I get the “Second Factor:" prompt, and then after entering the OTP code, it get “Couldn’t set up secure tunnel to ThinnLinc Agent. (Login Failed! Wrong username or password).”
Where could I look to see what is different between the two logins, or determine the issue with the Native Client?
2 posts - 2 participants
]]>However, they also have a need for remote desktop support to specific systems. In some cases these systems are even limited to a single user utilizing them, in others there might be a group of Linux hosts where the users would want direct remote desktop to them. They may likely want to choose which host in the group that they connect to.
Thinlinc is a robust Linux Remote Desktop solution but am I missing knowledge where users have the ability using the ThinLinc client to select remote control of a specific Linux system running an agent? The documentation only appears to talk about automatically load balancing across agents. I am watching for a remote desktop solution that is robust but has to also allow manual selection of which host to attach to?
I apologize if this is a well known capability but I watched multiple videos and at least skimmed through the documentation.
Thank you,
-Nyle
13 posts - 2 participants
]]>Thanks.
4 posts - 4 participants
]]>i got a server Xubuntu 24.04.3 LTS with thinlinc version 4.19 , xfce 4.20 nividia NVIDIA GeForce GTX 1050 Ti installed but i dont use virtualGL on the server side and the client is running on windows 11. It is a 3 monitor setup on the client side with 1 main screen at 4k and 2 screen vertical on top of eachother off resolution 2560x1440. So i used these 2 screens for the thinlinc connection to the server. The 4k screen is just my windows screen. Everything was working fine for a month and now suddenly it doens’t scale anymore over the 2 screens. This happend out of the blue. When i press f8 and select again the 2 screens it flashes the 2screen setup for a few seconds and then i just got 1 screen. While like you see on my display option i selected full screen on selected monitors. I rebooted serveral times and the i got it thinlinc session manager nice on 2 screens but when i choose the session it flips to vnc1.
Can anyone help me to fix this thank you for all the help and support 
5 posts - 2 participants
]]>I have what at first glance might look like one of the “I can’t start the Xsession” problems we see here from time to time, but this is slightly different I think.
System: AlmaLinux 9.7, patched 25-12-22, TL 4.19 for both server and clients, air-gapped with very strict control about what can be exported from the server (so no logfiles to show, sorry about that)
Symptoms: Of about 20 users, some can log in to their Xsession (gnome and gnome classic) without any issues while others get the typical error message after the initial session configuration indicating that a xsession is already running for that user. But the thing is that this happens even after the server is rebooted in a proper way! During debugging I logged in as a regular user on a freshly rebooted server without any problems, checked for other users (none), user processes apart from my own (none), sessions apart from mine (none), sockets under /tmp/.X11-unix apart from mine (none), other lockfiles that I could think of (none), any strange process running related to other users (none). Clean, empty and nothing! The other user could still not start the Xsession. Terminate old sessions box checked in the client UI. All the central log files under /var/log look clean on the way in and then nothing strange when “bouncing out”. xinit.log for the user just says that the XDG session command is executed followed by the line with exit code 0 and then tl-kdestroy.sh and so on. Just like when you already have a xsession running. But I am pretty sure there is none.
Any ideas?
Per
Edit: the users with issues used to be able to log in and start the xsession before we updated to 4.19.
9 posts - 2 participants
]]>Recently there were some updates on the box and now I cannot get KDE plasma to start..
I can get to the profile selection menu.. I select kde… The kde splash logos display.. and I then end up with an all black display with the magnifier app (Magnus) window.. thats it.. no toolbar, menus etc.. all black.
I swear this came up once in the past…and I eventually figured out how to fix it.. but I cannot find any details.. so here I am trying to debug it again. I created a new user on the box and it DOES work for the new user.. so I know it is something in config/caching for my original user. I am running lightdm and everything seems to be fine. Other desktops work fine.. I can connect with XFCE just fine.. its just an issue with KDE.
I tried these things and nothing changed:
Connecting with ‘terminate existing session’
Checked Thinlinc sessions in a separate terminal on the host to see if multiple sessions were in play but only saw the one that is not working.
Clear existing kde configs with
mv .kde .kde.bak
mv .config .config.bak
mv .local .local.bak
rm -rf ~/.config/plasma* ~/.config/kdeglobals ~/.config/kwinrc ~/.config/kglobalshortcutsrc ~/.config/plasmashellrc ~/.config/dolphinrc
rm -rf ~/.cache/plasma* ~/.cache/krunner ~/.cache/org.kde.dirmodel-qml.kcache
I am at a loss. I don’t know if it could be something that can be corrected via the Thinlinc apps or if its something in the Linux arena ..
Does anyone have any ideas? Any info would be greatly appreciated!..
4 posts - 2 participants
]]>I am currently running a ThinLinc setup with two servers: one is Master & Agent and the other one is just an Agent, so both can host user sessions but only the Master distributes them. Both servers currently have an external and an internal IP on two separate NICs, so users can connect from the internet or the internal network.
Now, I plan to extend the cluster with two additional servers for a total of 4. But: I don’t have any additional external IPs available. My idea was to create a new setup where there is 1 small VM that just acts as Master (with an external IP) and the 4 servers would all be simple Agents which do not have external IPs.
However, from what I read in the manual ( Network requirements — ThinLinc Administrator's Guide ) it sounds like every Agent also would necessarily need an external IP, because clients connecting from the internet would directly connect to their Agent after they’ve been transferred by the Master and a session is established.
Is a setup like this possible in any way? That there is a single Master/Relaying VM that routes traffic between external (internet-side) clients and the 4 Agents on the internal network? Either directly in ThinLinc or via more-or-less janky trickery with proxies/firewall rules?
ChatGPT, when asked, said something about a mysterious “master_gateway = 1” parameter in vsmserver.conf but since I did not find anything about this parameter with Google or in the manual, I think it may have been hallucinating there. 
Thanks in advance!
3 posts - 2 participants
]]>The server runs Thinlinc 2.19 on Ubuntu 24.04 (on X11, not Wayland). The client runs Thinlinc 2.19 on Windows 11 (64 bits). Connecting to this server through Thinlinc is, most of the time, smooth and speedy. But there are days when, for many hours, using Thinlinc becomes impossibly slow. And by that I mean, slow as in the screen takes a couple of seconds to refresh. This computer server is never turned off, the session itself is rarely closed or re-initiated.
Today was one of those days, where the server became unusably slow even nothing changed - the connection quality seems the same in both sides, the server session was not restarted. So, I took the opportunity to start collecting some information. First, I installed Thinlinc 2.19 on a different client computer, which runs on Ubuntu 23.04, and tried logging in to the server from there. Same problem: server access is slow to the point of unusable. So this shows me the problem is not on the OS/computer specs side of things. Client connection: I tried from fast wifi connections in different places. All gave the same problem. But I also measured the details of the wifi connection where the client usually connects from, and that connection has ~550mps download and 250mbps upload, average latency of 35ms and jitter of 12ms. Also, I gathered all patience that I could muster and opened a web browser on the server to test the connection there. About 1Gb/s download and 1Gb/s upload, average latency of 12ms and jitter of 17ms. Clearly, the problem does not seem to be connection related. Just in case I tried doing other internet operation in both computers, downloading different sizes of files, uploading, streaming data from SSH. All good and speedy.
However, the “Connection Info” from the Thinlinc client, while connected to the server, does give us a hint: just about 3200 kbits/s of expected line speed. This is odd, though, since like I just said, connection on the server side and on the client side seems fine. I tried re-starting Thinlinc on the server. No change. I tried rebooting the client and the server. No change. I tried all possible combinations of Thinlinc client parameters in what regards compression, optimizations, etc. Nothing. Also, the server and the client both have enough CPU and RAM available (by a large margin) and the server has a dedicated Nvidia GPU.
Would you have any suggestion on how I could proceed trying to diagnose the problem?
Thanks!
3 posts - 3 participants
]]>2025-11-27 22:19:02 INFO vsmagent: VSM agent version 4.19.0 build 4116 started
2025-11-27 22:19:02 INFO vsmagent: My public hostname is 172.25.70.39
2025-11-27 22:19:15 ERROR vsmagent: Exception in callback ServerProtocol.\_call_callback(, , {…}, {…})
2025-11-27 22:19:15 ERROR vsmagent: handle: <Handle ServerProtocol.\_call_callback(, , {…}, {…})>
2025-11-27 22:19:15 ERROR vsmagent: ----------------------------------------
2025-11-27 22:19:15 ERROR vsmagent: Traceback (most recent call last):
2025-11-27 22:19:15 ERROR vsmagent: File “/usr/lib64/python3.12/asyncio/events.py”, line 88, in \_run
2025-11-27 22:19:15 ERROR vsmagent: self.\_context.run(self.\_callback, \*self.\_args)
2025-11-27 22:19:15 ERROR vsmagent: File “/opt/thinlinc/modules/thinlinc/vsm/xmlrpc.py”, line 341, in \_call_callback
2025-11-27 22:19:15 ERROR vsmagent: self . \_response = self . \_callback ( methodname , \* params )
2025-11-27 22:19:15 ERROR vsmagent: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2025-11-27 22:19:15 ERROR vsmagent: File “/opt/thinlinc/modules/thinlinc/vsm/vsmagent.py”, line 199, in \_handle_method
2025-11-27 22:19:15 ERROR vsmagent: i1iI1 = I1i1i . handle ( method , params )
2025-11-27 22:19:15 ERROR vsmagent: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2025-11-27 22:19:15 ERROR vsmagent: File “/opt/thinlinc/modules/thinlinc/vsm/handler_reqsession.py”, line 48, in handle
2025-11-27 22:19:15 ERROR vsmagent: self . \_check_old_client ( )
2025-11-27 22:19:15 ERROR vsmagent: File “/opt/thinlinc/modules/thinlinc/vsm/handler_reqsession.py”, line 60, in \_check_old_client
2025-11-27 22:19:15 ERROR vsmagent: self . \_check_valid_user ( )
2025-11-27 22:19:15 ERROR vsmagent: File “/opt/thinlinc/modules/thinlinc/vsm/handler_reqsession.py”, line 66, in \_check_valid_user
2025-11-27 22:19:15 ERROR vsmagent: self . \_setup_session_info ( )
2025-11-27 22:19:15 ERROR vsmagent: File “/opt/thinlinc/modules/thinlinc/vsm/handler_reqsession.py”, line 90, in \_setup_session_info
2025-11-27 22:19:15 ERROR vsmagent: self . \_test_next_display ( )
2025-11-27 22:19:15 ERROR vsmagent: File “/opt/thinlinc/modules/thinlinc/vsm/handler_reqsession.py”, line 130, in \_test_next_display
2025-11-27 22:19:15 ERROR vsmagent: self . \_found_free_display ( )
2025-11-27 22:19:15 ERROR vsmagent: File “/opt/thinlinc/modules/thinlinc/vsm/handler_reqsession.py”, line 173, in \_found_free_display
2025-11-27 22:19:15 ERROR vsmagent: os . unlink ( OOo )
2025-11-27 22:19:15 ERROR vsmagent: OSError: \[Errno 30\] Read-only file system: ‘/tmp/.X11-unix/X10’
2025-11-27 22:19:15 ERROR vsmagent: ----------------------------------------
2025-11-27 22:19:17 ERROR vsmagent: Exception in callback ServerProtocol.\_call_callback(, , {…}, {…})
2025-11-27 22:19:17 ERROR vsmagent: handle: <Handle ServerProtocol.\_call_callback(, , {…}, {…})>
2025-11-27 22:19:17 ERROR vsmagent: ----------------------------------------
2025-11-27 22:19:17 ERROR vsmagent: Traceback (most recent call last):
2025-11-27 22:19:17 ERROR vsmagent: File “/usr/lib64/python3.12/asyncio/events.py”, line 88, in \_run
2025-11-27 22:19:17 ERROR vsmagent: self.\_context.run(self.\_callback, \*self.\_args)
2025-11-27 22:19:17 ERROR vsmagent: File “/opt/thinlinc/modules/thinlinc/vsm/xmlrpc.py”, line 341, in \_call_callback
2025-11-27 22:19:17 ERROR vsmagent: self . \_response = self . \_callback ( methodname , \* params )
2025-11-27 22:19:17 ERROR vsmagent: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2025-11-27 22:19:17 ERROR vsmagent: File “/opt/thinlinc/modules/thinlinc/vsm/vsmagent.py”, line 199, in \_handle_method
2025-11-27 22:19:17 ERROR vsmagent: i1iI1 = I1i1i . handle ( method , params )
2025-11-27 22:19:17 ERROR vsmagent: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2025-11-27 22:19:17 ERROR vsmagent: File “/opt/thinlinc/modules/thinlinc/vsm/handler_reqsession.py”, line 48, in handle
2025-11-27 22:19:17 ERROR vsmagent: self . \_check_old_client ( )
2025-11-27 22:19:17 ERROR vsmagent: File “/opt/thinlinc/modules/thinlinc/vsm/handler_reqsession.py”, line 60, in \_check_old_client
2025-11-27 22:19:17 ERROR vsmagent: self . \_check_valid_user ( )
2025-11-27 22:19:17 ERROR vsmagent: File “/opt/thinlinc/modules/thinlinc/vsm/handler_reqsession.py”, line 66, in \_check_valid_user
2025-11-27 22:19:17 ERROR vsmagent: self . \_setup_session_info ( )
2025-11-27 22:19:17 ERROR vsmagent: File “/opt/thinlinc/modules/thinlinc/vsm/handler_reqsession.py”, line 90, in \_setup_session_info
2025-11-27 22:19:17 ERROR vsmagent: self . \_test_next_display ( )
2025-11-27 22:19:17 ERROR vsmagent: File “/opt/thinlinc/modules/thinlinc/vsm/handler_reqsession.py”, line 130, in \_test_next_display
2025-11-27 22:19:17 ERROR vsmagent: self . \_found_free_display ( )
2025-11-27 22:19:17 ERROR vsmagent: File “/opt/thinlinc/modules/thinlinc/vsm/handler_reqsession.py”, line 173, in \_found_free_display
2025-11-27 22:19:17 ERROR vsmagent: os . unlink ( OOo )
2025-11-27 22:19:17 ERROR vsmagent: OSError: \[Errno 30\] Read-only file system: ‘/tmp/.X11-unix/X11’
2025-11-27 22:19:17 ERROR vsmagent: ----------------------------------------
2 posts - 2 participants
]]>Let me explain. When connecting to a remote server desktop with ThinLinc, if we lose connection the Thinlinc simply closes the connection window entirely, and shows a separate popup message to inform that connection was lost. Then, the user needs to keep an eye at the connection and, upon noticing that it was re-established, the user needs to manually open the ThinLinc client and re-attempt to connect.
In comparison, when connecting to a remove server desktop with Citrix Workspace, if we lose connection, the Citrix Workspace client app shows the following:
That is, the app does not immediately close. For 5 minutes, it keeps displaying the last seen remote screen before the connection was lost, and it keep repeatedly trying to re-stablish connection. If at some point it succeeds, then the user can simply resume working.
Would it be possible to consider implementing something similar in ThinLinc? This is so so helpful when connection is lost due to minor fluctuations in signal (for ex. when connecting to a server from an airport, airplane, train, or abroad).
Thanks for your consideration!
3 posts - 2 participants
]]>I have been trying to get a connection using ThinLinc via an SSH reverse tunnel back to a Kali Linux system but I have not been able to get it to work. I have searched for, and found, several previous posts about the topic but I have not been able to translate what I see in those posts into a working configuration.
I can connect back to the Kali Linux system through the reverse tunnel via standard SSH, but am unable to get a connection using the ThinLinc client. I have also been able to create a reverse tunnel back to the Kali Linux system and use the ThinLinc web connection.
The setup:
The remote Kali Linux system that I have is using autossh to create the tunnel to the intermediary Linux system. The command on the Kali Linux system is:
autossh -M 0 -o "ServerAliveInterval 30" -o "ServerAliveCountMax 3" -i /home/<user>/.ssh/<ssh_key> -R 3333:localhost:22 -R 33389:localhost:3389 -R 3300:localhost:300 -o "StrictHostKeyChecking=no" user@intermediary_Linux_system.org -N
Port 3333 tunnels SSH back to the Kali Linux system, port 33389 tunnels back to RDP on port 3389 (XRDP is actually not currently running since I like ThinLinc so much more), port 3300 tunnels back to the ThinLinc web service on port 300.
On my remote system I can create an SSH tunnel connection to the intermediary system using the following command from my remote system:
ssh -qnN -L 3333:127.0.0.1:3333 user@intermediary_Linux_system.org
Then I can SSH to the remote Kali Linux system via the reverse tunnel from my remote system using the following command:
ssh -p 3333 127.0.0.1
I can tunnel to the ThinLinc web connection if I connect from my remote system to the SSH reverse tunnel using this command:
ssh -qnN -L 3300:127.0.0.1:3300 user@intermediary_Linux_system.org
and then connect via a web browser using this URL
which ends up taking me to the remote ThinLinc web connect @ https://192.168.0.147:300/agent
I have tried many, many iterations of the
HOST_ALIASES=
in the ~/.thinlinc/tlclient.conf file but have never gotten anything to work.
Hopefully someone out there has been able to make something like this work and can help get me pointed in the right direction. What I am missing here?
Thanks very much in advance!
13 posts - 2 participants
]]>2 posts - 2 participants
]]>The agent server is working fine. In the vsmagent.log is the error: WARNING tl-session: mkdir: Permission denied.
Tracing this error shows that it is trying to create a directory under /var/opt/thinlinc/sessions/ and fails. If the user directory exists it can’t create the session directory. If the user directory doesn’t exist, it can’t create the user directory.
This occurs under 4.18 and 4.19. This appears to be a selinux permission issue. I have rerun the thinlinc selinux config, but it didn’t fix it.
The selinux context of /var/opt/thinlinc/sessions is “system_u:object_r:usr_t:s0”
Any ideas?
6 posts - 3 participants
]]>2 posts - 2 participants
]]>ThinLinc Client (4.19) installed on MacOS Tahoe
Server (tl-4.19) on Ubuntu 24.04
Log:
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”
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
Running /opt/thinlinc/etc/xstartup.d/15-tl-shadow-notify (Enabling notifications when the session is shadowed)
Running /opt/thinlinc/etc/xstartup.d/20-tl-select-profile.sh (Choosing a profile)
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)
Running /opt/thinlinc/etc/xstartup.d/43-tl-pulseaudio-launch.sh (Starting session PulseAudio server)
W: [pulseaudio] main.c: Couldn’t canonicalize binary path, cannot self execute.
Session PulseAudio server started. Redirecting applications…
Running /opt/thinlinc/etc/xstartup.d/50-tl-wait-smartcard (Waiting for smart card connection)
Stopping initial window manager…
Done.
Executing profile: ubuntu
Using XDG session: ubuntu
Updating D-Bus and systemd environment…
Executing XDG session command: env GNOME_SHELL_SESSION_MODE=ubuntu /usr/bin/gnome-session --session=ubuntu
Profile command exited with exit code 1
Running /opt/thinlinc/etc/xlogout.d/tl-kdestroy.sh
Running /opt/thinlinc/etc/xlogout.d/tl-umount-localdrives
tl-xinit: client terminated and returned 0
tl-xinit: Terminating X server…
tl-while-x11: lost Xserver connection, terminating child 10037 …
X I/O error
tl-while-x11: lost Xserver connection, terminating child 10047 …
Fri Oct 24 19:19:21 2025
VNCSConnST: Closing 127.0.0.1::44750: Server shutdown
EncodeManager: Framebuffer updates: 186
EncodeManager: Tight:
EncodeManager: Solid: 101 rects, 1.26187 Mpixels
EncodeManager: 1.57812 KiB (1:3124.19 ratio)
EncodeManager: Bitmap RLE: 42 rects, 9.123 kpixels
EncodeManager: 1.24609 KiB (1:28.9937 ratio)
EncodeManager: Indexed RLE: 184 rects, 131.944 kpixels
EncodeManager: 46.5986 KiB (1:11.1068 ratio)
EncodeManager: Tight (JPEG):
EncodeManager: Full Colour: 176 rects, 575.663 kpixels
EncodeManager: 488.033 KiB (1:4.61187 ratio)
EncodeManager: Total: 503 rects, 1.9786 Mpixels
EncodeManager: 537.456 KiB (1:14.3915 ratio)
tl-xinit: Xserver terminated and returned 0
tl-xinit: deleting ../10.1761326298.ended
tl-xinit: Session terminated. Exiting.
I tried different approaches found on the forum with no luck. I’ve seen empty welcome screen once and then after a few minutes ubuntu screen finally loaded but next time again session closed immediately.
I have quite high-end equipment (server and client) and 1Gbps LAN connection.
I do not know how to solve it…
3 posts - 2 participants
]]>it would be nice if I were able to run the ThinLinc client by clicking on a link (e.g. tlclient://user:[email protected]) and the client automatically fills out the provided fields (user, pass, serveraddress) and if possible tries to autologin with these values.
I know there is the WebAccess application, but it doesn’t provide the full functionallity of the client application (e.g. file transfer, direct clipboard support, etc.).
For Windows a protocol handler to run the client via some custom protocol prefix like tlclient:// is easily added into the registry:
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\tlclient]
“URL Protocol”=“”
[HKEY_CLASSES_ROOT\tlclient\shell]
[HKEY_CLASSES_ROOT\tlclient\shell\open]
[HKEY_CLASSES_ROOT\tlclient\shell\open\command]
@=“\"C:\\Program Files\\ThinLinc client\\tlclient.exe\" \"%1\"”
In Linux you could add the handler via a new .desktop file (e.g. tlclient-handler.desktop) in the /usr/share/applications/ folder:
[Desktop Entry]
Type=Application
Exec=/opt/thinlinc/bin/tlclient %u
Name=ThinLinc Client Handler
Icon=thinlinc-client
MimeType=x-scheme-handler/tlclient;
Terminal=false
NoDisplay=true
The argument the handlers are sending to the application is always the full URL, so the client would need to parse this and fill out the fields accordingly.
Would be great if you implement something like this.
Thanks
Martin
2 posts - 2 participants
]]>Good work
Thanks!
Jan
2 posts - 2 participants
]]>i see, that the agents try to create the homedirectories but as nfs clients they dont have the authority (yes, i know i can change this behavior). is there a way to let the thinlinc server create the home directory?
Furthermore, in linux when a usershome directory ist created the content of /etc/skel will be copied into the homedir. i see this is not the case when thinlinc creates the directory. is there a work-around for that?
thank you
regards j.
4 posts - 2 participants
]]>