** 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/889672
Title:
logoff , reboot not working on standalone lxde
Status in Epoptes:
** Changed in: epoptes
Importance: Undecided => Wishlist
** Changed in: epoptes
Status: New => Confirmed
--
You received this bug notification because you are a member of Epoptes
Developers, which is the registrant for Epoptes.
https://bugs.launchpad.net/bugs/889671
Title:
show scre
>From http://www.epoptes.org/installation:
"""
After the installation you need to add some users to group "epoptes" (or use
another group as mentioned in the Configuration section below). These users
will be allowed to launch the GUI and control clients:
gpasswd -a username epoptes
Users that a
Yannis, the Incomplete bug status means that the developer is asking the bug
reporter for more info.
And if the reporter doesn't provide that info for some time, then the bug
automatically expires.
In Greek: το Incomplete σημαίνει ότι εγώ ρωτάω εσένα για περισσότερες
πληροφορίες, και αν δεν τις
Hi Yannis,
If I understood correctly, you want a menu item in Epoptes, that would say e.g.
"Restore preferred screen resolution".
And in the help file, we'd say "this menu restores the screen resolution after
other programs, not related to epoptes, change the resolution, and then crash".
I think
Question #181707 on Epoptes changed:
https://answers.launchpad.net/epoptes/+question/181707
Alkis Georgopoulos posted a new comment:
Mike sorry we haven't seen your question, I've now put "Epoptes
developers" as an "Answers contact", so we'll get notified for
Question #186013 on Epoptes changed:
https://answers.launchpad.net/epoptes/+question/186013
Alkis Georgopoulos proposed the following answer:
I reverted the change:
http://bazaar.launchpad.net/~epoptes/epoptes/trunk/revision/170#po/nl.po
I hope launchpad is smart enough to keep the translator
Question #187692 on Epoptes changed:
https://answers.launchpad.net/epoptes/+question/187692
Status: Open => Answered
Alkis Georgopoulos proposed the following answer:
Hi Jori,
sorry for the late response, I didn't get a notification for this
question.
I wrote a wiki page about it
> New connection from 192.168.0.223:36473
> Disconnect from 192.168.0.223:36473
I think the problem is because you have an old epoptes-client version
installed in your chroot, or you don't have an up to date certificate.
Please try the following:
sudo chroot /opt/ltsp/i386 dpkg-query -W epoptes-c
Question #188754 on Epoptes changed:
https://answers.launchpad.net/epoptes/+question/188754
Status: Open => Needs information
Alkis Georgopoulos requested more information:
Jori, try `ltsp-remoteapps xterm` first, and then launch epoptes inside that
xterm.
Then run /usr/sbin/epoptes-cli
Question #188754 on Epoptes changed:
https://answers.launchpad.net/epoptes/+question/188754
Status: Open => Needs information
Alkis Georgopoulos requested more information:
Jori, let's talk a bit about the last paragraph of your initial
question:
"Additionally anybody is welc
Question #188754 on Epoptes changed:
https://answers.launchpad.net/epoptes/+question/188754
Alkis Georgopoulos posted a new comment:
Also note that it may be easier to find us in IRC for some real-time
troubleshooting. You can find a link for the IRC channel in the Epoptes
Help menu.
--
You
Question #188754 on Epoptes changed:
https://answers.launchpad.net/epoptes/+question/188754
Status: Open => Needs information
Alkis Georgopoulos requested more information:
Jori, the previous output you pasted from `ltsp-remoteapps xterm; epoptes`, had
problems because of the certific
Question #188754 on Epoptes changed:
https://answers.launchpad.net/epoptes/+question/188754
Alkis Georgopoulos posted a new comment:
When a fat client boots, you see the blue fat icon. This connection is started
from /opt/ltsp/i386/etc/network/if-up.d/epoptes-client.
When a user logs in, you
hidden, so all
translations for it were already available in launchpad and are included
in the 0.4.4 version.
Please allow syncing it from Debian. Complete changelog entry:
epoptes (0.4.4-1) unstable; urgency=low
[ Alkis Georgopoulos ]
* screenshot: exit cleanly when X isn't avai
Question #189742 on Epoptes changed:
https://answers.launchpad.net/epoptes/+question/189742
Status: Open => Needs information
Alkis Georgopoulos requested more information:
Hi Thomas,
Press Alt+F2 and type gnome-terminal, to open a console. This makes it easy to
give us precise feedb
rgency=low
[ Alkis Georgopoulos ]
* screenshot: exit cleanly when X isn't available.
* Handle late connectionLost events better.
* Replace the View menu with the Labels menu.
* Ability to show real names instead of usernames.
* Don't use epoptes-client.init on LTS
Question #189742 on Epoptes changed:
https://answers.launchpad.net/epoptes/+question/189742
Status: Needs information => Answered
Alkis Georgopoulos proposed the following answer:
First of all, if you do this:
1) login as trichards38 and open epoptes
2) login as _another_ user from anot
Karol, I still believe it's the same problem you had previously, i.e. a wrong
epoptes certificate in your chroot.
Please issue the following commands in your LTSP server and paste their output
here:
sudo mount -o loop /opt/ltsp/images/i386.img /mnt
md5sum /etc/epoptes/server.crt
md5sum /opt/ltsp
For each LTSP client, there are 2 epoptes-client processes running:
* One runs as root on the thin client, and uses the certificate of the chroot,
which is wrong. This is the one that shows the little green monitor thumbnails.
* One runs as user from inside the session, and uses the certificate
Karol, what's the output of this command?
grep -v ^# /opt/ltsp/i386/etc/default/epoptes-client
Also, it might be easier to continue the troubleshooting online, if you
want go to the "Help → Live chat (IRC)" menu in Epoptes and try to find
us in IRC.
--
You received this bug notification because
problem, epoptes-client should still be
smart enough not to time out.
It will be fixed in the next version.
** Changed in: epoptes
Importance: Undecided => Low
** Changed in: epoptes
Status: Incomplete => Triaged
** Changed in: epoptes
Assignee: (unassigned) => Alkis Geo
signee: (unassigned) => Alkis Georgopoulos (alkisg)
--
You received this bug notification because you are a member of Epoptes
Developers, which is the registrant for Epoptes.
https://bugs.launchpad.net/bugs/950720
Title:
Epoptes doesn't support XDMCP
Status in Epoptes:
Fix Committed
Bug desc
Bug #940114 status changed in Epoptes:
Confirmed => Fix Released
https://bugs.launchpad.net/epoptes/+bug/940114
"Epoptes crashes when a client with an invalid server's certificate connects"
This bug is linked to #188754.
(solved) cannot view or support epoptes clients
https://answers.launchp
Fix committed in
http://bazaar.launchpad.net/~epoptes/epoptes/trunk/revision/225
** Changed in: epoptes
Status: Triaged => Fix Committed
** Changed in: epoptes
Assignee: (unassigned) => Alkis Georgopoulos (alkisg)
--
You received this bug notification because you are a mem
This was fixed in epoptes 0.4.4.
** Changed in: epoptes
Status: Confirmed => 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/940114
Title:
Epoptes crashes when a clie
Fix committed in
http://bazaar.launchpad.net/~epoptes/epoptes/trunk/revision/230
** Changed in: epoptes
Status: Confirmed => Fix Committed
** Changed in: epoptes
Assignee: Fotis Tsamis (phantomas) => Alkis Georgopoulos (alkisg)
--
You received this bug notification because y
mitted
** Changed in: epoptes
Assignee: (unassigned) => Alkis Georgopoulos (alkisg)
--
You received this bug notification because you are a member of Epoptes
Developers, which is the registrant for Epoptes.
https://bugs.launchpad.net/bugs/953521
Title:
mute/unmute causes "not f
** Also affects: epoptes
Importance: Undecided
Status: New
** No longer affects: epoptes (Ubuntu)
--
You received this bug notification because you are a member of Epoptes
Developers, which is the registrant for Epoptes.
https://bugs.launchpad.net/bugs/953501
Title:
/var/run/epoptes
In the past I tried adding an umask() call to epoptesd.py:
os.umask(007)
guiService = internet.UNIXServer(
"%s/epoptes.socket" % config.system['DIR'],
guiplex.GUIFactory())
There seems to be a twisted bug somewhere though and this doesn't work as
expected.
I think that's somehow related to the specific VM technology that you use,
vagrantc also mentioned something about it but I could never reproduce it with
VirtualBox.
What VM and which virtual graphics driver are you using? Is your color depth 24
or 32? Does it happen with other color depths?
If
t; Fix Committed
** Changed in: epoptes
Assignee: (unassigned) => Alkis Georgopoulos (alkisg)
--
You received this bug notification because you are a member of Epoptes
Developers, which is the registrant for Epoptes.
https://bugs.launchpad.net/bugs/953493
Title:
Missing epoptes(8) m
Thanks, fixed in
http://bazaar.launchpad.net/~epoptes/epoptes/trunk/revision/233
** Changed in: epoptes
Importance: Undecided => Wishlist
** Changed in: epoptes
Status: New => Fix Committed
** Changed in: epoptes
Assignee: (unassigned) => Alkis Georgopoulos (alkisg)
The problem is explained in http://www.karlrunge.com/x11vnc/faq.html
#faq-24bpp
xvnc4viewer crashes when the client display is configured at 24 bpp.
A workaround for users is to use another color mode, e.g. X_COLOR_DEPTH=16 if
using LTSP.
For KVM guests, -vga vmware could also be used.
A workar
at least fixed so that it produces a
warning instead of a segmentation fault.
* We'll document the problem in the epoptes website.
** Changed in: epoptes
Status: New => In Progress
** Changed in: epoptes
Assignee: (unassigned) => Alkis Georgopoulos (alkisg)
--
You r
For epoptes, fixed in
http://bazaar.launchpad.net/~epoptes/epoptes/trunk/revision/234.
For xvnc4viewer the bug should remain open until at least the
segmentation fault is fixed.
** Changed in: epoptes
Status: In Progress => Fix Committed
--
You received this bug notification because you
Public bug reported:
Zenity's notifications don't show up in gnome-fallback session, and probably in
others too.
And the connection progress isn't shown, and the method to terminate isn't very
intuitive.
It'd look nicer if the remote support dialog was self-contained, showing
the connection pro
Thanks, fixed in
http://bazaar.launchpad.net/~epoptes/epoptes/trunk/revision/243.
** Changed in: epoptes
Importance: Undecided => Medium
** Changed in: epoptes
Status: New => Fix Committed
** Changed in: epoptes
Assignee: (unassigned) => Alkis Georgopoulos (alkisg)
Fix committed in
http://bazaar.launchpad.net/~epoptes/epoptes/trunk/revision/244.
** Summary changed:
- can't shutdown ltsp client computers if no one is logged in on them
+ Epoptes-clients disconnect if DNS is misconfigured
** Changed in: epoptes
Status: Triaged => Fix Committed
--
You
Fix committed in
http://bazaar.launchpad.net/~epoptes/epoptes/trunk/revision/258
** Visibility changed to: Public
** Changed in: epoptes
Importance: Undecided => Low
** Changed in: epoptes
Status: Confirmed => Fix Committed
** Changed in: epoptes
Assignee: (unassigned) =&
Question #188754 on Epoptes changed:
https://answers.launchpad.net/epoptes/+question/188754
Status: Open => Answered
Alkis Georgopoulos changed the question status:
The problem was solved, marking the question as "answered".
--
You received this question notification beca
Thank you Yuri, fix committed in
http://bazaar.launchpad.net/~epoptes/epoptes/trunk/revision/264
** Changed in: epoptes
Importance: Undecided => Low
** Changed in: epoptes
Status: New => Fix Committed
** Changed in: epoptes
Assignee: (unassigned) => Alkis Georgopoulo
Fix released in Epoptes 0.5.0.
** 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/961907
Title:
Minor typo in remote-assi
Fix released in Epoptes 0.5.0.
** 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/955452
Title:
Stop using zenity for rem
Fix released in Epoptes 0.5.0.
** 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/954441
Title:
screenshot crashed with I
Fix released in Epoptes 0.5.0.
** 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/953521
Title:
mute/unmute causes "not f
Fix released in Epoptes 0.5.0.
** 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/954076
Title:
SSL certificate validity
Fix released in Epoptes 0.5.0.
** 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/953493
Title:
Missing epoptes(8) manpag
Fix released in Epoptes 0.5.0.
** 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/950720
Title:
Epoptes doesn't support X
Fix released in Epoptes 0.5.0.
** 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/949055
Title:
Epoptes-clients disconnec
Fix released in Epoptes 0.5.0.
** 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/937820
Title:
Incorrect IP for x11vnc -
Fix released in Epoptes 0.5.0.
** 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/889669
Title:
remote vnc on login scree
Fix released in Epoptes 0.5.0.
** 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/953512
Title:
xvnc4viewer crashes with
*** This bug is a duplicate of bug 880774 ***
https://bugs.launchpad.net/bugs/880774
It would be a security vulnerability only if by default, without epoptes-client
installed, all machines were locked. :)
It's a duplicate of LP bug #880774, marking as such...
** This bug has been marked a d
Question #191794 on Epoptes changed:
https://answers.launchpad.net/epoptes/+question/191794
Status: Open => Answered
Alkis Georgopoulos proposed the following answer:
The upstream Epoptes developers are using Debian and Ubuntu.
We do want to support any and all distributions, but we ca
tus: New => Confirmed
** Changed in: epoptes
Assignee: (unassigned) => Alkis Georgopoulos (alkisg)
** Summary changed:
- remote assistance in login screen, not working for debian/lxde
+ Assist user not working in Qimo login screen
--
You received this bug notification because you are a mem
Fix committed in
http://bazaar.launchpad.net/~epoptes/epoptes/trunk/revision/274.
** Changed in: epoptes
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Epoptes
Developers, which is the registrant for Epoptes.
https://bugs.launchpad.net
We wouldn't want to waste bandwidth or CPU to get screenshots every 5 seconds
for clients idling in the login screen.
It would be nice to get only one.
But that's rather complex, did the client reach the login screen or is it
showing the xorg black initialization screen? Does the client have X at
> Would be great if a option to add computer by their IP address should
be available.
Epoptes uses reverse connections, so it's the clients that connect to the
server, not the server to the clients like in iTalc.
So there's no need for discovery or for manually adding clients, it should all
be d
** 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/966060
Title:
Assist user not working in debian/lxde login screen
Stat
optes (Ubuntu)
Importance: Undecided => Low
** Changed in: epoptes (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: epoptes (Ubuntu)
Assignee: (unassigned) => Alkis Georgopoulos (alkisg)
--
You received this bug notification because you are a member of Epoptes
Develo
Should also check for the new ltsp-common-functions names, while
preserving compatibility with older LTSP versions.
--
You received this bug notification because you are a member of Epoptes
Developers, which is the registrant for Epoptes.
https://bugs.launchpad.net/bugs/975784
Title:
Epoptes c
Public bug reported:
Should check /proc/cmdline for ltsp instead.
** Affects: epoptes
Importance: Low
Assignee: Alkis Georgopoulos (alkisg)
Status: In Progress
--
You received this bug notification because you are a member of Epoptes
Developers, which is the registrant for
Fix committed in
http://bazaar.launchpad.net/~epoptes/epoptes/trunk/revision/283.
** Changed in: epoptes (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Epoptes
Developers, which is subscribed to epoptes in Ubuntu.
https://bugs
Fix committed in
http://bazaar.launchpad.net/~epoptes/epoptes/trunk/revision/284.
** Changed in: epoptes
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Epoptes
Developers, which is the registrant for Epoptes.
https://bugs.launchpad.n
x11vnc -grabkbd -grabptr can be used for that, in /usr/share/epoptes
/client-functions:
get_assisted() {
background x11vnc -noshm -24to32 -grabkbd -grabptr -connect_or_exit
"$SERVER:$1"
}
But it won't be committed upstream now, because we want to refrain from
adding new features to epoptes f
Fix released in epoptes 0.5.3-1.
** Changed in: epoptes (Ubuntu)
Status: Fix Committed => Fix Released
--
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/975433
Title:
package e
Fix released in epoptes 0.5.3-1.
** 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/975784
Title:
Epoptes checks for depr
** Visibility changed to: Public
--
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/977049
Title:
epoptes crashed with AttributeError in __init__(): 'module' object has
no attribute '
atus: New => Incomplete
** Changed in: epoptes
Assignee: (unassigned) => Alkis Georgopoulos (alkisg)
--
You received this bug notification because you are a member of Epoptes
Developers, which is the registrant for Epoptes.
https://bugs.launchpad.net/bugs/978050
Title:
Broad
Don't use "sudo" to run epoptes.
Either run it with plain "epoptes", or from the Gnome or other DE menu.
It shouldn't crash though, so marking as Confirmed...
** Also affects: epoptes
Importance: Undecided
Status: New
** No longer affects: epoptes (Ubuntu)
** Changed in: epoptes
Im
*** This bug is a duplicate of bug 975433 ***
https://bugs.launchpad.net/bugs/975433
** This bug has been marked a duplicate of bug 975433
package epoptes 0.5.2-1 failed to install/upgrade: subprocess installed
post-installation script returned error exit status 1
--
You received this bu
*** This bug is a duplicate of bug 975433 ***
https://bugs.launchpad.net/bugs/975433
** This bug has been marked a duplicate of bug 975433
package epoptes 0.5.2-1 failed to install/upgrade: subprocess installed
post-installation script returned error exit status 1
--
You received this bu
1) I think that the "seat" part of a multiseat system can be merged into
the "computer" part as far as the GUI is concerned. So I don't think
there's need to add extra label options, only to put the seat
name/number as a suffix after the computer name.
2) Each of those root terminals has access to
> The most common way to identify a seat in a multiseat network is by
its hostname/IP and by the value of DISPLAY variable for the Xorg
instance running in that seat.
Unfortunately it isn't that simple; thin clients also run server
sessions with different DISPLAYs, and even a simple ssh -X gives a
*** This bug is a duplicate of bug 975433 ***
https://bugs.launchpad.net/bugs/975433
Angutivik, you reported this bug 3 times, and I've been marking it as a
duplicate of LP bug #975433.
In other words, this bug has been solved, and to get around it, you need to run:
sudo service epoptes stop
Question #194873 on Epoptes changed:
https://answers.launchpad.net/epoptes/+question/194873
Status: Open => Invalid
Alkis Georgopoulos changed the question status:
This question is completely unrelated to Epoptes, as Epoptes doesn't
restrict or do anything else about X/Gnome screen
Question #194924 on Epoptes changed:
https://answers.launchpad.net/epoptes/+question/194924
Status: Open => Answered
Alkis Georgopoulos proposed the following answer:
Hi Theodotos,
> Is there such a feature in epoptes?
No.
> Any plan to add such feature if not?
http://www.ep
Question #195888 on Epoptes changed:
https://answers.launchpad.net/epoptes/+question/195888
Status: Open => Answered
Alkis Georgopoulos proposed the following answer:
Epoptes-client uses reverse connections, so currently each client can
only be controller by a single server.
So, y
Question #195888 on Epoptes changed:
https://answers.launchpad.net/epoptes/+question/195888
Alkis Georgopoulos proposed the following answer:
> b) create an /opt/ltsp/i386/usr/local/usr/sbin/epoptes-client wrapper,
with the following contents:
Ouch, /etc/xdg/autostart/epoptes-client.desk
Question #195888 on Epoptes changed:
https://answers.launchpad.net/epoptes/+question/195888
Alkis Georgopoulos posted a new comment:
> The only glitch is that screen captures and user name labels are not
appearing on the Epoptes main screen.
Edit /etc/default/epoptes-client on the LTSP server
Question #197285 on Epoptes changed:
https://answers.launchpad.net/epoptes/+question/197285
Status: Open => Answered
Alkis Georgopoulos proposed the following answer:
Hi Oscar,
Since openSUSE doesn't have epoptes packages (yet?), you basically need to:
1) Install epoptes in your lap
Question #197285 on Epoptes changed:
https://answers.launchpad.net/epoptes/+question/197285
Status: Open => Answered
Alkis Georgopoulos proposed the following answer:
You can't use the MAC address, epoptes uses TCP/IP and doesn't (yet?) have any
ARP related code.
You should al
Question #197285 on Epoptes changed:
https://answers.launchpad.net/epoptes/+question/197285
Status: Open => Answered
Alkis Georgopoulos proposed the following answer:
http://avahi.org :)
You don't need to read many things though, just try to ping a client by putting
".loc
Question #197285 on Epoptes changed:
https://answers.launchpad.net/epoptes/+question/197285
Alkis Georgopoulos posted a new comment:
> I'd like to say thanks to all the people that works on Gofris.
> Gofris is great...
Maybe you meant "epoptes" there? :)
You're welc
Ethtool does provide an if-up script to restore settings (including WOL), so
you don't need to create your own.
Also some NIC modules default to WOL=on, and others provide an option for that.
We don't want epoptes-client to set hardware settings though, as (1) not
all cards support ethtool and (2
Epoptes has a ping mechanism to detect and remove dead clients, so are you sure
that those clients are really dead?
E.g. if you're using LTSP, do you see epoptes-client still running for those
users on the LTSP server?
** Changed in: epoptes
Status: New => Incomplete
--
You received thi
When you see a dead client, could you pull its network plug and wait for
the 10 sec epoptes ping timeout to occur, to verify that the problem
isn't e.g. another user's epoptes-client process running on that same
client?
--
You received this bug notification because you are a member of Epoptes
Dev
Η έκδοση 12.04 των sch-scripts θα έχει μόνο μία επιλογή για δημιουργία
εικονικού δίσκου (και για thin και για fat clients).
** Changed in: sch-scripts
Status: New => Invalid
--
You received this bug notification because you are a member of Epoptes
Developers, which is the registrant for E
When epoptes was first developed, it targeted LTSP netbooted computer
labs, where the clients would crash anyway if the network connection was
ever lost. So the reconnection feature was skipped in order to minimize
RAM usage for thin clients.
It will be implemented in a future version, since now e
Question #200174 on Epoptes changed:
https://answers.launchpad.net/epoptes/+question/200174
Status: Open => Needs information
Alkis Georgopoulos requested more information:
Hi, log in on a thin client, open a gnome-terminal, run
/usr/sbin/epoptes-client
and paste the output here.
--
Question #200174 on Epoptes changed:
https://answers.launchpad.net/epoptes/+question/200174
Status: Open => Needs information
Alkis Georgopoulos requested more information:
And after you do that you don't see its thumbnails on epoptes and no
error messages in the epoptes-client outpu
Question #200174 on Epoptes changed:
https://answers.launchpad.net/epoptes/+question/200174
Alkis Georgopoulos requested more information:
Also, when you say that you've upgraded to 5.4.0, what was your previous
version? 5.3.0? Because the changelog from 5.3.0 to 5.4.0 mostly
involves transl
Question #200174 on Epoptes changed:
https://answers.launchpad.net/epoptes/+question/200174
Alkis Georgopoulos posted a new comment:
Maybe you need to update your chroot, if it still has such an old version. You
can also come to the #ltsp IRC channel for online troubleshooting:
http
*** This bug is a duplicate of bug 977049 ***
https://bugs.launchpad.net/bugs/977049
The system epoptes-client service does run as root from
/etc/network/if-up.d/epoptes-client, so you can control the clients before
logon.
If you're using a fresh epoptes version and it's correctly installed
Public bug reported:
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.
** Affects: epoptes
Importance: Medium
Assignee: Alkis Georgopoulos (alkisg)
Status
Fix committed in
http://bazaar.launchpad.net/~epoptes/epoptes/trunk/revision/318
** Changed in: epoptes
Importance: Undecided => Medium
** Changed in: epoptes
Status: New => Fix Committed
** Changed in: epoptes
Assignee: (unassigned) => Alkis Georgopoulos (alkisg)
Thank you, fix committed in
http://bazaar.launchpad.net/~epoptes/epoptes/trunk/revision/322.
** Changed in: epoptes
Importance: Undecided => Low
** Changed in: epoptes
Status: New => Fix Committed
** Changed in: epoptes
Assignee: (unassigned) => Alkis Georgopoulo
> First we tried to start the client in/etc/kde4/kdm/Xsession (with root
rights), which fails. The client will now started on users login with
user rights (/usr/bin/startkde).
You shouldn't start epoptes-client manually, please revert your changes and
re-test.
There are two epoptes-client instanc
Could you open one gnome-terminal for the "teacher" and one the "student",
and paste here the output of this command for both of them?
setxkbmap -print
** Changed in: epoptes
Status: New => Incomplete
--
You received this bug notification because you are a member of Epoptes
Developers, w
1 - 100 of 365 matches
Mail list logo
