[X2Go-Dev] Bug#1222: Timeout of about 30s to start the x2go session

Package: Version: <4.1.0.0-0x2go1.2~git20170806.1410+9.heuler.1> # uname -a Linux mtcie1 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2+deb9u1 (2017-06-18) x86_64 GNU/Linux # cat /etc/issue Debian GNU/Linux 9 \n \l When connecting to this x2go server - linux client and/or Windows client, I tested both -

[X2Go-Dev] Bug#1200: Bug#1200: Bug#1200: Environment variables not set

9:28 GMT+02:00 Bruno CAPELETO <bruno.capel...@abcreseau.com>: > The issue came from my home-made sshd_config file. > > I still work it up and will give here the solution in a few minutes. > > > 2017-09-05 9:07 GMT+02:00 Bruno CAPELETO <bruno.capel...@abcreseau.co

[X2Go-Dev] Bug#1200: Bug#1200: Bug#1200: Environment variables not set

The issue came from my home-made sshd_config file. I still work it up and will give here the solution in a few minutes. 2017-09-05 9:07 GMT+02:00 Bruno CAPELETO <bruno.capel...@abcreseau.com>: > I did dpkg-reconfigure locales as root. > > Then I get : > > ~# loca

[X2Go-Dev] Bug#1200: Environment variables not set

gt;: > 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 ins

[X2Go-Dev] Bug#1200: Bug#1200: Environment variables not set

People in Laurux's forum have reported this software works in single app mode but on an Ubuntu server. So it looks like this crash issue is related to the non-proper setting of the locale on Debian server... 2017-08-16 11:17 GMT+02:00 Bruno CAPELETO <bruno.capel...@abcreseau.com>: >

[X2Go-Dev] Bug#1200: Environment variables not set

t what version is tested, but knowing > whether > there's a difference in behavior between the stable and nightly versions is > certainly helpful. > Same issues with both versions. > > > On 08/10/2017 12:24 PM, Bruno CAPELETO wrote: > > Package: Version: <4.0.1.20-0x2go1+

[X2Go-Dev] Bug#1198: Bug#1198: X2Go issue (in src:x2goserver) has been marked as pending for release

That "fix" did not change anything to my issues. The issues are coming even on a new session. 2017-08-11 9:47 GMT+02:00 Mihai Moldovan : > tag #1198 pending > fixed #1198 4.0.1.21 > thanks > > Hello, > > X2Go issue #1198 (src:x2goserver) reported by you has been > fixed in X2Go

[X2Go-Dev] Bug#1200: Bug#1200: Bug#1200: Bug#1200: Environment variables not set

difference between the full LXDE session et single app mode : is there an explanation somewhere ? 2017-08-10 21:52 GMT+02:00 Bruno CAPELETO <bruno.capel...@abcreseau.com>: > >> > 1. Whatever the client (Windows or Linux 4.0.3.1-4), the local >> >> > environ

[X2Go-Dev] Bug#1200: Bug#1200: Bug#1200: Bug#1200: Environment variables not set

> > >> > 1. Whatever the client (Windows or Linux 4.0.3.1-4), the local > >> > environment > >> > variables are not set properly and the software - which needs French > >> > localization - crashes. That could be "solved" the following way : > >> > /etc/x2go/Xsession : > >> > >> Hmm, the

[X2Go-Dev] Bug#1200: Bug#1200: Bug#1200: Environment variables not set

> > > 1. Whatever the client (Windows or Linux 4.0.3.1-4), the local > environment > > variables are not set properly and the software - which needs French > > localization - crashes. That could be "solved" the following way : > > /etc/x2go/Xsession : > > Hmm, the environment is usually set by the

[X2Go-Dev] Bug#1200: Bug#1200: Environment variables not set

ins an unusual number of problems at once. Are > you sure your system is setup properly? > > Uli > > On Thu, Aug 10, 2017 at 12:24 PM, Bruno CAPELETO > <bruno.capel...@abcreseau.com> wrote: > > Package: > > Version: <4.0.1.20-0x2go1+git20170412.1125+9.main.1>

[X2Go-Dev] Bug#1200: Environment variables not set

Package: Version: <4.0.1.20-0x2go1+git20170412.1125+9.main.1> # uname -a Linux mtcie1 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2+deb9u1 (2017-06-18) x86_64 GNU/Linux The below bugs are most probably related to each other, that's why I open one case for all of them. The issues are the following : I