Tlserver service can not start on openSUSE tumbleweed

chanson@192:~> systemctl status vsmserver
× vsmserver.service - ThinLinc VSM server
     Loaded: loaded (/usr/lib/systemd/system/vsmserver.service; disabled; preset: disabled)
     Active: failed (Result: exit-code) since Thu 2025-05-29 00:04:22 CST; 4min 34s ago
 Invocation: aa53434c5d324cbbb2a41e96cfe9ffe2
    Process: 10056 ExecStart=/bin/bash --login -c /opt/thinlinc/sbin/vsmserver (code=exited, status=1/FAILURE)
        CPU: 179ms
chanson@192:~> systemctl start vsmserver
==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ====
启动“vsmserver.service”需要认证。
Authenticating as: root
Password: 
chanson@192:~> systemctl status vsmserver
× vsmserver.service - ThinLinc VSM server
     Loaded: loaded (/usr/lib/systemd/system/vsmserver.service; disabled; preset: disabled)
     Active: failed (Result: exit-code) since Thu 2025-05-29 00:04:22 CST; 4min 51s ago
 Invocation: aa53434c5d324cbbb2a41e96cfe9ffe2
    Process: 10056 ExecStart=/bin/bash --login -c /opt/thinlinc/sbin/vsmserver (code=exited, status=1/FAILURE)
        CPU: 179ms
chanson@192:~> sudo systemctl start vsmserver
[sudo] root :
Job for vsmserver.service failed because the control process exited with error code.
See "systemctl status vsmserver.service" and "journalctl -xeu vsmserver.service" for details.

Hi @chanson,

We will have to see if we can reproduce this error. In the mean time, could you please provide the output of journalctl -xeu vsmserver.service?

It blank, Nothing output!!!

Thinlinc installer does not support SUSE Tumbleweed change of file locations.
I did a PR on the ansible roles some time ago ( Fixed opensuse installation issuses by pewo · Pull Request #48 · cendio/ansible-role-thinlinc-server · GitHub ), but it was never merged.
It is a simple copy and you should be fine.

# cp /usr/lib/pam.d/sshd /etc/pam.d/sshd

# /opt/thinlinc/sbin/tl-setup

This works on openSUSE Tumbleweed VERSION=“20250522”

Thanks @pewo, yes I think you’re right. I’d forgotten about that.

For future reference, the corresponding bug in our Bugzilla is https://bugzilla.cendio.com/show_bug.cgi?id=7829.