Bug 7346 - /profiles/default cannot be optimal on all systems
Summary: /profiles/default cannot be optimal on all systems
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Misc (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: 4.10.1
Assignee: Peter Åstrand
Keywords: ossman_tester, prosaic
Depends on:
Blocks: 7345
  Show dependency treegraph
Reported: 2019-05-07 11:20 CEST by Peter Åstrand
Modified: 2019-06-18 12:27 CEST (History)
0 users

See Also:
Acceptance Criteria:


Description Peter Åstrand cendio 2019-05-07 11:20:47 CEST
Our profile selection dialog currently respects the configuration variable /profiles/default. In our default profiles.hconf, we have:


Unfortunately, for example, on Ubuntu 19.04 with a typical package set, this means that the second "GNOME Desktop" option will be default rather than the first "Ubuntu Desktop". This is different from how the local display manager behaves.

It's not possible to solve this if we continue to have a "default" parameter in our shipped config files. A more generic mechanism would be to use the first available profile, based on the "order" parameter. This is actually how it works if there's no match on the "default" profile. There could still be cases where we cannot match the display manager default, but the problem would occur less often.
Two suggestions on how this bug can be solved:

1) Remove the "default" parameter from our shipped profiles.hconf


2) Remove support for the "default" parameter
Comment 2 Pierre Ossman cendio 2019-06-17 11:10:18 CEST
The core functionality seems to work well:

 * Empty default: First is selected

 * Specific default: The named profile is selected

 * Invalid default: First is selected

 * Just one valid profile: Default doesn't matter

However, tlwebadm hasn't been updated. It uses a drop down box for this field, and it doesn't have the option of leaving it blank.
Comment 4 Pierre Ossman cendio 2019-06-18 12:27:20 CEST
Works well now. Closing.

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