Bug 1425 - Simplify "ThinLincification" of a Linux system - perhaps via tl-setup
Summary: Simplify "ThinLincification" of a Linux system - perhaps via tl-setup
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Server Installer (show other bugs)
Version: 1.4.0
Hardware: PC Linux
: P2 Enhancement
Target Milestone: 4.15.0
Assignee: Bugzilla mail exporter
Depends on:
Reported: 2005-07-07 09:28 CEST by Peter Åstrand
Modified: 2022-04-05 13:33 CEST (History)
0 users

See Also:
Acceptance Criteria:


Description Peter Åstrand cendio 2005-07-07 09:28:31 CEST
Each one installs a new ThinLinc system, there's a certain amount of things that
needs to be done to tune the system for ThinLinc. This includes:

* Set a default, plain background color for all users 

* Disable the screensavers for all users

* Fix the KDE aRts error message stuff

All this is described in the UG FAQ. We could create some kind of tool that
automates these steps. It would be possible to add this functionality to the
tl-setup tool. It already allows you to select different "tasks" to perform, for
example setup the CUPS queues and configure Webmin. Doing this "KDE" tuning
could be one or more new tasks. 

One drawback with implementing this is that this quite little to do with
ThinLinc. It will fail on systems with non-standard KDE installations, such as
Debian and Solaris.
Comment 1 Peter Åstrand cendio 2005-11-09 13:13:50 CET
The first two things can be fixed with kiosktool etc. That leaves us with only
the arts message.
Comment 2 Peter Åstrand cendio 2016-08-10 16:30:50 CEST
Bug 5584 is another example of when it could be useful to offer the admin to tweak the system. This could be in a form of a tl-setup page:

Adapt System for Remote Desktop Sessions

[x] Disable "PackageKit" authentication dialogs
[x] Disable "colord" authentication dialogs
Comment 3 Pierre Ossman cendio 2022-04-05 13:33:37 CEST
This is outside our current scope for the product. We try to document serious issues under platform specific notes, and other things can be discussed in our community forums.

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