Ulrich Sibiller

Hmm, this posting states that it happens for gcc < 4.6 which is not the same as >= 4.5: https://stackoverflow.com/questions/60441165/stackless-python-pragma-gcc-diagnostic-not-allowed-inside-functions So what's the exact comparison value? On Mon, Jan 31,...

Note that there's 1.7.5 now

There are three types of packages here: a) *dbg* - debuginfo packages, required if you want to debug the installed nx packages with a debugger b) *dev* - development packages,...

I am sorry that you did not get a reaction to this so far - I just detected it today and will have a look at it

I have seen this again today: Server 3.5.99.21, client 3.5.99.22

I looks to me as the main problem is that nxagent is creating ALL atoms on the real X server, so there's no way to distinguish an nxagent from a...

I think the whole approach of using atoms (and their order) is wrong as long as nxagent creates the atoms on the remote side itself. This will create the atoms...

Either check for the NXAGENT_VERSION property on the root window of the X server or prevent forwarding of the NXAGENT_SIGNATURE and/or NX_IDENTITY atom.

I have not checked this. AFAIU this is only needed when you close all clients. Normally Xnest will stay alive and not close down the Display connection. With FullGeneration it...

I am aware of that code. But if I keep all that logic this patch does not make any sense, as I have to keep most of the code.