Hi folks,
Just an idea - some XRANDR-related stuff that is specific to X2Go-TCE-Live is happening in this file:
Which, in turn, was inspired by this file from X2Go-TCE-Classic (NFS):
As this is specific to the TCEs, maybe this is the root cause of the difference you're seeing?
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
On Tue, Jul 25, 2017 at 6:55 PM, Stefan Baur <X2Go-ML-1@baur-itcs.de> wrote:
Hi folks,
Just an idea - some XRANDR-related stuff that is specific to X2Go-TCE-Live is happening in this file:
Which, in turn, was inspired by this file from X2Go-TCE-Classic (NFS):
As this is specific to the TCEs, maybe this is the root cause of the difference you're seeing?
Hmmm, I doubt that. Usings NX the client side is not really doing anything X wise. It's the nxagent that calls XineramaQueryScreens(). It asks the client side X server (the real X server) for its Xinerama configuration. We have learned from the previous outputs that Walis had sent that the real X server does not have Xinerama configured. Therefore the agent does not see any Xinerama configuration. (The only possible exception to this would be nxproxy running with LD_PRELOAD of libfakexinerama.so which is not happening here.)
Now, in the Laptop scenario you can see via xrandr that nxagent has gotten the Xinerama information somehow. Otherwise it would not have been possible to setup two NX outputs/monitors/heads.
The two logfiles are almost the same except the last line where the in the Laptop scenario you can see this line
Info: Screen [0] resized to geometry [3840x1080] fullscreen [1].
This line is printed if nxagent has received and processed a sizing event. In the TCE scenario no sizing event was sent to nxagent which - if really true - is probably the TCE window manager's fault.
Walid, can you please try pressing CTRL-ALT-F twice in the TCE scenario? What is xrandr showing afterwards?
Uli
Hi guys,
Just to give a bit more informations on my TCE setup : it is not based on the live-build scripts because it is not well suited for Ubuntu 16.04 and to be honest, I never managed to get a working live build that way so I gave up. My TCE image is more or less a tweaked ubuntu 16.04 debbotstrapped image with x2gothinclient-displaymanager installed (+ a few more things but really, this is a pretty basic ubuntu server image + x2gothinclient installed)
By the way, Stefan put the finger on one point : in /usr/sbin/x2gothinclientd, I commented the whole randr stuff block (from line 114 to line 175) to make a try then restarted the x2gothinclient-displaymanager but while it didn't fix my multimonitor support within the X2Go session, it fixed a bad ordering of the monitors. Before that, my monitors were inverted (right was left and left was right), commenting this block lead to right ordering of the monitors this time.
Concerning your test Uli, doing "Ctrl+Alt+F" within the X2Go session on the TCE did nothing. I don't know if it was meant to do anything but I did it many times following the action by a xrandr output in the console, nothing changed, same values all the time (one big screen, not 2)
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" <ulrich.sibiller@gmail.com> À: "Stefan Baur" <X2Go-ML-1@baur-itcs.de> Cc: 1197@bugs.x2go.org, "Walid MOGHRABI" <w.moghrabi@servicemagic.eu> Envoyé: Mardi 25 Juillet 2017 22:11:28 Objet: Re: Bug#1197: Multihead fullscreen not working with TCE client in displaymanager mode
On Tue, Jul 25, 2017 at 6:55 PM, Stefan Baur <X2Go-ML-1@baur-itcs.de> wrote:
Hi folks,
Just an idea - some XRANDR-related stuff that is specific to X2Go-TCE-Live is happening in this file:
Which, in turn, was inspired by this file from X2Go-TCE-Classic (NFS):
As this is specific to the TCEs, maybe this is the root cause of the difference you're seeing?
Hmmm, I doubt that. Usings NX the client side is not really doing anything X wise. It's the nxagent that calls XineramaQueryScreens(). It asks the client side X server (the real X server) for its Xinerama configuration. We have learned from the previous outputs that Walis had sent that the real X server does not have Xinerama configured. Therefore the agent does not see any Xinerama configuration. (The only possible exception to this would be nxproxy running with LD_PRELOAD of libfakexinerama.so which is not happening here.)
Now, in the Laptop scenario you can see via xrandr that nxagent has gotten the Xinerama information somehow. Otherwise it would not have been possible to setup two NX outputs/monitors/heads.
The two logfiles are almost the same except the last line where the in the Laptop scenario you can see this line
Info: Screen [0] resized to geometry [3840x1080] fullscreen [1].
This line is printed if nxagent has received and processed a sizing event. In the TCE scenario no sizing event was sent to nxagent which - if really true - is probably the TCE window manager's fault.
Walid, can you please try pressing CTRL-ALT-F twice in the TCE scenario? What is xrandr showing afterwards?
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
On Wed, Jul 26, 2017 at 10:35 AM, Walid MOGHRABI <w.moghrabi@servicemagic.eu> wrote:
Just to give a bit more informations on my TCE setup : it is not based on the live-build scripts because it is not well suited for Ubuntu 16.04 and to be honest, I never managed to get a working live build that way so I gave up. My TCE image is more or less a tweaked ubuntu 16.04 debbotstrapped image with x2gothinclient-displaymanager installed (+ a few more things but really, this is a pretty basic ubuntu server image + x2gothinclient installed)
Maybe Stefan can provide an image that you can try?
By the way, Stefan put the finger on one point : in /usr/sbin/x2gothinclientd, I commented the whole randr stuff block (from line 114 to line 175) to make a try then restarted the x2gothinclient-displaymanager but while it didn't fix my multimonitor support within the X2Go session, it fixed a bad ordering of the monitors. Before that, my monitors were inverted (right was left and left was right), commenting this block lead to right ordering of the monitors this time.
AFAIU wrong ordering is the raeson for that code. You can instruct it how to arrange the monitors via that code ("above", "leftof" a.s.o.)
Concerning your test Uli, doing "Ctrl+Alt+F" within the X2Go session on the TCE did nothing. I don't know if it was meant to do anything but I did it many times following the action by a xrandr output in the console, nothing changed, same values all the time (one big screen, not 2)
Hmm, this keystroke is supposed to toggle fullscreen. And it is working in the TCE image I have here (switches to windowed mode and back again to fullscreen on the second stroke). You could also try Ctrl+Shift+Alt+F but I doubt it will work if the other keystroke did not work...
Uli
Am 26.07.2017 um 11:01 schrieb Ulrich Sibiller:
Just to give a bit more informations on my TCE setup : it is not based on the live-build scripts because it is not well suited for Ubuntu 16.04 and to be honest, I never managed to get a working live build that way so I gave up.
Why didn't you report your issues with the current build process in a bug or on the list so we have a chance to improve our build process/documentation?
My TCE image is more or less a tweaked ubuntu 16.04 debbotstrapped image with x2gothinclient-displaymanager installed (+ a few more things but really, this is a pretty basic ubuntu server image + x2gothinclient installed) Maybe Stefan can provide an image that you can try?
We already do. Our images are hosted at
and I'm actually working on a new build of the stable image for a customer, so expect a new upload in the next few days.
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
Why didn't you report your issues with the current build process in a bug or on the list so we have a chance to improve our build process/documentation?
Well, for multiple reasons :
First : the kernel image process uses live build scripts that are obsolete on Ubuntu 16.04 so it crashes all the time because of invalid dependencies problems (those scripts needs packages from Debian that are not available on Ubuntu) ... so it was just headaches
Second : sorry to say that but the live build process documentation is pretty partial and based on situation where "it works" but outside that scope a lot of things "just don't work" and there are many forks for the setup scripts from many users so to be honest ... this is a bit messy and since there is nothing in the repo but everything in personnal github here and there, it was just to complicated
Third : I wanted to report things and help in building a nice TCE builder process but I wanted to base this on Ubuntu and not Debian and I also wanted to understand what was under the hood so I did it myself and to my surprise, it was not that complicated and works pretty well (until this dual head problem) for then report things and help.
I'll give a try to the built images.
Regards, Walid Moghrabi
TRAVAUX.COM BAT I - PARC CEZANNE 2 290 AVENUE GALILEE - CS 80403 13591 AIX EN PROVENCE CEDEX 3
----- Mail original -----
De: "Stefan Baur" <X2Go-ML-1@baur-itcs.de> À: "Ulrich Sibiller" <uli42@gmx.de>, "Walid MOGHRABI" <w.moghrabi@servicemagic.eu> Cc: 1197@bugs.x2go.org Envoyé: Mercredi 26 Juillet 2017 11:05:20 Objet: Re: Bug#1197: Multihead fullscreen not working with TCE client in displaymanager mode
Am 26.07.2017 um 11:01 schrieb Ulrich Sibiller:
Just to give a bit more informations on my TCE setup : it is not based on the live-build scripts because it is not well suited for Ubuntu 16.04 and to be honest, I never managed to get a working live build that way so I gave up.
Why didn't you report your issues with the current build process in a bug or on the list so we have a chance to improve our build process/documentation?
My TCE image is more or less a tweaked ubuntu 16.04 debbotstrapped image with x2gothinclient-displaymanager installed (+ a few more things but really, this is a pretty basic ubuntu server image + x2gothinclient installed) Maybe Stefan can provide an image that you can try?
We already do. Our images are hosted at
and I'm actually working on a new build of the stable image for a customer, so expect a new upload in the next few days.
Kind Regards, Stefan Baur
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
Am 26.07.2017 um 11:25 schrieb Walid MOGHRABI:
Why didn't you report your issues with the current build process in a bug or on the list so we have a chance to improve our build process/documentation?
Well, for multiple reasons :
First : the kernel image process uses live build scripts that are obsolete on Ubuntu 16.04 so it crashes all the time because of invalid dependencies problems (those scripts needs packages from Debian that are not available on Ubuntu) ... so it was just headaches
You could probably set up a Debian changeroot using debootstrap (admittedly, I've never tried that, though), or a virtual machine with Debian as a dedicated build host.
Second : sorry to say that but the live build process documentation is pretty partial and based on situation where "it works" but outside that scope a lot of things "just don't work" and there are many forks for the setup scripts from many users so to be honest ... this is a bit messy and since there is nothing in the repo but everything in personnal github here and there, it was just to complicated
Are you talking about the live-build project's documentation, or the X2Go-TCE-Live documentation?
If all you want to do is build X2Go-TCE-Live images, you don't need to start by reading and trying to understand the live-build project's docs.
Read our Wiki page: <https://wiki.x2go.org/doku.php/doc:howto:tce#starting_the_build>, run the three chunks of code given in the sections titled "Configuring the Build", "Live-Patching the Build", "Starting the Build", and you end up with a stable, i386 build ready for netbooting via PXE, TFTP, HTTP.
Prefer one that boots from local/portable media? Change export LBX2GO_IMAGETYPE='netboot' to export LBX2GO_IMAGETYPE='iso-hybrid' in the first chunk of code, and you're done. Can't get much easier than that, can it?
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
That's what I did and it simply didn't work for a Ubuntu based image.
Most configuration switches for live-build script are not supported under Ubuntu and well, I don't remember every bits of what were working or not because I tried monthes ago but it was to tricky and except for Debian, it was simply unusable as is. As for the git repos, I tried many combinations and nothing worked as expected so I basicaly decided to do this by hand and take inspiration from the howto on what to install/tweak.
I ended with something that was not that complicated to do, scriptable (mostly) and working (except for this dual head stuff) so I stopped going the Live Build way, at least, just the time to sort out things and get back with some contributions on that part.
Regards, Walid Moghrabi
TRAVAUX.COM BAT I - PARC CEZANNE 2 290 AVENUE GALILEE - CS 80403 13591 AIX EN PROVENCE CEDEX 3
----- Mail original -----
De: "Stefan Baur" <X2Go-ML-1@baur-itcs.de> À: "Walid MOGHRABI" <w.moghrabi@servicemagic.eu> Cc: 1197@bugs.x2go.org, "Ulrich Sibiller" <uli42@gmx.de> Envoyé: Mercredi 26 Juillet 2017 11:49:56 Objet: Re: Bug#1197: Multihead fullscreen not working with TCE client in displaymanager mode
Am 26.07.2017 um 11:25 schrieb Walid MOGHRABI:
Why didn't you report your issues with the current build process in a bug or on the list so we have a chance to improve our build process/documentation?
Well, for multiple reasons :
First : the kernel image process uses live build scripts that are obsolete on Ubuntu 16.04 so it crashes all the time because of invalid dependencies problems (those scripts needs packages from Debian that are not available on Ubuntu) ... so it was just headaches
You could probably set up a Debian changeroot using debootstrap (admittedly, I've never tried that, though), or a virtual machine with Debian as a dedicated build host.
Second : sorry to say that but the live build process documentation is pretty partial and based on situation where "it works" but outside that scope a lot of things "just don't work" and there are many forks for the setup scripts from many users so to be honest ... this is a bit messy and since there is nothing in the repo but everything in personnal github here and there, it was just to complicated
Are you talking about the live-build project's documentation, or the X2Go-TCE-Live documentation?
If all you want to do is build X2Go-TCE-Live images, you don't need to start by reading and trying to understand the live-build project's docs.
Read our Wiki page: <https://wiki.x2go.org/doku.php/doc:howto:tce#starting_the_build>, run the three chunks of code given in the sections titled "Configuring the Build", "Live-Patching the Build", "Starting the Build", and you end up with a stable, i386 build ready for netbooting via PXE, TFTP, HTTP.
Prefer one that boots from local/portable media? Change export LBX2GO_IMAGETYPE='netboot' to export LBX2GO_IMAGETYPE='iso-hybrid' in the first chunk of code, and you're done. Can't get much easier than that, can it?
Kind Regards, Stefan Baur
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
On Wed, Jul 26, 2017 at 12:05 PM, Walid MOGHRABI <w.moghrabi@servicemagic.eu> wrote:
That's what I did and it simply didn't work for a Ubuntu based image.
Most configuration switches for live-build script are not supported under Ubuntu and well, I don't remember every bits of what were working or not because I tried monthes ago but it was to tricky and except for Debian, it was simply unusable as is. As for the git repos, I tried many combinations and nothing worked as expected so I basicaly decided to do this by hand and take inspiration from the howto on what to install/tweak.
I ended with something that was not that complicated to do, scriptable (mostly) and working (except for this dual head stuff) so I stopped going the Live Build way, at least, just the time to sort out things and get back with some contributions on that part.
Let's not get distracted.
Back to your setup. You posted xpdyinfo output some days ago that clearly showed that the real X server on your TCE setup does not offer xinerama. And you posted xrandr output that showed multiple screens for the same X server. Just to be sure nothing got confused: please run both commands again on the TCE's X server. If it stays like this please check the X server's logfile for any randr or xinerama messages.
Uli
You're right, here are what you asked, all taken from the TCE directly, not from within the X2Go session :
========================================================================= root@TCE-CLIENT-DELL-VOSTRO430-4D1ZR4J:~# xdpyinfo -display :0 name of display: :0 version number: 11.0 vendor string: The X.Org Foundation vendor release number: 11804000 X.Org version: 1.18.4 maximum request size: 16777212 bytes motion buffer size: 256 bitmap unit, bit order, padding: 32, LSBFirst, 32 image byte order: LSBFirst number of supported pixmap formats: 7 supported pixmap formats: depth 1, bits_per_pixel 1, scanline_pad 32 depth 4, bits_per_pixel 8, scanline_pad 32 depth 8, bits_per_pixel 8, scanline_pad 32 depth 15, bits_per_pixel 16, scanline_pad 32 depth 16, bits_per_pixel 16, scanline_pad 32 depth 24, bits_per_pixel 32, scanline_pad 32 depth 32, bits_per_pixel 32, scanline_pad 32 keycode range: minimum 8, maximum 255 focus: window 0x600005, revert to Parent number of extensions: 29 BIG-REQUESTS Composite DAMAGE DOUBLE-BUFFER DPMS DRI2 GLX Generic Event Extension MIT-SCREEN-SAVER MIT-SHM Present RANDR RECORD RENDER SECURITY SGI-GLX SHAPE SYNC X-Resource XC-MISC XFIXES XFree86-DGA XFree86-VidModeExtension XINERAMA XInputExtension XKEYBOARD XTEST XVideo XVideo-MotionCompensation default screen number: 0 number of screens: 1
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" <uli42@gmx.de> À: "Walid MOGHRABI" <w.moghrabi@servicemagic.eu> Cc: "Stefan Baur" <X2Go-ML-1@baur-itcs.de>, 1197@bugs.x2go.org Envoyé: Mercredi 26 Juillet 2017 12:10:42 Objet: Re: Bug#1197: Multihead fullscreen not working with TCE client in displaymanager mode
On Wed, Jul 26, 2017 at 12:05 PM, Walid MOGHRABI <w.moghrabi@servicemagic.eu> wrote:
That's what I did and it simply didn't work for a Ubuntu based image.
Most configuration switches for live-build script are not supported under Ubuntu and well, I don't remember every bits of what were working or not because I tried monthes ago but it was to tricky and except for Debian, it was simply unusable as is. As for the git repos, I tried many combinations and nothing worked as expected so I basicaly decided to do this by hand and take inspiration from the howto on what to install/tweak.
I ended with something that was not that complicated to do, scriptable (mostly) and working (except for this dual head stuff) so I stopped going the Live Build way, at least, just the time to sort out things and get back with some contributions on that part.
Let's not get distracted.
Back to your setup. You posted xpdyinfo output some days ago that clearly showed that the real X server on your TCE setup does not offer xinerama. And you posted xrandr output that showed multiple screens for the same X server. Just to be sure nothing got confused: please run both commands again on the TCE's X server. If it stays like this please check the X server's logfile for any randr or xinerama messages.
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
On Wed, Jul 26, 2017 at 1:36 PM, Walid MOGHRABI <w.moghrabi@servicemagic.eu> wrote:
You're right, here are what you asked, all taken from the TCE directly, not from within the X2Go session :
========================================================================= root@TCE-CLIENT-DELL-VOSTRO430-4D1ZR4J:~# xdpyinfo -display :0
No, that's wrong!
xdpyinfo -ext XINERAMA -display :0 is the right command!
========================================================================= root@TCE-CLIENT-DELL-VOSTRO430-4D1ZR4J:~# xrandr --display :0 Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 8192 x 8192 DVI-I-1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 510mm x 287mm 1920x1080 60.00*+ 1280x1024 75.02 60.02 1152x864 75.00 1024x768 75.08 60.00 800x600 75.00 60.32 640x480 75.00 60.00 720x400 70.08 HDMI-1 disconnected (normal left inverted right x axis y axis) VGA-1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 510mm x 287mm 1920x1080 60.00*+ 1280x1024 75.02 60.02 1152x864 75.00 1024x768 75.08 60.00 800x600 75.00 60.32 640x480 75.00 60.00 720x400 70.08
So I expect the correct command to report 2 heads, one with 1920x1080+1920+0 and one with 1920x1080+0+0
If that is not the case we have the reason for the problems.
Uli
Sorry, find the correct output attached. Seems to report 2 heads effectively.
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" <uli42@gmx.de> À: "Walid MOGHRABI" <w.moghrabi@servicemagic.eu> Cc: "Stefan Baur" <X2Go-ML-1@baur-itcs.de>, 1197@bugs.x2go.org Envoyé: Mercredi 26 Juillet 2017 13:45:24 Objet: Re: Bug#1197: Multihead fullscreen not working with TCE client in displaymanager mode
On Wed, Jul 26, 2017 at 1:36 PM, Walid MOGHRABI <w.moghrabi@servicemagic.eu> wrote:
You're right, here are what you asked, all taken from the TCE directly, not from within the X2Go session :
========================================================================= root@TCE-CLIENT-DELL-VOSTRO430-4D1ZR4J:~# xdpyinfo -display :0
No, that's wrong!
xdpyinfo -ext XINERAMA -display :0 is the right command!
========================================================================= root@TCE-CLIENT-DELL-VOSTRO430-4D1ZR4J:~# xrandr --display :0 Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 8192 x 8192 DVI-I-1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 510mm x 287mm 1920x1080 60.00*+ 1280x1024 75.02 60.02 1152x864 75.00 1024x768 75.08 60.00 800x600 75.00 60.32 640x480 75.00 60.00 720x400 70.08 HDMI-1 disconnected (normal left inverted right x axis y axis) VGA-1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 510mm x 287mm 1920x1080 60.00*+ 1280x1024 75.02 60.02 1152x864 75.00 1024x768 75.08 60.00 800x600 75.00 60.32 640x480 75.00 60.00 720x400 70.08
So I expect the correct command to report 2 heads, one with 1920x1080+1920+0 and one with 1920x1080+0+0
If that is not the case we have the reason for the problems.
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
On Wed, Jul 26, 2017 at 1:52 PM, Walid MOGHRABI <w.moghrabi@servicemagic.eu> 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
Humm ... I guess the images used by Stefan are "mini desktop" based. I don't want to use that mode, I'd rather go with the "displaymanager" mode instead. I really want my users to login directly to their X2Go session.
I works really well in one screen only situations but now, I'd like to give my devs access to a X2Go session too but they use dual head setup and so, I wanted to have a good dual head support ... which is the case with the client under Linux (but not under Windows as I already reported earlier) so I thought that making them use the TCE would fix that but that is not the case for unknown reason.
There must be a way to fix that but I admit that my knowledge on that part is somewhat limited.
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" <uli42@gmx.de> À: "Walid MOGHRABI" <w.moghrabi@servicemagic.eu> Cc: 1197@bugs.x2go.org, "Stefan Baur" <X2Go-ML-1@baur-itcs.de> Envoyé: Mercredi 26 Juillet 2017 11:01:20 Objet: Re: Bug#1197: Multihead fullscreen not working with TCE client in displaymanager mode
On Wed, Jul 26, 2017 at 10:35 AM, Walid MOGHRABI <w.moghrabi@servicemagic.eu> wrote:
Just to give a bit more informations on my TCE setup : it is not based on the live-build scripts because it is not well suited for Ubuntu 16.04 and to be honest, I never managed to get a working live build that way so I gave up. My TCE image is more or less a tweaked ubuntu 16.04 debbotstrapped image with x2gothinclient-displaymanager installed (+ a few more things but really, this is a pretty basic ubuntu server image + x2gothinclient installed)
Maybe Stefan can provide an image that you can try?
By the way, Stefan put the finger on one point : in /usr/sbin/x2gothinclientd, I commented the whole randr stuff block (from line 114 to line 175) to make a try then restarted the x2gothinclient-displaymanager but while it didn't fix my multimonitor support within the X2Go session, it fixed a bad ordering of the monitors. Before that, my monitors were inverted (right was left and left was right), commenting this block lead to right ordering of the monitors this time.
AFAIU wrong ordering is the raeson for that code. You can instruct it how to arrange the monitors via that code ("above", "leftof" a.s.o.)
Concerning your test Uli, doing "Ctrl+Alt+F" within the X2Go session on the TCE did nothing. I don't know if it was meant to do anything but I did it many times following the action by a xrandr output in the console, nothing changed, same values all the time (one big screen, not 2)
Hmm, this keystroke is supposed to toggle fullscreen. And it is working in the TCE image I have here (switches to windowed mode and back again to fullscreen on the second stroke). You could also try Ctrl+Shift+Alt+F but I doubt it will work if the other keystroke did not work...
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
Am 26.07.2017 um 11:09 schrieb Walid MOGHRABI:
Humm ... I guess the images used by Stefan are "mini desktop" based. I don't want to use that mode, I'd rather go with the "displaymanager" mode instead. I really want my users to login directly to their X2Go session.
How about actually taking a look, rather than guessing? ;-) Hint: They're NOT minidesktop-based.
Minidesktop is still in development - it's something I occasionally work on in my spare time - and is *one* of *four* feature branches - in fact it doesn't even show up in X2Go's official Git yet (see bottom of <https://code.x2go.org/gitweb?p=live-build-x2go.git;a=summary>), only in the github repo we use in parallel for development builds (<https://github.com/LinuxHaus/live-build-x2go/tree/feature/mate-minidesktop>).
I works really well in one screen only situations but now, I'd like to give my devs access to a X2Go session too but they use dual head setup and so, I wanted to have a good dual head support ... which is the case with the client under Linux (but not under Windows as I already reported earlier) so I thought that making them use the TCE would fix that but that is not the case for unknown reason.
There must be a way to fix that but I admit that my knowledge on that part is somewhat limited.
Then use the official build process or one of our provided images, before you start tinkering. That way, we actually have a chance of telling where you took the wrong turn and are able to support you. I know for sure that our build works with dual head, as that was a paying customer's request and so we tested it. Though I'm not sure if it works the way you expect it to work. Screenshots/Pictures of your desired setup (iow, from your laptop) might help.
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
On Wed, Jul 26, 2017 at 11:21 AM, Stefan Baur <X2Go-ML-1@baur-itcs.de> wrote:
Then use the official build process or one of our provided images, before you start tinkering. That way, we actually have a chance of telling where you took the wrong turn and are able to support you. I know for sure that our build works with dual head, as that was a paying customer's request and so we tested it. Though I'm not sure if it works the way you expect it to work. Screenshots/Pictures of your desired setup (iow, from your laptop) might help.
While you are right in principle you need to consider what complicates the issue here: Walid is using nx-libs 3.5.99.x. So have you tested with them, too? If we knew if XINERAMA it is working properly even with beta nx-libs this would definitely help!
@Walid: can you provide what you have as a bootable image?
Uli
Am 26.07.2017 um 11:26 schrieb Ulrich Sibiller:
While you are right in principle you need to consider what complicates the issue here: Walid is using nx-libs 3.5.99.x. So have you tested with them, too? If we knew if XINERAMA it is working properly even with beta nx-libs this would definitely help!
No, we haven't tested that combination, as our customer runs the stable release. But: Our images are available to everyone and known to work against stable, so those should be the starting point for all tests.
If/Once these images play nice with 3.5.99.x, we can start taking a look at why forks/homegrown scripts don't work. Until then, it's a wild-goose chase.
-Stefan
-- 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
Hi,
Just tested the pre-built images from Stefan. It works with dual head, I have to tweak it a little now to use our broker instead of the session file supplied but it works (I modified the session file to tap on my X2Go server and not the demo server from Stefan).
By the way, another reason why I wanted to go Ubuntu and not Debian is the kernel support ... Debian provides 3.16 (in Jessie) and some of our test hardware were too new for that and needed at least 4.x. Ubuntu 16.04 through its HWE support provides from 4.4 to 4.10.
One question : I didn't see any x2gothinclient_init, x2gothinclient_start file in /etc/x2go in this image ... where is the client configured and where can I add my broker settings ?
Regards, Walid Moghrabi
TRAVAUX.COM BAT I - PARC CEZANNE 2 290 AVENUE GALILEE - CS 80403 13591 AIX EN PROVENCE CEDEX 3
----- Mail original -----
De: "Stefan Baur" <X2Go-ML-1@baur-itcs.de> À: "Ulrich Sibiller" <uli42@gmx.de> Cc: "Walid MOGHRABI" <w.moghrabi@servicemagic.eu>, 1197@bugs.x2go.org Envoyé: Mercredi 26 Juillet 2017 11:38:28 Objet: Re: Bug#1197: Multihead fullscreen not working with TCE client in displaymanager mode
Am 26.07.2017 um 11:26 schrieb Ulrich Sibiller:
While you are right in principle you need to consider what complicates the issue here: Walid is using nx-libs 3.5.99.x. So have you tested with them, too? If we knew if XINERAMA it is working properly even with beta nx-libs this would definitely help!
No, we haven't tested that combination, as our customer runs the stable release. But: Our images are available to everyone and known to work against stable, so those should be the starting point for all tests.
If/Once these images play nice with 3.5.99.x, we can start taking a look at why forks/homegrown scripts don't work. Until then, it's a wild-goose chase.
-Stefan
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
Am 26.07.2017 um 11:48 schrieb Walid MOGHRABI:
By the way, another reason why I wanted to go Ubuntu and not Debian is the kernel support ... Debian provides 3.16 (in Jessie) and some of our test hardware were too new for that and needed at least 4.x. Ubuntu 16.04 through its HWE support provides from 4.4 to 4.10.
One question : I didn't see any x2gothinclient_init, x2gothinclient_start file in /etc/x2go in this image ... where is the client configured and where can I add my broker settings ?
It all happens via boot parameters. Please see <https://wiki.x2go.org/doku.php/doc:howto:tce#boot_parameters_for_x2go-tce>
For newer kernels, Debian Stretch comes with 4.9, if I'm not mistaken, and there probably are newer kernels available in the backports repository. We don't offer ready-made images for Stretch yet, but there is the feature/stretch branch used by my TCE-Live co-maintainer Juri Grabowski, so TCE-Live should work on Stretch, too. (Yet another reason you should attend the Gathering - and bring your demo setup - as Uli and Juri will be there in person, together with me.)
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
Hi again,
Just to add a few more informations, here is the xrandr output taken from the TCE itself (not from within the x2go session) :
As you can see, both monitors are perfectly detected.
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" <w.moghrabi@servicemagic.eu> À: uli42@gmx.de Cc: 1197@bugs.x2go.org Envoyé: Mercredi 26 Juillet 2017 10:35:22 Objet: [X2Go-Dev] Bug#1197: Multihead fullscreen not working with TCE client in displaymanager mode
Hi guys,
Just to give a bit more informations on my TCE setup : it is not based on the live-build scripts because it is not well suited for Ubuntu 16.04 and to be honest, I never managed to get a working live build that way so I gave up. My TCE image is more or less a tweaked ubuntu 16.04 debbotstrapped image with x2gothinclient-displaymanager installed (+ a few more things but really, this is a pretty basic ubuntu server image + x2gothinclient installed)
By the way, Stefan put the finger on one point : in /usr/sbin/x2gothinclientd, I commented the whole randr stuff block (from line 114 to line 175) to make a try then restarted the x2gothinclient-displaymanager but while it didn't fix my multimonitor support within the X2Go session, it fixed a bad ordering of the monitors. Before that, my monitors were inverted (right was left and left was right), commenting this block lead to right ordering of the monitors this time.
Concerning your test Uli, doing "Ctrl+Alt+F" within the X2Go session on the TCE did nothing. I don't know if it was meant to do anything but I did it many times following the action by a xrandr output in the console, nothing changed, same values all the time (one big screen, not 2)
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" <ulrich.sibiller@gmail.com> À: "Stefan Baur" <X2Go-ML-1@baur-itcs.de> Cc: 1197@bugs.x2go.org, "Walid MOGHRABI" <w.moghrabi@servicemagic.eu> Envoyé: Mardi 25 Juillet 2017 22:11:28 Objet: Re: Bug#1197: Multihead fullscreen not working with TCE client in displaymanager mode
On Tue, Jul 25, 2017 at 6:55 PM, Stefan Baur <X2Go-ML-1@baur-itcs.de> wrote:
Hi folks,
Just an idea - some XRANDR-related stuff that is specific to X2Go-TCE-Live is happening in this file:
Which, in turn, was inspired by this file from X2Go-TCE-Classic (NFS):
As this is specific to the TCEs, maybe this is the root cause of the difference you're seeing?
Hmmm, I doubt that. Usings NX the client side is not really doing anything X wise. It's the nxagent that calls XineramaQueryScreens(). It asks the client side X server (the real X server) for its Xinerama configuration. We have learned from the previous outputs that Walis had sent that the real X server does not have Xinerama configured. Therefore the agent does not see any Xinerama configuration. (The only possible exception to this would be nxproxy running with LD_PRELOAD of libfakexinerama.so which is not happening here.)
Now, in the Laptop scenario you can see via xrandr that nxagent has gotten the Xinerama information somehow. Otherwise it would not have been possible to setup two NX outputs/monitors/heads.
The two logfiles are almost the same except the last line where the in the Laptop scenario you can see this line
Info: Screen [0] resized to geometry [3840x1080] fullscreen [1].
This line is printed if nxagent has received and processed a sizing event. In the TCE scenario no sizing event was sent to nxagent which - if really true - is probably the TCE window manager's fault.
Walid, can you please try pressing CTRL-ALT-F twice in the TCE scenario? What is xrandr showing afterwards?
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