Hi
just installed the server on my Pop os 22.04. when i try to connect via the thinlinc client, i can see it connects, but after the forward button i get “no executable profiles could be found on this system” have followed the advice in the older post here, but nothing works.
when i did [ ls /usr/… /xsessions ] i got pop.desktop … i also tryed to [ $ sudo apt install ubuntu-mate-desktop] … i had some luck but it only showed me my chrome browser… and nothing else.
any ideas ?
cheers
Hello,
So, you got ThinLinc to work as expected with MATE desktop, but are missing applications?
Regarding pop.desktop, try to incorporate the contents of pop.desktop to /opt/thinlinc/conf.d/etc/profiles.hconf and then systemctl restart vsmagent.service and try to log on again.
Kind regards,
Martin
Hi Martin,
Thank you for the help, did try to incorporate but i dont get it to work, as i have no clue how it should look for pop os, did try to use the GNOME profile and change it to something like in the profile [ /profile/pop] and the name to pop further down… to be honest im just guessing have no clue what it should be 
cheers!
Hello @bert
Well, it’s hard to know what you are expecting to see if you have no reference to compare with 
Could you perhaps share some screenshots of the environment you’re seeing, and be more detailed in what you think is wrong?
Oh ok. I was under the impression that you could atleast get a MATE session up and running.
Try to clear out whatever changes you’ve made to /opt/thinlinc/etc/conf.d/profiles.hconf, and add this section to it:
[/profiles/pop]
xdg_session=pop
name=Pop Desktop
description=Pop Desktop
screenshot=
cmdline=
testcmd=
description_from_testcmd=false
Also append pop to the order= parameter and then restart the service with systemctl restart vsmagent
Regards,
Martin
Hi Martin,
its going the right way, atleast now i have passed the profile chooser… it loaded up some thing, and it does not exit now. although i have now just a blue screen of nothing “F8” seems to work aswell
mvh
bert
The blue screen probably means that you’re already logged in with the same user account locally on the server.
If this is true, log out your local session or create another user for using with ThinLinc.
Kind regards,
/Martin
Hm, unsure what’s going on here for you.
I tried a fresh installation of PopOS 22.04 and made the change to profiles.hconf that I wrote about above. Everything works fine on this reference system, both with the native client and in browser. I get a full PopOS desktop, with all the graphical bells and whistles.
Could you share your session log file with us?
It’s located in /var/opt/thinlinc/sessions//last/xinit.log
Regards,
Martin
Just me, and a begginer to Linux, making it harder then it should be
i logged out on my Pop machine, then i started the thin link and it worked, as you said i cant be logged on the “server” machine at the same time im trying to connect with my thin client from pc
thank you so much for the help Martin! 
Regards
Bert
l-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 Dec 1 17:03:16 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 <I372> 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::33752
VNCSConnST: closing 127.0.0.1::33752: Clean disconnection
EncodeManager: Framebuffer updates: 0
EncodeManager: Total: 0 rects, 0 pixels
EncodeManager: 0 B (1:-nan ratio)
Connections: closed: 127.0.0.1::33752
ComparingUpdateTracker: 0 pixels in / 0 pixels out
ComparingUpdateTracker: (1:-nan ratio)
tl-xinit: Xserver ready for clients.
--- System information ---
ThinLinc 4.14.0
Linux pop-os 6.0.6-76060006-generic #202210290932~1669062050~22.04~d94609a SMP PREEMPT_DYNAMIC Mon N x86_64 x86_64 x86_64 GNU/Linux
Pop!_OS 22.04 LTS \n \l
No LSB modules are available.
--- End system information ---
Cannot find xsri. Background image support not available.
Running /opt/thinlinc/etc/xstartup.d/01-tl-kinit.sh (Obtaining Kerberos ticket)
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"
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Unsupported high keycode 372 for name <I372> 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
Obt-Message: Failed to open an Input Method
Obt-Message: Failed to open an Input Method
Obt-Message: Failed to open an Input Method
Running /opt/thinlinc/etc/xstartup.d/15-tl-shadow-notify (Enabling notifications when the session is shadowed)
XOpenIM() failed
Running /opt/thinlinc/etc/xstartup.d/20-tl-select-profile.sh (Choosing a profile)
Thu Dec 1 17:03:19 2022
Connections: accepted: 127.0.0.1::53874
SConnection: Client needs protocol version 3.8
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/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: pop
Using XDG session: pop
Updating D-Bus and systemd environment...
Executing XDG session command: env GNOME_SHELL_SESSION_MODE=pop /usr/bin/gnome-session --session=pop
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Unsupported high keycode 372 for name <I372> 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
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Unsupported high keycode 372 for name <I372> 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
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Unsupported high keycode 372 for name <I372> 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
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Unsupported high keycode 372 for name <I372> 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
Thank you, Martin, for supporting with installing an AWSOME window manager profile.
Here are the steps for other folks to install a new Window Manager profile:
(this is on Ubuntu)
Look for “awesome.desktop”
In my case it was there.
Open the config file (profiles.hconf) with your preferred terminal editor, I use VIM here:
$ sudo vim /opt/thinlinc/etc/conf.d/profiles.hconf
Find line 9 and add your desktop or windows manager after “order=”. I added awesome:
order=awesome unity ubuntu gnome gnome-classic kde xfce cinnamon mate lxde
Add the profile entry at the end of the config file. You can copy and paste this entry and modify it for your environment:
[/profiles/awesome]
xdg_session=awesome
name=Awesome Window Manager
description=Awesome
screenshot=
cmdline=
testcmd=
description_from_testcmd=false
Important here that you put the correct command to start your window manager after “xdg_session=”
Restart the “vsmagent” agent:
$ sudo systemctl restart vsmagent
Now you can login into your ThinLinc client and you should see AWESOME window manager profile listed.