[Epoptes] [Merge] lp:~oiteam/epoptes/multiseat-one-root-terminal-per-host into lp:epoptes

Laércio de Sousa has proposed merging lp:~oiteam/epoptes/multiseat-one-root-terminal-per-host into lp:epoptes. Requested reviews: Epoptes Developers (epoptes) For more details, see: https://code.launchpad.net/~oiteam/epoptes/multiseat-one-root-terminal-per-host/+merge/278194 Please ingore

Re: [Epoptes] [Bug 1518140] [NEW] socat using 100% of CPU

Try to set manually the IP address of your Epoptes server in /etc/default/epoptes-client. It may be a problem related to server name resolution. Enviado através do Boxer Em 19/11/2015 11:05 PM, map7 escreveu: Public bug reported: I'm using Epoptes version 0.5.7-1 & socat

[Epoptes] [Bug 1517574] [NEW] Make socat timeout configurable in /etc/default/epoptes-client

Public bug reported: Now that a socat timeout was introduced in revision 458, I would like to propose a little suggestion: make it configurable in /etc/default /epoptes-client. Some users may want to give it a greater or smaller value, depending on their network characteristics. ** Affects:

[Epoptes] [Merge] lp:~oiteam/epoptes/respawning-timeout-configurable into lp:epoptes

Laércio de Sousa has proposed merging lp:~oiteam/epoptes/respawning-timeout-configurable into lp:epoptes. Requested reviews: Epoptes Developers (epoptes) Related bugs: Bug #1517574 in Epoptes: "Make socat timeout configurable in /etc/default/epoptes-client" https://bugs.lau

[Epoptes] [Bug 1517574] Re: Make socat timeout configurable in /etc/default/epoptes-client

** Branch linked: lp:~oiteam/epoptes/respawning-timeout-configurable -- You received this bug notification because you are a member of Epoptes Developers, which is subscribed to Epoptes. https://bugs.launchpad.net/bugs/1517574 Title: Make socat timeout configurable in

Re: [Epoptes] [Merge] lp:~oiteam/epoptes/x11vnc-wrapper-with-alt-input-grabbing into lp:epoptes

I've updated my branch since I've found an issue with the former mouse grabbing heuristic: if I disable my USB mouse with 'xinput set-prop $mouse_id "Device Enabled" 0' and try to move it locally, it's automatically re-enabled after a few seconds. Thus I'm restoring and old heuristic for mouse

[Epoptes] [Bug 1504547] Re: Provide an easy way to multicast videos

Synthesizing all options above in a server-side script, I've got the following: #!/bin/sh ADDRESS=239.255.100.100 PORT=5004 MULTICAST_BASE="rtp{dst=${ADDRESS},port=${PORT},mux=ts}" MULTICAST_LOCAL_PLAYBACK="duplicate{dst=${MULTICAST_BASE},dst=display}" ENABLE_LIVE_TRANSCODING=false

[Epoptes] [Bug 1504547] [NEW] Provide an easy way to multicast videos

Public bug reported: One task I do a lot in my lab is video multicast using VLC, but the manual setup for multicast always take me some time. I wonder if Epoptes could provide an easy way to provide such a fature (e.g. an interface to VLC to automate multicast configuration). ** Affects: epoptes

[Epoptes] [Bug 1428141] Re: Clients' local pointer movement can't be grabbed when they get assisted

** Branch linked: lp:~oiteam/epoptes/x11vnc-wrapper-with-alt-input- grabbing -- You received this bug notification because you are a member of Epoptes Developers, which is subscribed to Epoptes. https://bugs.launchpad.net/bugs/1428141 Title: Clients' local pointer movement can't be grabbed

[Epoptes] [Merge] lp:~oiteam/epoptes/x11vnc-wrapper-with-alt-input-grabbing into lp:epoptes

Laércio de Sousa has proposed merging lp:~oiteam/epoptes/x11vnc-wrapper-with-alt-input-grabbing into lp:epoptes. Requested reviews: Epoptes Developers (epoptes) Related bugs: Bug #1428141 in Epoptes: "Clients' local pointer movement can't be grabbed when they get assisted&quo

[Epoptes] [Bug 1503820] [NEW] Direct requirements for epoptes package are declared implictly as requirements for epoptes-client

