[Epoptes] [Bug 1018498] Re: Ensure that epoptes-client is actually booted to ltsp before setting LTSP_FATCLIENT=True
Fix released in Epoptes 0.5.4. http://bazaar.launchpad.net/~epoptes/epoptes/trunk/revision/312 ** Changed in: epoptes Importance: Undecided = Low ** Changed in: epoptes Status: New = Fix Released -- You received this bug notification because you are a member of Epoptes Developers, which is the registrant for Epoptes. https://bugs.launchpad.net/bugs/1018498 Title: Ensure that epoptes-client is actually booted to ltsp before setting LTSP_FATCLIENT=True Status in Epoptes: Fix Released Status in “epoptes” package in Ubuntu: Fix Released Status in “epoptes” source package in Precise: In Progress Status in “epoptes” source package in Quantal: Fix Released 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. To manage notifications about this bug go to: https://bugs.launchpad.net/epoptes/+bug/1018498/+subscriptions -- Mailing list: https://launchpad.net/~epoptes Post to : epoptes@lists.launchpad.net Unsubscribe : https://launchpad.net/~epoptes More help : https://help.launchpad.net/ListHelp
[Epoptes] [Bug 1018498] [NEW] Ensure that epoptes-client is actually booted to ltsp before setting LTSP_FATCLIENT=True
Public bug reported: 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. ** Affects: epoptes Importance: Low Status: Fix Released ** Affects: epoptes (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: epoptes (Ubuntu Precise) Importance: Undecided Assignee: Stéphane Graber (stgraber) Status: In Progress ** Affects: epoptes (Ubuntu Quantal) Importance: Undecided Status: Fix Released -- You received this bug notification because you are a member of Epoptes Developers, which is the registrant for Epoptes. https://bugs.launchpad.net/bugs/1018498 Title: Ensure that epoptes-client is actually booted to ltsp before setting LTSP_FATCLIENT=True Status in Epoptes: Fix Released Status in “epoptes” package in Ubuntu: Fix Released Status in “epoptes” source package in Precise: In Progress Status in “epoptes” source package in Quantal: Fix Released 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. To manage notifications about this bug go to: https://bugs.launchpad.net/epoptes/+bug/1018498/+subscriptions -- Mailing list: https://launchpad.net/~epoptes Post to : epoptes@lists.launchpad.net Unsubscribe : https://launchpad.net/~epoptes More help : https://help.launchpad.net/ListHelp
[Epoptes] [Bug 1018498] Re: Ensure that epoptes-client is actually booted to ltsp before setting LTSP_FATCLIENT=True
** Also affects: epoptes (Ubuntu) Importance: Undecided Status: New ** Also affects: epoptes (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: epoptes (Ubuntu Quantal) Importance: Undecided Status: New ** Changed in: epoptes (Ubuntu Quantal) Status: New = Fix Released ** Changed in: epoptes (Ubuntu Precise) Status: New = In Progress ** Changed in: epoptes (Ubuntu Precise) Assignee: (unassigned) = Stéphane Graber (stgraber) -- You received this bug notification because you are a member of Epoptes Developers, which is the registrant for Epoptes. https://bugs.launchpad.net/bugs/1018498 Title: Ensure that epoptes-client is actually booted to ltsp before setting LTSP_FATCLIENT=True Status in Epoptes: Fix Released Status in “epoptes” package in Ubuntu: Fix Released Status in “epoptes” source package in Precise: In Progress Status in “epoptes” source package in Quantal: Fix Released 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. To manage notifications about this bug go to: https://bugs.launchpad.net/epoptes/+bug/1018498/+subscriptions -- Mailing list: https://launchpad.net/~epoptes Post to : epoptes@lists.launchpad.net Unsubscribe : https://launchpad.net/~epoptes More help : https://help.launchpad.net/ListHelp
[Epoptes] [Bug 943598] Re: Twisted/GTK programs don't close properly on Ubuntu 12.04
*** This bug is a duplicate of bug 935756 *** https://bugs.launchpad.net/bugs/935756 ** Also affects: epoptes (Ubuntu) Importance: Undecided Status: New ** Also affects: twisted (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: epoptes (Ubuntu Precise) Importance: Undecided Status: New ** No longer affects: twisted (Ubuntu Precise) ** Changed in: epoptes (Ubuntu Precise) Status: New = In Progress ** Changed in: epoptes (Ubuntu Precise) Assignee: (unassigned) = Stéphane Graber (stgraber) -- You received this bug notification because you are a member of Epoptes Developers, which is subscribed to epoptes in Ubuntu. https://bugs.launchpad.net/bugs/943598 Title: Twisted/GTK programs don't close properly on Ubuntu 12.04 Status in Twisted: New Status in “epoptes” package in Ubuntu: New Status in “twisted” package in Ubuntu: New Status in “epoptes” source package in Precise: In Progress Bug description: I've been experiencing this with our www.epoptes.org application, but I've been able to reproduce the problem with http://twistedmatrix.com/documents/current/core/examples/pbgtk2.py too. I.e. when I run one of those apps from a console, and then close the application window, the window does close, but my console prompt doesn't return. Sometimes the app closes after 20-30 seconds, sometimes it just sits there forever waiting. An strace tells me it's waiting at some poll() call. The same programs run fine in previous versions of Ubuntu. Also, if I put a `reactor.crash()` just before `reactor.stop()`, then those programs terminate immediately. To manage notifications about this bug go to: https://bugs.launchpad.net/twisted/+bug/943598/+subscriptions -- Mailing list: https://launchpad.net/~epoptes Post to : epoptes@lists.launchpad.net Unsubscribe : https://launchpad.net/~epoptes More help : https://help.launchpad.net/ListHelp
[Epoptes] [Bug 1013808] Re: Assist student stops working after a while
** Description changed: When doing the following: 1) Assist student 2) Close VNC 3) Broadcast teacher 4) Stop broadcasts 5) Assist student ...then Assist student in (5) doesn't work. + + == SRU == + + [rational] + A bad variable reuse in the code leads to bad port numbers breaking the Assist student function. + + [test case] + 1) Assist student + 2) Close VNC + 3) Broadcast teacher + 4) Stop broadcasts + 5) Assist student + + 5) is currently failing, post-SRU, it works + + [regression potential] + Very limited, the diff is easy to read and it's an obvious mistake that's been solved. -- You received this bug notification because you are a member of Epoptes Developers, which is the registrant for Epoptes. https://bugs.launchpad.net/bugs/1013808 Title: Assist student stops working after a while Status in Epoptes: Fix Committed Status in “epoptes” package in Ubuntu: Fix Released Status in “epoptes” source package in Precise: In Progress Status in “epoptes” source package in Quantal: Fix Released Bug description: When doing the following: 1) Assist student 2) Close VNC 3) Broadcast teacher 4) Stop broadcasts 5) Assist student ...then Assist student in (5) doesn't work. == SRU == [rational] A bad variable reuse in the code leads to bad port numbers breaking the Assist student function. [test case] 1) Assist student 2) Close VNC 3) Broadcast teacher 4) Stop broadcasts 5) Assist student 5) is currently failing, post-SRU, it works [regression potential] Very limited, the diff is easy to read and it's an obvious mistake that's been solved. To manage notifications about this bug go to: https://bugs.launchpad.net/epoptes/+bug/1013808/+subscriptions -- Mailing list: https://launchpad.net/~epoptes Post to : epoptes@lists.launchpad.net Unsubscribe : https://launchpad.net/~epoptes More help : https://help.launchpad.net/ListHelp
[Epoptes] [Bug 1015239] Re: Incorrect fullscreen option for vncviewer command line?
Fix released in Epoptes 0.5.6.
** Changed in: epoptes
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Epoptes
Developers, which is the registrant for Epoptes.
https://bugs.launchpad.net/bugs/1015239
Title:
Incorrect fullscreen option for vncviewer command line?
Status in Epoptes:
Fix Released
Bug description:
In my lab, Epoptes doesn't broadcasts correctly in fullscreen mode: it
always launches VNC viewer in windowed mode.
Investigating the problem, I've found that script /usr/share/epoptes
/client-functions could have an error in receive_broadcast() function.
Currently, next to line 260, there are scructures like
${3:+[Ff]ull[Ss]creen (...)}
when the correct should be
${3:+-[Ff]ull[Ss]creen (...)}
with an hyphen right after +.
To manage notifications about this bug go to:
https://bugs.launchpad.net/epoptes/+bug/1015239/+subscriptions
--
Mailing list: https://launchpad.net/~epoptes
Post to : epoptes@lists.launchpad.net
Unsubscribe : https://launchpad.net/~epoptes
More help : https://help.launchpad.net/ListHelp
