Bug 4678 - Add support for "driving" our client from another application
Summary: Add support for "driving" our client from another application
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Client (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: LowPrio
Assignee: Bugzilla mail exporter
: 3333 (view as bug list)
Depends on:
Reported: 2013-06-04 14:14 CEST by Peter Åstrand
Modified: 2022-12-06 13:19 CET (History)
3 users (show)

See Also:
Acceptance Criteria:


Description Peter Åstrand cendio 2013-06-04 14:14:10 CEST
Related to bug 2897. Although we are reluctant to hide the tlclient GUI altogether, it could be nice if it was possible to launch tlclient with command line arguments, and then programatically retrieve an exit code, describing if the login was ok etc. 

Currently, we have partial support for this: If you call tlclient with server, username, and password[*], a login will be automatically started. However, if the login fails, you will get an error message and then return to the interactive GUI. 

We could provide an option which makes tlclient exit with a exit code instead. Or, we could consider changing the current behaviour so that this is always done when server, username, and password[*] is provided. 

[*]: or other credentials
Comment 1 Peter Åstrand cendio 2013-07-22 11:08:43 CEST
One use case for this feature is when deploying up a "kiosk type" installation, similar to what you can do with Sun Ray kiosk sessions. In addition to specifying credentials on the command line, it is also possible to use tlclient.conf, ie:


Then, call tlclient with --loop. In this case, I believe we should not return to the GUI either, but exit.
Comment 2 Aaron Sowry cendio 2015-03-30 15:14:11 CEST
Reassigning for discussion.
Comment 3 Jens Maus 2015-07-24 09:43:33 CEST
I would like to join the discussion on this bugzilla entry since our company would really appreciate it if the ThinLinc client would be able to act like it is described here.

In fact, we already execute ThinLinc here from a shell-based script (see https://github.com/hzdr/thinstation/blob/master/ts/build/packages/hzdr/bin/scripts/qutselect_connect_tlinc.sh) and supply the password via stdin. However, we would appreciate it if there would be an option to complately hide the ThinLinc GUI while connecting to the Server. In addition, returning proper exit codes if a connection cannot be created would help to show than own error messages with the reason of the failure.

So please consider adding this kind of feature in one of the next ThinLinc versions as it would really improve usability of ThinLinc in such situations.

Another possibility would be of course to completely open-source the ThinLinc client (e.g. on Github) and allow own development/forks of it so that features like these can be more easily implemented by third-parties.
Comment 5 Pierre Ossman cendio 2022-07-13 10:12:19 CEST
*** Bug 3333 has been marked as a duplicate of this bug. ***

Note You need to log in before you can comment on or make changes to this bug.