Public bug reported: Currently some direct requirements (Depends/Recommends) for epoptes server-side package are declared implictly as requirements for epoptes- client, which in turn is a requirement (Recommends) for epoptes. If I remove epoptes-client from my server, these direct requirements

[Epoptes] [Bug 1503257] [NEW] Add a toolbar button in Epoptes GUI to open terminal

Public bug reported: One of the features I use the most in Epoptes is openning remote terminals (root/user). I wonder if a toolbar button could be included for that, so I don't need to open menu Execute > Open terminal > ... It could be a combo button with the following list order (my

[Epoptes] [Question #271291]: Epoptes massive notifications make GNOME Shell freeze

New question #271291 on Epoptes: https://answers.launchpad.net/epoptes/+question/271291 I'm not sure if it should be a bug report, but I've noticed that, after updating my Epoptes server to revision 435 (which has brought back my notifications), my entire GNOME Shell desktop freezes and becomes

Re: [Epoptes] [Question #271291]: Epoptes massive notifications make GNOME Shell freeze

Question #271291 on Epoptes changed: https://answers.launchpad.net/epoptes/+question/271291 Description changed to: I'm not sure if it should be a bug report, but I've noticed that, after updating my Epoptes server to revision 435 (which has brought back my notifications), my entire GNOME Shell

Re: [Epoptes] [Question #271291]: Epoptes massive notifications make GNOME Shell freeze

Question #271291 on Epoptes changed: https://answers.launchpad.net/epoptes/+question/271291 Linked to bug: #1494772 https://bugs.launchpad.net/bugs/1494772 "Epoptes massive notifications make GNOME Shell freeze" -- You received this question notification because your team Epoptes

[Epoptes] [Bug 1011482] Re: automatic reconnect of client if server went away

Hi there! Instead of hacking /usr/sbin/epoptes-client, I've written a wrapper script to be executed instead in /etc/xdg/autostart/epoptes- client.desktop. Here's the code (tested on Xubuntu 15.04): #!/bin/sh old_hostname=$(hostname) [ -x /usr/bin/nm-online ] nm-online --timeout=600 until [

Re: [Epoptes] [Bug 1439619] [NEW] epoptes not starting

Hi! I always get this error when trying to open epoptes if epoptes-server twistd daemon is not running. You can see if twistd is running using the following command: ps -FC twistd Em qui, 2 de abr de 2015 às 07:35, Yannis Tsop 1439...@bugs.launchpad.net escreveu: Public bug reported: When

[Epoptes] [Bug 1428141] [NEW] Clients' local pointer movement can't be grabbed when they get assisted

Public bug reported: Due to a x11vnc limitation, only mouse buttons, not pointer movement, can be grabbed with -grabptr command line option. So, when Epoptes server assists a client with option grabkbdptr=True, client user can still move pointer locally, which can be annoying to the teacher.

[Epoptes] [Merge] lp:~oiteam/epoptes/lock-pointer into lp:epoptes

Laércio de Sousa has proposed merging lp:~oiteam/epoptes/lock-pointer into lp:epoptes. Requested reviews: Epoptes Developers (epoptes) Related bugs: Bug #1428141 in Epoptes: Clients' local pointer movement can't be grabbed when they get assisted https://bugs.launchpad.net/epoptes/+bug

Re: [Epoptes] [Merge] lp:~oiteam/epoptes/systemd-logind-shutdown into lp:epoptes

I've found an error in my branch (a missing boolean argument for systemd-logind dbus calls). I've updated my branch and tested it in openSUSE 13.1. The shutdown/reboot via systemd-logind is now working correctly. --

[Epoptes] [Bug 1226094] [NEW] epotes-client relies on /lib/lsb/init-functions, which may not provide the desired functionality in non-Debian-based distros

Public bug reported: Current epoptes-client main script sources /lib/lsb/init-functions, which provide logging functions log_begin_msg() and log_end_msg() on Debian-based distros. However, openSUSE 12.3's /lib/lsb/init-functions doesn't provide these functions. Instead, it provides

[Epoptes] [Bug 980141] Re: some more suggestions for dealing with multiseat environments

Now that systemd-logind is coming to replace ConsoleKit in Ubuntu, we'll finally have a proper multiseat handling mechanism of which Epoptes could benefit. For example, logind provides a proper way to identify seats. Each seat receives a name of kind seat. The default seat, called seat0, is

Re: [Epoptes] [Question #208304]: How does Epoptes distinguish a LTSP thin/fat client from a standalone one

Question #208304 on Epoptes changed: https://answers.launchpad.net/epoptes/+question/208304 Status: Answered = Solved Laércio de Sousa confirmed that the question is solved: Thanks Alkis Georgopoulos, that solved my question. -- You received this question notification because you

[Epoptes] [Merge] lp:~oiteam/epoptes/auto-reconnect into lp:epoptes

Laércio de Sousa has proposed merging lp:~oiteam/epoptes/auto-reconnect into lp:epoptes. Requested reviews: Epoptes Developers (epoptes) For more details, see: https://code.launchpad.net/~oiteam/epoptes/auto-reconnect/+merge/153115 Add an auto-reconnect feature for standalone clients only

[Epoptes] [Bug 1011482] Re: automatic reconnect of client if server went away

I've just uploaded a new branch with this solution, for anyone interested. lp:~oiteam/epoptes/auto-reconnect -- You received this bug notification because you are a member of Epoptes Developers, which is subscribed to Epoptes. https://bugs.launchpad.net/bugs/1011482 Title: automatic

Re: [Epoptes] [Question #223444]: Best way to relaunch epoptes-client on server connection losses

Question #223444 on Epoptes changed: https://answers.launchpad.net/epoptes/+question/223444 Status: Answered = Solved Laércio de Sousa confirmed that the question is solved: Thanks Alkis Georgopoulos, that solved my question. -- You received this question notification because you

[Epoptes] [Bug 1011482] Re: automatic reconnect of client if server went away

Alkis, In my tests (server running Ubuntu 12.04;, clients running Ubuntu 10.04), your solution didn't work. Fortunately, I rapidly realized that socat exits with code 0 when I disconnect the server, thus I removed the !s in while clauses. Now the automatic reconnection works. Thanks a lot! --

[Epoptes] [Question #223444]: Best way to relaunch epoptes-client on server connection losses

New question #223444 on Epoptes: https://answers.launchpad.net/epoptes/+question/223444 As of version 0.5.6, Epoptes standalone clients are unable to automatically reconnect to server when connection is lost (e.g., when server reboots). While a definitive solution is to be developed, the

[Epoptes] [Merge] lp:~oiteam/epoptes/workaround-broadcasting-multiseat into lp:epoptes

Laércio de Sousa has proposed merging lp:~oiteam/epoptes/workaround-broadcasting-multiseat into lp:epoptes. Requested reviews: Epoptes Developers (epoptes) For more details, see: https://code.launchpad.net/~oiteam/epoptes/workaround-broadcasting-multiseat/+merge/131881 As discussed in https

[Epoptes] [Merge] lp:~oiteam/epoptes/remote-assist-grab-local-input into lp:epoptes

Laércio de Sousa has proposed merging lp:~oiteam/epoptes/remote-assist-grab-local-input into lp:epoptes. Requested reviews: Epoptes Developers (epoptes) For more details, see: https://code.launchpad.net/~oiteam/epoptes/remote-assist-grab-local-input/+merge/131882 As discussed in https

[Epoptes] [Question #208304]: How does Epoptes distinguish a LTSP thin/fat client from a standalone one

New question #208304 on Epoptes: https://answers.launchpad.net/epoptes/+question/208304 I'm studying Epoptes' code to learn how does it identify LTSP thin/fat clients, and standalone ones, but I'm in trouble to find the specific piece of code. Could you please tell me where can I find it?

[Epoptes] [Bug 1015239] [NEW] Incorrect fullscreen option for vncviewer command line?

Public bug reported: 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

[Epoptes] [Bug 978050] [NEW] Broadcasts not working properly in multiseat environment

Public bug reported: I have a multiseat setup in my lab, with 8 CPUs for 16 seats, using Userful Multiplier. Epoptes works very well with all seats, except for broadcasting. When I try to broadcast my server screen to all clients, sometimes it doesn't show at all, sometimes it shows in the first