The magic pixel can be disabled in nxagent 3.5.99.16. I am wondering why the the WM is relevant. Nxagent is talking to the X server and not the WM. So what does xrandr report on the tce side with and without WM? Uli Stefan Baur <X2Go-ML-1@baur-itcs.de> schrieb am Mi., 16. Mai 2018, 15:25:
Am 16.05.2018 um 15:11 schrieb Walid MOGHRABI:
This is a known bug I encountered and this is due to the lack of Window Manager. Apparently, the WM is needed to have a good working xinerama.
I fixed this by installing OpenBox in my TCE image and added this line :
============================================================================================
--- /usr/sbin/x2gothinclientd +++ /usr/sbin/x2gothinclientd @@ -175,6 +175,9 @@ } }
# Spawn openbox
system("su - x2gothinclient -c \"DISPLAY=:0 openbox &\"");
detected screens `DISPLAY=:0 xsetroot -solid "#246ed8"`;# set screen background to X2Go default blue on all
============================================================================================
I also did a few modifications to /etc/xdg/openbox/rc.xml to disable
windows borders and a few stuff ... in fact these are just modifications you can find in the TCE Live Build project.
Please find my rc.xml attached.
Once you do this, everything works just like on your desktop.
... or not.
As I said, it also happens in TCE-Live, though only sometimes. Hooooweveeeerr ... we include code to kill openbox once the NX window comes up, so that the dreaded magic pixel won't trigger.
Maybe the act of disabling sometimes happens too soon, and we get a race condition between the xinerama components and the magic-pixel-workaround.
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