Please find them attached. Just to note, I don't know what you mean by "older x2go client", on my TCE, x2go client is the most up to date I could get (Heuler release and up to date) : =========================================================== root@TCE-CLIENT-DELL-VOSTRO430-4D1ZR4J:~# dpkg -l | grep "x2go\|nx" ii libxcomp3:amd64 2:3.5.0.33-0~693~ubuntu16.04.1 amd64 nx-X11 compression library ii nxproxy 2:3.5.0.33-0~693~ubuntu16.04.1 amd64 NX proxy ii pinentry-x2go 0.7.5.10-0~106~ubuntu16.04.1 amd64 Qt4-based PIN or pass-phrase entry dialog for x2goclient ii x2goclient 4.1.0.1-0~1616~ubuntu16.04.1 amd64 X2Go Client application (Qt4) ii x2gothinclient-common 1.5.0.0-0~612~ubuntu16.04.1 all X2Go thin client environment (common files) ii x2gothinclient-displaymanager 1.5.0.0-0~612~ubuntu16.04.1 all login daemon starting x2goclient in displaymanager mode =========================================================== Note that I uninstalled Arctica Libs to see if it changed anything but it didn't, that's why you don't see Arctica's nxproxy/libxcomp3 versions. Here are my client versions on my laptop : =========================================================== walid@FRLM02:~$ dpkg -l | grep "x2go\|nx" ii libxcomp3:amd64 2:3.5.0.33-0~693~ubuntu16.04.1 amd64 nx-X11 compression library ii nxproxy 2:3.5.0.33-0~693~ubuntu16.04.1 amd64 NX proxy ii x2goclient 4.1.0.1-0~1616~ubuntu16.04.1 amd64 X2Go Client application (Qt4) =========================================================== Regards, Walid Moghrabi TRAVAUX.COM BAT I - PARC CEZANNE 2 290 AVENUE GALILEE - CS 80403 13591 AIX EN PROVENCE CEDEX 3 ----- Mail original ----- De: "Ulrich Sibiller" À: "Walid MOGHRABI" , 1197@bugs.x2go.org, "Stefan Baur" Envoyé: Mercredi 26 Juillet 2017 14:19:36 Objet: Re: Bug#1197: Multihead fullscreen not working with TCE client in displaymanager mode Ok, thanks. This shows that the TCE is using an old x2goclient that is still generating a xinerama.conf on ther server side (this file's content should match the values of xrandr and xdpyinfo you sent before). So you probably have xinerama enabled in the session configuration in x2goclient. For nx 3.5.99.x this is not required (but I doubt adjusting that will change anything). The options file contains fullscreen=1 and we have a bug regarding that option (https://github.com/ArcticaProject/nx-libs/issues/449). So I ask you to - provide the options file and ls output also for the working Laptop session - turn off fullscreen in the session's configuration and see if that changes anything for you (maybe ctrl-alt-f will work then, too) Uli On Wed, Jul 26, 2017 at 2:08 PM, Walid MOGHRABI wrote: > Here there are > > > Regards, > Walid Moghrabi > > TRAVAUX.COM > BAT I - PARC CEZANNE 2 290 AVENUE GALILEE - CS 80403 > 13591 AIX EN PROVENCE CEDEX 3 > > ----- Mail original ----- > > De: "Ulrich Sibiller" > À: "Walid MOGHRABI" > Cc: "Stefan Baur" , 1197@bugs.x2go.org > Envoyé: Mercredi 26 Juillet 2017 13:58:14 > Objet: Re: Bug#1197: Multihead fullscreen not working with TCE client in displaymanager mode > > On Wed, Jul 26, 2017 at 1:52 PM, Walid MOGHRABI > wrote: >> Sorry, find the correct output attached. >> Seems to report 2 heads effectively. > > Ok, now we are a step further. From my POV your client setup ist > correct. X11 wise. We now need to find out why nxagent does not get / > respect that information. > > Let't have a look at the server side. In the same dir you found the > nxagent logfiles there will also be a file called options. What's the > content? Please also post an ls -l of the dir. > > Uli > --- > DISCLAIMER: This e-mail is private and confidential and may contain proprietary or legally privileged information. It is for the intended recipient only. If you have received this email in error, please notify the author by replying to it and then destroy it. If you are not the intended recipient you must not use, disclose, distribute, copy, print or rely on this e-mail or any attachment. Thank you --- DISCLAIMER: This e-mail is private and confidential and may contain proprietary or legally privileged information. It is for the intended recipient only. If you have received this email in error, please notify the author by replying to it and then destroy it. If you are not the intended recipient you must not use, disclose, distribute, copy, print or rely on this e-mail or any attachment. Thank you