[Bug 987726] Re: Unity doesn't start at all on a 3D capable machine instead of falling back to unity-2d as it should (because of lack of 16bit support in compiz).

[Stéphane Graber]

Tested on a fat client, confirmed that prior to the update I'd just get
an empty desktop without unity, post-upgade unity 3d starts as expected.

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ltsp in Ubuntu.
https://bugs.launchpad.net/bugs/987726

Title:
  Unity doesn't start at all on a 3D capable machine instead of falling
  back to unity-2d as it should (because of lack of 16bit support in
  compiz).

Status in “ltsp” package in Ubuntu:
  Fix Released
Status in “ltsp” source package in Precise:
  Fix Committed

Bug description:
  [rationale]
  DESKTOP_SESSION isn't properly set when using the "default" session (no parameter passed to Xsession), this leads to gconf not loading the custom unity settings, resulting in just nautilus being running.

  The fix adds an Xsession.d script to both ltsp-client-core and ltsp-
  server, this script parses the parameter of Xsession and sets
  DESKTOP_SESSION to the expected value, similar to what lightdm does on
  a regular desktop.

  [test case]
  1) Build a fat client chroot on a working LTSP system (ltsp-build-client --fat-client)
  2) Boot a 3D capable thin client
  3) Login using the default session

  3) in the past would lead to a blank screen, with the fix, you get
  unity-3d.

  [regression potential]
  As far as I can tell, DESKTOP_SESSION is only used by gconf at the moment, so if the code fails, all we should get is more gconf weirdness, though I can hardly see how it could get any worse than not getting a desktop session.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/987726/+subscriptions