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
On Wed, May 16, 2018 at 2:50 PM, Oleksandr Shneyder
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~git201805
* On 05/16/2018 10:22 PM, Stefan Baur wrote:
> Does that mean it would also work with older NX-Lib versions, like 3.5.0.33?
No. That's a new feature that has been introduced in the 3.5.99.x line only.
Mihai
signature.asc
Description: OpenPGP digital signature
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 me
On Wed, May 16, 2018 at 4:35 PM, Ulrich Sibiller
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 toggl
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 i
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 di
We can add that to the options string, so it can be switched depending on
the client's preference. No big deal...
Stefan Baur 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
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 worki
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
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
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 AVEN
> As I said, it also happens in TCE-Live, though only sometimes.
> Hwevrr ... 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
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)
G
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 schrieb am Mi., 16. Mai 2018, 15:25:
> Am 16.05.2018 um 15:11 schr
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 :
>
>
>
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 :
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 Rega
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
Hi Mike,
I don't understand, why do you need to do this so complicated. Broker
just should return correct exit status after changing password to signal
if everything went ok. After password change it supposed to give answer
which could be parsed by function checkAccess.
so if in slotPassChanged "
20 matches
Mail list logo