Re: [Epoptes] [Question #235560]: SSVNC default configuration
Question #235560 on Epoptes changed: https://answers.launchpad.net/epoptes/+question/235560 Status: Open = Answered Alkis Georgopoulos proposed the following answer: Hi François, if you can do what you want from the command line, and you cannot do it from epoptes, then it's an epoptes-related question. But if I understood you correctly, you can do what you want from the F8 menu, but not from the SSVNC command line. If so, it's an SSVNC-related question, which we cannot answer! Try contacting the SSVNC developers instead! Cheers, Alkis -- You received this question notification because you are a member of Epoptes Developers, which is an answer contact for Epoptes. -- Mailing list: https://launchpad.net/~epoptes Post to : epoptes@lists.launchpad.net Unsubscribe : https://launchpad.net/~epoptes More help : https://help.launchpad.net/ListHelp
Re: [Epoptes] [Question #235560]: SSVNC default configuration
Question #235560 on Epoptes changed: https://answers.launchpad.net/epoptes/+question/235560 Status: Answered = Open CF is still having a problem: Thanks for your answer. Yes that's right, I would like to change the default behavior, without the F8 pop-up. I'll search to find a way for changing default monitoring parameters (64 colors with highest compression possible). I leave this question opened for the moment, I'll post a solution if I found one within a few days. Thanks again. François -- You received this question notification because you are a member of Epoptes Developers, which is an answer contact for Epoptes. -- Mailing list: https://launchpad.net/~epoptes Post to : epoptes@lists.launchpad.net Unsubscribe : https://launchpad.net/~epoptes More help : https://help.launchpad.net/ListHelp
Re: [Epoptes] [Question #235680]: Thin client not registering with epoptes
Question #235680 on Epoptes changed: https://answers.launchpad.net/epoptes/+question/235680 Status: Needs information = Open David Hopkins gave more information on the question: Fotis, This is probably a silly question, but how do I start from a terminal? I'm only aware of using the init scripts with service epoptes start/stop/restart. Same for the epoptes-client. Or are you referring to the epoptes GUI? Ive pasted the output from the epoptes.log below, the output from /usr/bin/epoptes (GUI) below that. I stopped/started epoptes (service epoptes stop ; service epoptes start) 2013-09-16 07:12:33-0400 [-] Log opened. 2013-09-16 07:12:33-0400 [-] twistd 11.1.0 (/usr/bin/python 2.7.3) starting up. 2013-09-16 07:12:33-0400 [-] reactor class: twisted.internet.pollreactor.PollReactor. 2013-09-16 07:12:33-0400 [-] DelimitedBashReceiverFactory (TLS) starting on 789 2013-09-16 07:12:33-0400 [-] Starting factory epoptes.daemon.bashplex.DelimitedBashReceiverFactory instance at 0x192fb48 2013-09-16 07:12:33-0400 [-] GUIFactory starting on '/var/run/epoptes/epoptes.socket' 2013-09-16 07:12:33-0400 [-] Starting factory epoptes.daemon.guiplex.GUIFactory instance at 0x192fc68 I then started epoptes in a GUI. After the GUI was up, I booted ltsp20, and logged in. I didn't get a notification until after logging in. I next booted a different thin client and booted it, and then logged in with a different account. Both account logins are registered, but only the second machine. Very strange. dhopkins@ncslts7:~$ epoptes Got clients: None New connection from 127.0.0.1:55500 --- **addClient's been called for 127.0.0.1:55500 Continuing inside addClient... * This client is a new one, creating an instance * I am a user client, will add dcas028 in my list New connection from 192.168.0.25:34055 --- **addClient's been called for 192.168.0.25:34055 Continuing inside addClient... * This client is a new one, creating an instance * I am a root client New connection from 127.0.0.1:55643 --- **addClient's been called for 127.0.0.1:55643 Continuing inside addClient... * This is an existing client * I am a user client, will add dcas029 in my list -- You received this question notification because you are a member of Epoptes Developers, which is an answer contact for Epoptes. -- Mailing list: https://launchpad.net/~epoptes Post to : epoptes@lists.launchpad.net Unsubscribe : https://launchpad.net/~epoptes More help : https://help.launchpad.net/ListHelp
Re: [Epoptes] [Question #235416]: Epoptes is running commands with wrong locale
Question #235416 on Epoptes changed: https://answers.launchpad.net/epoptes/+question/235416 Status: Open = Needs information Alkis Georgopoulos requested more information: Comparing local and remote == that's comparing 2 different PCs, which might have different locale settings. It would be better to compare [remote invoked with epoptes] with [remote invoked with alt+f2], like I suggested. Try putting this file to the standalone client, in /etc/xdg/autostart/xterm.desktop: http://www.opensource.apple.com/source/X11apps/X11apps-44/xterm/xterm-269/xterm.desktop That way, an xterm should open after login. Check the environment there. If it's the same as in the epoptes-client invoked xterm, then it's not an epoptes issue, it's an opensuse issue (or an installation issue). -- You received this question notification because you are a member of Epoptes Developers, which is an answer contact for Epoptes. -- Mailing list: https://launchpad.net/~epoptes Post to : epoptes@lists.launchpad.net Unsubscribe : https://launchpad.net/~epoptes More help : https://help.launchpad.net/ListHelp
Re: [Epoptes] [Question #235416]: Epoptes is running commands with wrong locale
Question #235416 on Epoptes changed: https://answers.launchpad.net/epoptes/+question/235416 Status: Open = Answered Alkis Georgopoulos proposed the following answer: LSB was supposed to be a cross-distro standard... but unfortunately it appears it's not really portable :( So we'll probably have to put a lot of distro-specific code there, if we want to have good start/stop daemon output in all distros and init systems... Laércio, please close this question and file a related bug report in epoptes, I'll test 5-6 different distros and commit a fix when I have some free time. Thanks! -- You received this question notification because you are a member of Epoptes Developers, which is an answer contact for Epoptes. -- 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 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 log_success_msg(), log_warning_msg() and log_failure_msg(). Moreover, it sources another openSUSE-specific config file named /etc/rc.status, which exports LC_ALL=POSIX. This will set LC_ALL=POSIX in the environment of any command executed by Epoptes' execute dialog, which can lead to applications being opened in english, instead of user's default locale. So, before sourcing /lib/lsb/init-functions, epoptes-client should check if distro is Debian-based (check for /etc/debian_version?). If sourcing /lib/lsb/init-functions is still desirable in openSUSE, please notice that - the logging functions are different (see above), - you should explicitly source file /etc/profile.d/lang.sh to get rid of LC_ALL, if its value is other than $LANG. ** Affects: epoptes Importance: Undecided Status: New ** Summary changed: - epotes-client relies in /lib/lsb/init-functions, which may not provide the desired functionality in non-Debian-based distros + epotes-client relies on /lib/lsb/init-functions, which may not provide the desired functionality in non-Debian-based distros ** Description changed: 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 log_success_msg(), log_warning_msg() and log_failure_msg(). Moreover, it sources another openSUSE-specific config file named /etc/rc.status, which exports LC_ALL=POSIX. This will set LC_ALL=POSIX in the environment of any command executed by Epoptes' execute dialog, which can lead to applications being opened in english, instead of user's default locale. So, before sourcing /lib/lsb/init-functions, epoptes-client should check if distro is Debian-based (check for /etc/debian_version?). If sourcing /lib/lsb/init-functions is still desirable in openSUSE, please notice that - the logging functions are different (see above), - - you should explicitly source file /etc/profile.d/lang.sh to get rid of LC_ALL, if its value is different of $LANG. + - you should explicitly source file /etc/profile.d/lang.sh to get rid of LC_ALL, if its value is other than $LANG. -- You received this bug notification because you are a member of Epoptes Developers, which is subscribed to Epoptes. https://bugs.launchpad.net/bugs/1226094 Title: epotes-client relies on /lib/lsb/init-functions, which may not provide the desired functionality in non-Debian-based distros Status in Epoptes: New Bug description: 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 log_success_msg(), log_warning_msg() and log_failure_msg(). Moreover, it sources another openSUSE-specific config file named /etc/rc.status, which exports LC_ALL=POSIX. This will set LC_ALL=POSIX in the environment of any command executed by Epoptes' execute dialog, which can lead to applications being opened in english, instead of user's default locale. So, before sourcing /lib/lsb/init-functions, epoptes-client should check if distro is Debian-based (check for /etc/debian_version?). If sourcing /lib/lsb/init-functions is still desirable in openSUSE, please notice that - the logging functions are different (see above), - you should explicitly source file /etc/profile.d/lang.sh to get rid of LC_ALL, if its value is other than $LANG. To manage notifications about this bug go to: https://bugs.launchpad.net/epoptes/+bug/1226094/+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
