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

2017-09-05 Thread Mihai Moldovan
On 09/05/2017 09:28 AM, Bruno CAPELETO wrote: > 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. sshd_config? Sounds more like something in your shell startup scripts, but there are few options that might influence this. O

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

2017-09-04 Thread Bruno CAPELETO
Dear Mihai, What good piece of news to start the day with !!! So you do not see that "bug" on a fresh install. Unfortunately I see it, and also on a fresh install. It is even worse : I see it on 3 fresh server installs : - Ubuntu 14.04.4 LTS (old installation) - Debian GNU/Linux 8 - Debian GNU/Li

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

2017-09-04 Thread Mihai Moldovan
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-xsessi

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

2017-08-16 Thread Bruno CAPELETO
2017-08-11 5:29 GMT+02:00 Mihai Moldovan : > Control: reassign -1 x2goserver 4.0.1.20 > > First of all, x2goserver 4.0.1.20 actually is the correct stable release. > 4.1.0.0 are the current nightly releases. > > I personally don't care much about what version is tested, but knowing > whether > the

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

2017-08-10 Thread Mihai Moldovan
Control: reassign -1 x2goserver 4.0.1.20 First of all, x2goserver 4.0.1.20 actually is the correct stable release. 4.1.0.0 are the current nightly releases. I personally don't care much about what version is tested, but knowing whether there's a difference in behavior between the stable and night

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

2017-08-10 Thread Bruno CAPELETO
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