If you run epoptes from a fat client with ltsp-remoteapps, that means that you don't run it from a fat client but from the server.
That's why the fat client shows up in the UI.
To work around this problem 2 steps are needed:
1) The variables LTSP_CLIENT and LTSP_CLIENT_MAC need to be defined when you run epoptes, e.g.:
teacher@fatclient123:~$ ssh -XC teacher@server LTSP_CLIENT=$LTSP_CLIENT LTSP_CLIENT_MAC=$LTSP_CLIENT_MAC epoptes
2) The file /usr/lib/python2.7/dist-packages/epoptes/ui/gui.py needs to be changed to exclude the root epoptes-client connection of the fat pc:
- if (mac in self.current_macs) and (uid == self.uid):
+ if (mac in self.current_macs) and ((uid == self.uid) or (uid == 0)):
If you run epoptes from a fat client with ltsp-remoteapps, that means that you don't run it from a fat client but from the server.
That's why the fat client shows up in the UI.
To work around this problem 2 steps are needed: fatclient123: ~$ ssh -XC teacher@server LTSP_CLIENT= $LTSP_CLIENT LTSP_CLIENT_ MAC=$LTSP_ CLIENT_ MAC epoptes
1) The variables LTSP_CLIENT and LTSP_CLIENT_MAC need to be defined when you run epoptes, e.g.:
teacher@
2) The file /usr/lib/ python2. 7/dist- packages/ epoptes/ ui/gui. py needs to be changed to exclude the root epoptes-client connection of the fat pc:
- if (mac in self.current_macs) and (uid == self.uid):
+ if (mac in self.current_macs) and ((uid == self.uid) or (uid == 0)):