Hi Paul,

On  Mi 05 Nov 2014 21:43:15 CET, paul.szabo wrote:

I just wrote:
  Further testing suggests that as nautilus is about to die, it gets a
  GenericEvent opcode=35 and then an event with opcode=0, then it dies.
Maybe the issue is
  X Generic Event Extension
  http://www.x.org/releases/X11R7.7/doc/xextproto/geproto.html
of variable length, as yet un-supported by nxproxy?

the question here again is if nautilus crashes

  (a) in nxagent scenarios
  (b) in nxproxy -S + Xvfb/Xephyr scenarios

While writing the above... Does nautilus directly bind to nxproxy -S or do you have a Xephyr (or Xvfb) xserver instance that nautilus then runs in / crashes in?

Do you test nautilus in some desktop shell (e.g. GNOMEv3) or do you launch nautilus as a standalone (aka rootless, seamless) application?

If server-side applications bind to nxproxy -S directly, then the code path (very roughly speaking) should be:

  (1) nautilus
  (1.1) libcairo
  (1.2) lib-X.Org's client extensions (e.g. libXext, libXrandr, etc.)
  (2) nxproxy -S
  (3) nxproxy -C
  (4) X.org server on client-side

So, basically, nxproxy should allow pass-through of everything that libx11-* produces and it should be proxies through to the client side X.org. On the other hand, when Debian wheezy was in its final testing phase, we had loads of NX breakage (nxagent, that was) by libcairo.

Do you see anything in the session logs of nxproxy (or in the debug output if enabled at build time) that alludes to nxproxy being the cause of those crashes?

Also, nautilus may request some extension not supported on our client-side system. Or request an extension version that's not available. (This is more likely, when nautilus runs on top of nxagent, though).

Can you detect where in nautilus the crash occurs? It may be helpful looking at the nautilus / libcairo code that causes the crash.

Greets,
Mike


--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb

Attachment: pgppiYQYfh9rI.pgp
Description: Digitale PGP-Signatur

Reply via email to