[X2Go-Dev] Bug#1200: Double clicks not recognized in Qt(4?/5?) applications (Was: Environment variables not set)

2017-09-05 Thread Mihai Moldovan
Control: retitle -1 Double clicks not recognized in Qt(4?/5?) applications Control: reassign -1 x2goclient 4.1.0.0 Control: tag -1 build-win32 On 09/05/2017 10:42 AM, Bruno CAPELETO wrote: > Found : in sshd_config, one must use the "UsePAM yes" directive > > I do not really see the link with the

[X2Go-Dev] Processed: Re: Double clicks not recognized in Qt(4?/5?) applications (Was: Environment variables not set)

2017-09-05 Thread X2Go Bug Tracking System
Processing control commands: > retitle -1 Double clicks not recognized in Qt(4?/5?) applications Bug #1200 [x2goserver] Environment variables not set Changed Bug title to 'Double clicks not recognized in Qt(4?/5?) applications' from 'Environment variables not set' > reassign -1 x2goclient

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

2017-09-05 Thread Bruno CAPELETO
Found : in sshd_config, one must use the "UsePAM yes" directive I do not really see the link with the locales, and on top of that that open some security holes I guess. For example, adding this instruction I had to add additional instructions to forbid the password authentication. Conclusions

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

2017-09-05 Thread Bruno CAPELETO
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 : > I did dpkg-reconfigure locales as root. > > Then I get : > > ~# locale > LANG=fr_FR.UTF-8 >

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

2017-09-05 Thread Ulrich Sibiller
Maybe you could provide a VM with the non-working Installation so we can have a look at it. Uli - Ursprüngliche Nachricht - Von: "Bruno CAPELETO" Gesendet: ‎05.‎09.‎2017 08:10 An: "Mihai Moldovan" Cc: "1...@bugs.x2go.org"

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

2017-09-05 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