If a user has tlog¹ enabled to log everything the user does on the system, then ThinLinc fails to function correctly. The client just stops, with "Connection to server xyz...". Looking in tlclient.log, we can see that things have stalled waiting for output from thinlinc-login: > ... > 2024-03-01T11:15:14: Updating host keys for lab-103. > 2024-03-01T11:15:14: ssh[E]: debug1: pledge: fork > 2024-03-01T11:15:14: ssh[E]: Locale charset is ANSI_X3.4-1968 (ASCII) > 2024-03-01T11:15:14: ssh[E]: Assuming locale environment is lost and charset is UTF-8 > 2024-03-01T11:15:14: ssh[E]: > 2024-03-01T11:15:14: ssh[E]: ATTENTION! Your session is being recorded! > 2024-03-01T11:15:14: ssh[E]: I can see the relevant output in tlog's logging though: > Mar 01 11:15:24 lab-103.lkpg.cendio.se tlog-rec-session[11248]: {"ver":"2.3","host":"lab-103.lkpg.cendio.se","rec":"1c83b02d7e70408e80225989e2b04293-2bf0-21b7f","user":"tltest","term":"","session":14,"id":1,"pos":0,"time":1709288114.934,"timing":">29+5>33","in_txt":"","in_bin":[],"out_txt":"THINLINC-LOGIN: HELLO 4.16.0\nTHINLINC-LOGIN: CONNECTED MASTER\n","out_bin":[]} So it seems like it is gobbling it up and fails to pass it on correctly. ¹ https://github.com/Scribery/tlog
This is a bug in tlog as far as I can tell. It redirects stderr output to stdout. And since we expect the data on stderr, we never see it. I reported it here: https://github.com/Scribery/tlog/issues/367
