Modern Linux systems are designed with the assumption of a single session per user, and can misbehave to varying degree when you break this assumption. There is unfortunately no coordination or enforcement of this assumption. The common case we see this with ThinLinc is that users are logged in locally on the server, and then try to log in using ThinLinc using the same user. The ThinLinc session will then often hang, or immediately terminate, or behave strangely in various ways. The issue can also appear for users that enable multiple ThinLinc sessions per user. But as that is not the default, we do not see many reports about that. Users are also more likely to realise the reason for the issue in that case, as they actively changed a setting.
We do not consider this a ThinLinc issue, as the problem lies in the desktop environment, the applications and the base system. However, since it is much more frequently encountered with ThinLinc, we should consider mitigations for the problem.
https://community.thinlinc.com/t/budgie-de-connection-lasts-less-than-10-seconds/1078
Created attachment 1258 [details] gdm warning dialog For reference, modern GNOME detects and blocks if you attempt to log in both locally and remotely. See attached screenshot. No idea what mechanism it uses, though. However, it is compatible with ThinLinc. If I log in via ThinLinc, GDM will block both a local login, and via their headless RDP. I guess they added this to solve this specific problem when using their new headless feature.
