Thinlinc cannot create session
Apparently it needs /var/opt/thinlinc and /var/opt/thinlinc/sessions, and they were not automatically created for some reason. And also you need to restorecon of them when created.
My work, my view, and my imagination

Apparently it needs /var/opt/thinlinc and /var/opt/thinlinc/sessions, and they were not automatically created for some reason. And also you need to restorecon of them when created.
Check entries in /boot/loader Reinstalling kernel should update them.
Sometime a multi users linux box can go extremely slow even if there are not much actually. This may be caused by abandoned user sessions. To get rid of these, please run: systemctl | grep “abandoned” | cut -f3 -d ‘ ‘ | xargs systemctl stop
This happens mostly when your NVidia display card is too old to be compatible to the most recent driver version. Although the older version of NVidia driver is still available in the corresponding repository, like cuda-rhel9.repo, which supports driver version from 515 till 580, you can only install latest version when doing dnf install nvidia-driver […]
Sometime when updated NVidia driver and CUDA on Rocky Linux systems, running nvidia-smi shows that kernel driver version mismatch. If you run dmseg It will show: NVRM: API mismatch: the client has the version aaa.bbb, butNVRM: this kernel module has the version ccc.ddd. PleaseNVRM: make sure that this kernel module and all NVIDIA driverNVRM: components […]
This sometimes happen when the automatic nvidia kernel module installation fails. The workaround is:
First, use rpm -q gpg-pubkey –qf ‘%{NAME}-%{VERSION}-%{RELEASE}\t%{SUMMARY}\n’ to identify keys from obsolete repositories, then use rpm -e gpg-pubkey-xxxxxxxx-yyyyyyyy to remove the keys that were imported from the SHA1 era. Then have the offending packages removed by rpm -q –nosignature –querybynumber xxxx where you can get the xxxx from the stderr messages from rpm -qa >/dev/null
When upgrading OS or replacing drives, the UEFI booting may not be able to automatically installed on the boot drive, resulting not able to update the boot menu to include the new kernels. When you do grub2-install <your boot device>, it errors out with information: Installing for x86_64-efi platform.grub2-install: error: This utility should not be […]
It was found that systemd-logind malfunctioned, By restarting it — systemctl restart systemd-logind The problem is resolved.