Ensure that epoptes-client is actually booted to ltsp before setting LTSP_FATCLIENT=True
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Epoptes |
Fix Released
|
Low
|
Unassigned | ||
epoptes (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Precise |
Fix Released
|
Undecided
|
Stéphane Graber | ||
Quantal |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
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.
Related branches
Changed in epoptes (Ubuntu Quantal): | |
status: | New → Fix Released |
Changed in epoptes (Ubuntu Precise): | |
status: | New → In Progress |
assignee: | nobody → Stéphane Graber (stgraber) |
description: | updated |
Fix released in Epoptes 0.5.4. bazaar. launchpad. net/~epoptes/ epoptes/ trunk/revision/ 312
http://