Hi guys,
I have a strange issue. The Xinerama works well in full screen mode, when x2goclient is started on desktop, but doesn't work if x2goclient is started from TCE. It's the same version of client: 4.1.2.0-0x2go1~git20180514.1774+9.heuler.1 and same version of Debian - stretch. Session config identical as well.
xrandr output inside of X2Go session is different though:
desktop:
Screen 0: minimum 320 x 240, current 4480 x 1080, maximum 4480 x 1200 NX1 connected 1920x1080+2560+0 0mm x 0mm nx_1920x1080 60.00* NX2 connected 2560x1080+0+0 0mm x 0mm
TCE:
Screen 0: minimum 320 x 240, current 2560 x 1024, maximum 2560 x 1200 default connected 2560x1024+0+0 0mm x 0mm 1360x768 60.00 320x240 60.00 1024x600 60.00 1280x800 60.00 1600x900 60.00 1600x1200 60.00
Although if session is started from TCE, I'm getting error dialog from /etc/x2go/Xsession.d/20x11-common_process-args: "unsupported number of arguments (3); falling back to default"
before I'm starting to look for the reason, maybe someone who tweaked on Xinerama or on x2go server have any idea why it's happening?
regards, Alex
--
Oleksandr Shneyder | Email: o.shneyder@phoca-gmbh.de phoca GmbH | Tel. : 0911 - 14870374 0 Harzstr. 4 | Fax. : 0911 - 14870374 9 D-90491 Nürnberg | Mobil: 0163 - 49 64 461
Geschäftsführung: Dipl.-Inf. Oleksandr Shneyder
Amtsgericht München | http://www.phoca-gmbh.de HRB 196 658 | http://www.x2go.org USt-IdNr.: DE281977973
Hi Alex,
Sorry, no solution yet, but we ran into the same issue yesterday/today (with TCE-Live, not NFS). What's worse is that it happens sometimes, but not always. At first we thought it depended on the Desktop Environment/Window Manager, but it seems to be a different issue than that.
Kind Regards, Stefan Baur
Am 16.05.2018 um 14:50 schrieb Oleksandr Shneyder:
Hi guys,
I have a strange issue. The Xinerama works well in full screen mode, when x2goclient is started on desktop, but doesn't work if x2goclient is started from TCE. It's the same version of client: 4.1.2.0-0x2go1~git20180514.1774+9.heuler.1 and same version of Debian - stretch. Session config identical as well.
xrandr output inside of X2Go session is different though:
desktop:
Screen 0: minimum 320 x 240, current 4480 x 1080, maximum 4480 x 1200 NX1 connected 1920x1080+2560+0 0mm x 0mm nx_1920x1080 60.00* NX2 connected 2560x1080+0+0 0mm x 0mm
TCE:
Screen 0: minimum 320 x 240, current 2560 x 1024, maximum 2560 x 1200 default connected 2560x1024+0+0 0mm x 0mm 1360x768 60.00 320x240 60.00 1024x600 60.00 1280x800 60.00 1600x900 60.00 1600x1200 60.00
Although if session is started from TCE, I'm getting error dialog from /etc/x2go/Xsession.d/20x11-common_process-args: "unsupported number of arguments (3); falling back to default"
before I'm starting to look for the reason, maybe someone who tweaked on Xinerama or on x2go server have any idea why it's happening?
regards, Alex
x2go-dev mailing list x2go-dev@lists.x2go.org https://lists.x2go.org/listinfo/x2go-dev
-- 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 Stefan, Alex,
On Mi 16 Mai 2018 15:00:33 CEST, Stefan Baur wrote:
Hi Alex,
Sorry, no solution yet, but we ran into the same issue yesterday/today (with TCE-Live, not NFS). What's worse is that it happens sometimes, but not always. At first we thought it depended on the Desktop Environment/Window Manager, but it seems to be a different issue than that.
Kind Regards, Stefan Baur
Same issue here with pyhoca-cli and Arctica Greeter's remote logon feature.
I'll read the full scope of this mail thread and join in tomorrow...
Mike
DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby mobile: +49 (1520) 1976 148 landline: +49 (4354) 8390 139
GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
Am 17.05.2018 um 13:02 schrieb Mike Gabriel:
Same issue here with pyhoca-cli and Arctica Greeter's remote logon feature.
I'll read the full scope of this mail thread and join in tomorrow...
TL;DR: No local Window Manager equals no working XINERAMA.
TCE-NFS has none, so fails.
TCE-Live comes with one (OpenBox), so works when OpenBox is running.
If you enable the magicpixel-workaround in TCE-Live, OpenBox will be killed once the NX-Window opens (because without a Window Manager, the magicpixel's minimize request is ignored). This is sometimes too soon for XINERAMA, it seems, that's why XINERAMA will occasionally fail on TCE-Live.
The solution is probably to disable MP on the Server and disable the workaround, to keep OpenBox running all the time. $SOON, it will be possible to disable MP on the client side, so no server-side actions will be needed.
Having OpenBox (or any other WM) active brings additional advantages, like window decoration and text field focus for X2GoClient's interactive popups, so I strongly suggest going the "we need a WM" way, rather than trying to "fix" this somewhere else in the code, with possible new side effects.
-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
On Thu, May 17, 2018 at 1:52 PM, Stefan Baur <X2Go-ML-1@baur-itcs.de> wrote:
Am 17.05.2018 um 13:02 schrieb Mike Gabriel:
Same issue here with pyhoca-cli and Arctica Greeter's remote logon feature.
I'll read the full scope of this mail thread and join in tomorrow...
TL;DR: No local Window Manager equals no working XINERAMA.
TCE-NFS has none, so fails.
TCE-Live comes with one (OpenBox), so works when OpenBox is running.
If you enable the magicpixel-workaround in TCE-Live, OpenBox will be killed once the NX-Window opens (because without a Window Manager, the magicpixel's minimize request is ignored). This is sometimes too soon for XINERAMA, it seems, that's why XINERAMA will occasionally fail on TCE-Live.
I am suspecting this has to do with the fact that openbox is the first client to TCEs X server. Can someone try and run an xterm/xclock/xlogo/whatever (and no WM) prior to x2goclient?
Uli
Am 17.05.2018 um 13:59 schrieb Ulrich Sibiller:
I am suspecting this has to do with the fact that openbox is the first client to TCEs X server. Can someone try and run an xterm/xclock/xlogo/whatever (and no WM) prior to x2goclient?
What would you expect to happen when another application is the first client? (Just so testers know what to look for ...)
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
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 &\""); + # set screen background to X2Go default blue on all detected screens `DISPLAY=:0 xsetroot -solid "#246ed8"`; ============================================================================================ 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. I would really suggest to include that modification and dependencies in the x2gothinclient-displaymanager package. Regards, Walid Moghrabi TRAVAUX.COM BAT I - PARC CEZANNE 2 290 AVENUE GALILEE - CS 80403 13591 AIX EN PROVENCE CEDEX 3 ----- Mail original ----- De: "Oleksandr Shneyder" <o.shneyder@phoca-gmbh.de> À: x2go-dev@lists.x2go.org Envoyé: Mercredi 16 Mai 2018 14:50:52 Objet: [X2Go-Dev] Different behavior of X2Go Client from Desktop and TCE Hi guys, I have a strange issue. The Xinerama works well in full screen mode, when x2goclient is started on desktop, but doesn't work if x2goclient is started from TCE. It's the same version of client: 4.1.2.0-0x2go1~git20180514.1774+9.heuler.1 and same version of Debian - stretch. Session config identical as well. xrandr output inside of X2Go session is different though: desktop: Screen 0: minimum 320 x 240, current 4480 x 1080, maximum 4480 x 1200 NX1 connected 1920x1080+2560+0 0mm x 0mm nx_1920x1080 60.00* NX2 connected 2560x1080+0+0 0mm x 0mm TCE: Screen 0: minimum 320 x 240, current 2560 x 1024, maximum 2560 x 1200 default connected 2560x1024+0+0 0mm x 0mm 1360x768 60.00 320x240 60.00 1024x600 60.00 1280x800 60.00 1600x900 60.00 1600x1200 60.00 Although if session is started from TCE, I'm getting error dialog from /etc/x2go/Xsession.d/20x11-common_process-args: "unsupported number of arguments (3); falling back to default" before I'm starting to look for the reason, maybe someone who tweaked on Xinerama or on x2go server have any idea why it's happening? regards, Alex -- ----------------------------------------------------------- Oleksandr Shneyder | Email: o.shneyder@phoca-gmbh.de phoca GmbH | Tel. : 0911 - 14870374 0 Harzstr. 4 | Fax. : 0911 - 14870374 9 D-90491 Nürnberg | Mobil: 0163 - 49 64 461 Geschäftsführung: Dipl.-Inf. Oleksandr Shneyder Amtsgericht München | http://www.phoca-gmbh.de HRB 196 658 | http://www.x2go.org USt-IdNr.: DE281977973 ----------------------------------------------------------- _______________________________________________ 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
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 openboxsystem("su - x2gothinclient -c \"DISPLAY=:0 openbox &\"");# set screen background to X2Go default blue on all detected screens `DISPLAY=:0 xsetroot -solid "#246ed8"`;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
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 openboxsystem("su - x2gothinclient -c \"DISPLAY=:0 openbox &\"");# 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
Am 16.05.2018 um 15:48 schrieb Ulrich Sibiller:
The magic pixel can be disabled in nxagent 3.5.99.16.
Yes, but AFAIK X2GoClient doesn't make use of that feature in 4.1.1.1. (I may be mistaken, though, so feel free to correct 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
I don't know, the only thing I know for sure is the fact that without adding a WM, it never worked. Anyway, adding OpenBox and tweaking its conf is really nothing to do so I would say this is an acceptable fix for the TCE mode. 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: x2go-dev@lists.x2go.org Envoyé: Mercredi 16 Mai 2018 15:48:54 Objet: Re: [X2Go-Dev] Different behavior of X2Go Client from Desktop and TCE 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 &\"");
set screen background to X2Go default blue on all detected screens
`DISPLAY=:0 xsetroot -solid "#246ed8"`;
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 _______________________________________________ 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
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.
MagicPixel is not a problem anymore. I filed a feature request which has been done to add a parameter to disable this behaviour directly at the nx level. Just add the "-nomagicpixel" option in x2goagent.options 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> À: x2go-dev@lists.x2go.org Envoyé: Mercredi 16 Mai 2018 15:19:00 Objet: Re: [X2Go-Dev] Different behavior of X2Go Client from Desktop and TCE 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 &\"");
set screen background to X2Go default blue on all detected screens
`DISPLAY=:0 xsetroot -solid "#246ed8"`;
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 --- 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 16.05.2018 um 15:52 schrieb Walid MOGHRABI:
MagicPixel is not a problem anymore. I filed a feature request which has been done to add a parameter to disable this behaviour directly at the nx level. Just add the "-nomagicpixel" option in x2goagent.options
Wait, that's on the server side and a per-server setting? That's not where this should go. This SHOULD be a client-side option, triggered e.g. by X2GoClient being called with "--thinclient", and active otherwise.
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
It has been done at the server side (this is not the default behaviour anyway and this is optionnal) because this was the easiest way to do it and as far as I'm concerned, this is what I want since I have a dedicated TCE server farm and there is no reason for my TCEs to have this MagicPixel sh*t and the workaround (which has the merit to exist) is as ugly as the "bug" itself.
To me, disabling MagicPixel (which is something barely useful) at the server side is perfect. Feel free to give me a use case where this should be kept, I don't see any on my side.
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: x2go-dev@lists.x2go.org, "ionic >> Mihai Moldovan" <ionic@ionic.de> Envoyé: Mercredi 16 Mai 2018 15:55:55 Objet: Re: [X2Go-Dev] Different behavior of X2Go Client from Desktop and TCE
Am 16.05.2018 um 15:52 schrieb Walid MOGHRABI:
MagicPixel is not a problem anymore. I filed a feature request which has been done to add a parameter to disable this behaviour directly at the nx level. Just add the "-nomagicpixel" option in x2goagent.options
Wait, that's on the server side and a per-server setting? That's not where this should go. This SHOULD be a client-side option, triggered e.g. by X2GoClient being called with "--thinclient", and active otherwise.
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
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 16.05.2018 um 16:07 schrieb Walid MOGHRABI:
To me, disabling MagicPixel (which is something barely useful) at the server side is perfect. Feel free to give me a use case where this should be kept, I don't see any on my side. The use case is a mixed environment, where people are working from regular workstations (Windows, macOS, Linux) as well as TCE terminals.
Working on a regular workstation, the magic pixel is actually handy, because you can use it to go back to your local desktop without leaving fullscreen mode - remember that on Windows, Ctrl+Alt+F is broken (causes a VcXsrv crash).
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
We can add that to the options string, so it can be switched depending on the client's preference. No big deal...
Stefan Baur <X2Go-ML-1@baur-itcs.de> schrieb am Mi., 16. Mai 2018, 16:25:
Am 16.05.2018 um 16:07 schrieb Walid MOGHRABI:
To me, disabling MagicPixel (which is something barely useful) at the server side is perfect. Feel free to give me a use case where this should be kept, I don't see any on my side. The use case is a mixed environment, where people are working from regular workstations (Windows, macOS, Linux) as well as TCE terminals.
Working on a regular workstation, the magic pixel is actually handy, because you can use it to go back to your local desktop without leaving fullscreen mode - remember that on Windows, Ctrl+Alt+F is broken (causes a VcXsrv crash).
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
Ok, installing WM just to make Xinerama work doesn't seem to be a right solution for me. On the client site everything looks good. X2Go Client creating correct xinerama.conf and sending correct options to x2goagent. So I guess the problem is in NX-Xinerama code. I'll have a look and will see how difficult is to fix it.
Regards Alex
Am 16.05.18 um 16:35 schrieb Ulrich Sibiller:
We can add that to the options string, so it can be switched depending on the client's preference. No big deal...
Stefan Baur <X2Go-ML-1@baur-itcs.de <mailto:X2Go-ML-1@baur-itcs.de>> schrieb am Mi., 16. Mai 2018, 16:25:
Am 16.05.2018 um 16:07 schrieb Walid MOGHRABI: > To me, disabling MagicPixel (which is something barely useful) at the server side is perfect. > Feel free to give me a use case where this should be kept, I don't see any on my side. The use case is a mixed environment, where people are working from regular workstations (Windows, macOS, Linux) as well as TCE terminals. Working on a regular workstation, the magic pixel is actually handy, because you can use it to go back to your local desktop without leaving fullscreen mode - remember that on Windows, Ctrl+Alt+F is broken (causes a VcXsrv crash). 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 <mailto: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
--
Oleksandr Shneyder | Email: o.shneyder@phoca-gmbh.de phoca GmbH | Tel. : 0911 - 14870374 0 Harzstr. 4 | Fax. : 0911 - 14870374 9 D-90491 Nürnberg | Mobil: 0163 - 49 64 461
Geschäftsführung: Dipl.-Inf. Oleksandr Shneyder
Amtsgericht München | http://www.phoca-gmbh.de HRB 196 658 | http://www.x2go.org USt-IdNr.: DE281977973
Am 16.05.2018 um 19:28 schrieb Oleksandr Shneyder:
Ok, installing WM just to make Xinerama work doesn't seem to be a right solution for me. On the client site everything looks good. X2Go Client creating correct xinerama.conf and sending correct options to x2goagent. So I guess the problem is in NX-Xinerama code. I'll have a look and will see how difficult is to fix it.
Alex,
having a WM (openbox) in TCE is useful for a lot more than just XINERAMA. Think Popups for SSH-Private-Key passwords and for "wrong password, try again" or "no route to host", etc. They all come up god knows where and worst case, when I first ran into the issue, it was impossible to focus on the password field, so all I could do was reboot the client and try again - it wouldn't let me enter the password. Life is so much easier when they have a window decoration and can get a focus ...
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, May 16, 2018 at 4:35 PM, Ulrich Sibiller <ulrich.sibiller@gmail.com> wrote:
We can add that to the options string, so it can be switched depending on the client's preference. No big deal...
Turns out that feature is already present in nxagent. You can use -nomagicpixel on nxagent's command line and you can toggle the magic pixel by using magicpixel=0/1 in the options string. So all that's missing is support in x2go.
Uli
Am 16.05.2018 um 22:08 schrieb Ulrich Sibiller:
Turns out that feature is already present in nxagent. You can use -nomagicpixel on nxagent's command line and you can toggle the magic pixel by using magicpixel=0/1 in the options string. So all that's missing is support in x2go.
Does that mean it would also work with older NX-Lib versions, like 3.5.0.33?
-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 all,
On Mi 16 Mai 2018 15:11:30 CEST, Walid MOGHRABI wrote:
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.
since today, this is not true anymore. The nxagent now also supports
Xinerama without a running WM.
The merge of this PR fixed the issue. https://github.com/ArcticaProject/nx-libs/pull/695
Thus, you might want to ponder de-complicating the TCE code in that
respect. However, a WM does not hurt. The workaround is just not
needed anymore.
Greets, Mike
DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby mobile: +49 (1520) 1976 148 landline: +49 (4354) 8390 139
GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
Am 24.05.2018 um 11:25 schrieb Mike Gabriel:
Thus, you might want to ponder de-complicating the TCE code in that respect. However, a WM does not hurt. The workaround is just not needed anymore.
The WM is not needed for Xinerama any more - but still for window decoration and focus, unless you want to degrade user experience in case of popups (yes, in a perfect world, we wouldn't have popups, but sometimes, there's no route to host, there's a wrong password, there's a private key file that needs to have its passphrase entered, ...).
-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
I agree, adding a minimalistic WM in the TCE setup is not cosmetic, anyway, this is nice that this bug is now fixed :)
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> À: x2go-dev@lists.x2go.org Envoyé: Jeudi 24 Mai 2018 11:52:04 Objet: Re: [X2Go-Dev] Different behavior of X2Go Client from Desktop and TCE
Am 24.05.2018 um 11:25 schrieb Mike Gabriel:
Thus, you might want to ponder de-complicating the TCE code in that respect. However, a WM does not hurt. The workaround is just not needed anymore.
The WM is not needed for Xinerama any more - but still for window decoration and focus, unless you want to degrade user experience in case of popups (yes, in a perfect world, we wouldn't have popups, but sometimes, there's no route to host, there's a wrong password, there's a private key file that needs to have its passphrase entered, ...).
-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
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
On Wed, May 16, 2018 at 2:50 PM, Oleksandr Shneyder <o.shneyder@phoca-gmbh.de> wrote:
Hi guys,
I have a strange issue. The Xinerama works well in full screen mode, when x2goclient is started on desktop, but doesn't work if x2goclient is started from TCE. It's the same version of client: 4.1.2.0-0x2go1~git20180514.1774+9.heuler.1 and same version of Debian - stretch. Session config identical as well.
xrandr output inside of X2Go session is different though:
desktop:
Screen 0: minimum 320 x 240, current 4480 x 1080, maximum 4480 x 1200 NX1 connected 1920x1080+2560+0 0mm x 0mm nx_1920x1080 60.00* NX2 connected 2560x1080+0+0 0mm x 0mm
So your client side has 2 displayss
TCE:
Screen 0: minimum 320 x 240, current 2560 x 1024, maximum 2560 x 1200 default connected 2560x1024+0+0 0mm x 0mm 1360x768 60.00 320x240 60.00 1024x600 60.00 1280x800 60.00 1600x900 60.00 1600x1200 60.00
This indicates you are only having one screen. Is this true in that setup?
Also, I just remembered there's some xrandr magic going on in TCE mode that _might_ mess things up for you. Have a look at lib/live/config/2800-x2go-thinclientconfig.
Although if session is started from TCE, I'm getting error dialog from /etc/x2go/Xsession.d/20x11-common_process-args: "unsupported number of arguments (3); falling back to default"
Sorry, no idea. (the arguments are the ones for Xsession, if I get that right. Which only supports 0 or 1 argument)
Uli
Am 16.05.2018 um 22:57 schrieb Ulrich Sibiller:
Also, I just remembered there's some xrandr magic going on in TCE mode that _might_ mess things up for you. Have a look at lib/live/config/2800-x2go-thinclientconfig.
I think you mean 2900. (We increased that count by 100 a while ago.)
And the xrandr code in there is actually based on <https://code.x2go.org/gitweb?p=x2gothinclient.git;a=blob_plain;f=displaymanager/sbin/x2gothinclientd;h=6897d42d17bd6778e7de5e62ec3f51727d4e8800;hb=HEAD>
Both the perl original and the bash clone have a nice explanation of what that code is doing - aligning displays in the order specified, and making sure clone mode is active if all you have is a touchscreen (on one surface) and no additional pointing device like a mouse (because in that case, you would either be unable to reach the areas on the non-touch-enabled screen with your pointing device, or the touch-sensitive area would be totally out of sync with what's displayed on 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
-
Mihai Moldovan -
Mike Gabriel -
Oleksandr Shneyder -
Stefan Baur -
Ulrich Sibiller -
Walid MOGHRABI