** Description changed:

  Epoptes version: 0.5.3-1
  
  If one installs epoptes-client in a standalone (non-LTSP) PC which for
  some reason also has the ltsp-client package installed, then that PC is
  reported to be a fat client in the Epoptes UI, even if it was booted
  locally.
+ 
+ == SRU ==
+ [rational]
+ Epoptes reports regular workstations with ltsp-client installed as fat 
clients even though they didn't boot from LTSP.
+ 
+ [test case]
+ 1) Install epoptes
+ 2) Install ltsp-client
+ 3) Restart epoptes
+ 4) Start classroom manager on teacher computer
+ 
+ 4) should report the machine as a workstation, not a fat client
+ 
+ [regression potential]
+ The fix just adds a check for /proc/cmdline, the check while not perfect 
should match 99% of the cases where ltsp-client and epoptes are installed on a 
non-ltsp machine.
+ If this still doesn't match, then the client will be reported as a fat 
client, but overall, the logic can't be any more wrong that it's today.

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

Title:
  Ensure that epoptes-client is actually booted to ltsp before setting
  LTSP_FATCLIENT=True

To manage notifications about this bug go to:
https://bugs.launchpad.net/epoptes/+bug/1018498/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to