On 09/04/2017 05:44 PM, Bruno CAPELETO wrote:
> People in Laurux's forum have reported this software works in single app mode
> but on an Ubuntu server.

Okay, I have just tried to reproduce your issues in a new, fresh Debian Stretch
VM. Only installed the core system, x2goserver, x2goserver-xsession, lxde and
gambas3.

Then (since I installed the system using the en_US.utf8 locale), ran
dpkg-reconfigure locales, selected fr_FR.* to be generated and set the default
locale to fr_FR.utf8.

Started up a new X2Go session (desktop session, LXDE) and was greeted by a
French-speaking LXDE instance (with some English text from the clipboard
manager, that does not seem to have a French localization. No problem.)

Afterwards, started gambas3 in the LXDE desktop session. Worked fine. And showed
up in French.


Next up: started gambas3 in single application mode. Came up fine and in French.


And just for fun, I then went on, downloaded Laurux3.tar.gz from the website
(since this software doesn't seem to be packaged within Debian directly...),
installed gambas3-gb-qt4 and gambas3-gb-qt4-ext (since it looked like these
modules were missing) and started Laurux3.gambas in the LXDE instance. It
greeted me in French with a dialog to setup MySQL. I skipped this and
Gambas3-Laurux started up. Again, everything was in French.

Last thing: started /home/ionic/applications/Laurux3/Laurux3.gambas (obviously
the path I extracted it to) in a single application session. Again, I was
greeted by the dialog to create a MySQL database. Skipped this, and
Laurux-Gambas came up. All in French. It looked weird, but that's because in
single application mode, we don't yet have an XSETTINGS daemon running that
would enable Qt4 to look up its theme settings, so a ugly fallback theme is
being used by default.


So far, I'm unable to reproduce any issue (and curiously, the Laurux version
from their homepage seems to be using Qt4 instead of Qt5 as well, so I wonder
how you came up with Qt4 before.)

I wasn't able to test the double-clicking issue, since all tests were carried
out using X2Go Client on Linux.


I'd like to understand why your env variables are not being set correctly, but
it doesn't seem to be systematic X2Go bug. With a cleanly installed system, this
does not seem to happen.



Mihai