Bug 5059 - disabling ~/.thinlinc/xstartup shouldn't require changing xstartup.default
Summary: disabling ~/.thinlinc/xstartup shouldn't require changing xstartup.default
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: VSM Agent (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: LowPrio
Assignee: Peter Åstrand
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-01 17:05 CEST by Pierre Ossman
Modified: 2014-04-08 10:29 CEST (History)
0 users

See Also:
Acceptance Criteria:

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

Description Pierre Ossman cendio 2014-04-01 17:05:32 CEST 
Right now xsession will always run ~/.thinlinc/xstartup if it exists. It is likely though that administrators will want to be able to lock down the system so that users cannot control what gets started in their thinlinc session.
Comment 1 Pierre Ossman cendio 2014-04-08 10:29:18 CEST 
We actually have some support for this today. We mark xstartup.default as a config file and the TAG references that you can change it for exactly this use case. I'm not convinced that this is the best approach though. Proper configuration is preferable to having people change our shipped scripts.
Note You need to log in before you can comment on or make changes to this bug.