Bug 7811 - User will not automatically receive an updated default configuration when updating the client
Summary: User will not automatically receive an updated default configuration when upd...
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Client (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: MediumPrio
Assignee: Bugzilla mail exporter
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-12-21 14:31 CET by William Sjöblom
Modified: 2022-10-19 14:06 CEST (History)
1 user (show)

See Also:
Acceptance Criteria:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description William Sjöblom cendio 2021-12-21 14:31:32 CET 
When first starting the ThinLinc client, the configuration from that release will be written to `~/.thinlinc/tlclient.conf'. 

If we decide to change the default configuration values in the next release, the user will have to remove their `tlclient.conf' for these changes to take effect. This makes it problematic for us to roll out new configuration defaults.

One possible approach would be to consider all configuration options that are set to the default value to be unchanged by the user. When a new version is installed, the new defaults replaces the old "unchanged" default values.
Comment 1 Pierre Ossman cendio 2021-12-28 14:51:22 CET 
When changing this you should also consider what effect it has on configuration migration, as that code can trigger on the existence of variables. Removing them because they have the default value may then cause undesirable side effects.
Comment 2 Martin Östlund cendio 2022-10-19 14:06:41 CEST 
This also means that ThinLinc administrators does not have the possibility to change UPDATE_URL for their users, such use case could be that they have a customized ThinLinc client.
Note You need to log in before you can comment on or make changes to this bug.