Parameters in /profiles/¶
In this section, we will describe all the parameters currently used by the profiles feature.
The profile that should be preselected when the profile chooser starts, and the profile to be chosen when there is a problem displaying the profile chooser to the user.
A space separated list of profiles that should be available for the user to choose from. The profiles will be displayed in the same order as specified here.
If this parameter is true then the introduction text specified in
introductionwill be displayed by the profile chooser. Enabled by default.
This parameter specifies the title for the introduction text specified in
introduction. It is also shown above the profile list. Pango Markup can be used here to provide styling to the text (e.g. italicized words).
This parameter specifies the the introduction text shown by the profile chooser. Pango Markup can be used here to provide styling to the text (e.g. bold or italicized words). If
show_introis set to false then this text is not shown.
Each profile is defined under a section named
/profiles/<profile key>. It has the following fields:
- /profiles/<profile key>/xdg_session¶
Connects this ThinLinc profile with a system desktop session configuration. The directories
/usr/share/xsessionswill be searched for a file matching
<xdg_session>.desktop. It is recommended that this field is used for all modern desktop environments as it sets up important environment variables.
testcmdwill all be implicitly filled in by the system configuration. You can override those values individually by specifying a different value in the ThinLinc configuration.
Multiple values can be specified in this field, separated by spaces. The first matching configuration will be used. If no matching configuration can be found then the profile will not be shown.
If the configuration is listed in
/etc/upstart-xsessionsthen the specified command is ignored and an Upstart user session will be started instead. A manually specified
cmdlinecan still be used to override the command.
- /profiles/<profile key>/name¶
A short description of the profile, shown in the profile list. Pango Markup can be used here to provide styling to the text (e.g. italicized words).
- /profiles/<profile key>/description¶
A longer description, shown below the name in the profile list. Pango Markup can be used here to provide styling to the text (e.g. bold or italicized words).
- /profiles/<profile key>/icon¶
A image shown next to the name in the profile list. We recommend using SVG files, but if not, the icon should be at least 22×22. Paths can be absolute or relative
/opt/thinlinc/share/tl-select-profile. It is also possible to specify an icon name in accordance with the icon naming specification.
- /profiles/<profile key>/screenshot¶
A image with aspect ratio 4:3, shown in the profile list. Resolutions of 640×480 or 800×600 works well. Paths can be absolute or relative
- /profiles/<profile key>/cmdline¶
The command to execute if this profile has been chosen.
xdg_sessionis set then the environment variable XDG_EXEC will be set to the original command line from the system desktop session configuration.
- /profiles/<profile key>/testcmd¶
A shell expression or command that is executed to determine if this profile should be visible or not. A non-zero return code causes the entry to be hidden. If this field is empty or missing then the entry will always be shown.
xdg_sessionis set then the environment variable XDG_TRY_EXEC will be set to the expected binary from the system desktop session configuration. Note that this value differs in behaviour from
testcmd. XDG_TRY_EXEC should only name a executable binary in PATH , whilst
testcmdwill be executed and its return code inspected.