Hi, Here a log files taken from the x2goserver when logged from my laptop (where it works) and from my tce (where it works badly). I also attach the xdpyinfo output taken from within the x2go session from my laptop and from my tce ... As you will see, they are strictly identical. In the log files, apparently, RANDR and XINERAMA support is enabled in both cases. Regards, Walid Moghrabi TRAVAUX.COM BAT I - PARC CEZANNE 2 290 AVENUE GALILEE - CS 80403 13591 AIX EN PROVENCE CEDEX 3 ----- Mail original ----- De: "Walid MOGHRABI" À: uli42@gmx.de, 1197@bugs.x2go.org Envoyé: Lundi 24 Juillet 2017 21:49:41 Objet: [X2Go-Dev] Bug#1197: Bug#1197: Bug#1197: Bug#1197: Multihead fullscreen not working with TCE client in displaymanager mode Well, I'll do this tomorrow. The only thing I can tell is that multihead IS working on my laptop and I was quite sceptical too when I saw the output from my laptop ... I would have thought that it would list 2 separate screens at least and not on huge aggregated one. Are there any requirements for randr to work with X2Go and Arctica libs on the client side ? Maybe there are some tools/libs missing on the TCE side. I saw that x11-xserver-utils where missing on my TCE side which means xrandr tool was missing and I couldn't use it. Anyway, installing it changed a thing (before, the second screen was black when the broker logon was there, now it is blue and the screen ordering is different) but it didn't changed anything once the X2Go session was opened (still MATE Desktop stretched on both screens and only 1 huge monitor seen by the screen utility). 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" À: "Stefan Baur" , 1197@bugs.x2go.org Envoyé: Lundi 24 Juillet 2017 20:35:20 Objet: [X2Go-Dev] Bug#1197: Bug#1197: Bug#1197: Multihead fullscreen not working with TCE client in displaymanager mode If I understand correctly TCE is not the side where the nxagent is running. So the version oft nx-libs there does not matter. I am wondering how the connection from the laptop can generate xinerama info as the laptop's xserver, that must provide the data, does not. Please post a log oft the nxagent startup. And the output oft xdpyinfo -ext XINERAMA within the session. Uli Am 24.07.2017 18:50 schrieb "Stefan Baur" < X2Go-ML-1@baur-itcs.de >: Am 24.07.2017 um 15:16 schrieb Walid MOGHRABI: > Using latest Arctica's NX-Libs xrandr support is far better and multihead support in fullscreen mode with the Linux x2goclient works like a charm. [...] > So with the Linux client installed on a desktop (I'm personaly using Ubuntu 16.04 + Unity desktop) it works great whereas, in TCE / Displaymanager mode, multiple monitors are supported but the desktop is stretched as if it was only one big screen and not 2 separated screens. Are you sure your custom TCE build includes the Arctica NX-Libs? I would suggest logging in to a running TCE and comparing the output of "dpkg -l". Kind Regards, Stefan Baur -- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243 _______________________________________________ x2go-dev mailing list x2go-dev@lists.x2go.org https://lists.x2go.org/listinfo/x2go-dev _______________________________________________ x2go-dev mailing list x2go-dev@lists.x2go.org https://lists.x2go.org/listinfo/x2go-dev --- 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 _______________________________________________ x2go-dev mailing list x2go-dev@lists.x2go.org https://lists.x2go.org/listinfo/x2go-dev --- 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