Setting X_COLOR_DEPTH in lts.conf doesn't have any effect.

[Marc Gariépy]

[Impact]
When i set X_COLOR_DEPTH=24 in lts.conf it does get overwritten to to 16 bit.

[test case]
1) set X_COLOR_DEPTH=24 in lts.conf
2) boot a thin client and check if X is started with -depth 16

[regression potential]
None

[development fix]
I know this section is deprecated but it's actually relevant in this case ;)
The fix hasn't hit quantal yet because of some massive packaging rework going on with LTSP to try and bring us in sync with Debian. I can guarantee that we will have a new upstream release in quantal that will include this fix. ETA is of a couple of weeks.

we need to pull this patch from upstream trunk to fix this issue.

http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/revision/2316

[Clint Byrum (clint-fewbar)]

Hello Marc, or anyone else affected,

Accepted ltsp into precise-proposed. The package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

[Marc Gariépy (mgariepy)]

just tested the new package and everything works correctly

Thanks for the upload.

[Launchpad Janitor (janitor)]

This bug was fixed in the package ltsp - 5.3.7-0ubuntu2.1

---------------
ltsp (5.3.7-0ubuntu2.1) precise-proposed; urgency=low

  * Cherry-pick upstream bugfixes:
    - Fix ionice on OpenVZ (r2242) (LP: #1004158)
    - Fix variable name conflict for ltsp-cluster (r2303) (LP: #1008618)
    - Check X_COLOR_DEPTH before overwritting with 16bit (r2316) (LP: #1010198)
 -- Stephane Graber <email address hidden> Fri, 08 Jun 2012 10:55:10 -0400

[Alkis Georgopoulos (alkisg)]

Fix released in LTSP 5.4.5.