Hi Paul,
On So 23 Nov 2014 03:19:24 CET, paul.szabo wrote:
Dear Mike,
I know there is "one last remaining bug" in nxproxy; I have not been
able to find it. I will now stop working on nxproxy, and start using
"ssh -C" instead: seems to provide similar performance, is well tested,
and is less l
Dear Mike,
I know there is "one last remaining bug" in nxproxy; I have not been
able to find it. I will now stop working on nxproxy, and start using
"ssh -C" instead: seems to provide similar performance, is well tested,
and is less likely to cause problems seeing how it does not mess much
with th
Hi Paul,
- Original message -
> Dear Mike,
>
> > The nxproxy built for X2Go does not get built against libX11 from Xorg
> > but against libNX_X11 [1] from NoMachine.
> > Will this break the GenericEvents part of your patch? Or does it
> > simply require a patch in libNX_X11?
>
> Please
Dear Mike,
> The nxproxy built for X2Go does not get built against libX11 from Xorg
> but against libNX_X11 [1] from NoMachine.
> Will this break the GenericEvents part of your patch? Or does it
> simply require a patch in libNX_X11?
Please update your libNX_X11 file. (Seems you took a copy of s
Hi Paul,
On Fr 14 Nov 2014 21:40:26 CET, paul.szabo wrote:
Dear Mike,
Unfortunately, your patch does not build cleanly (FTBFS!).
https://jenkins.x2go.org:8443/view/NX/job/nx-libs+nightly+debian-sid/63/console
Any idea why?
The "actual error" is shown towards the end of that .../console :
Dear Mike,
Seems that I found a reproducible way of getting nxproxy confused: start
/usr/bin/chromium then (at some stage) use ctrl-W to close its window:
the window will not close but become "empty and transparent", and
"nxproxy -C" will show an (endless?) stream of complaints
Proxy: WARNING! H
Dear Mike,
> Unfortunately, your patch does not build cleanly (FTBFS!).
> https://jenkins.x2go.org:8443/view/NX/job/nx-libs+nightly+debian-sid/63/console
> Any idea why?
The "actual error" is shown towards the end of that .../console :
ClientChannel.cpp:5444:33: error: 'GenericEvent' was not d
Hi Paul,
On Do 13 Nov 2014 23:33:03 CET, Mike Gabriel wrote:
Dear Paul,
On Mi 12 Nov 2014 21:22:51 CET, Paul Szabo wrote:
Dear Mike,
My current patches, for BIG-REQUESTS and Generic Event Extension, below.
With these, nxproxy works well. (Though, once a crash was observed,
unfortunately n
Dear Paul,
On Mi 12 Nov 2014 21:22:51 CET, Paul Szabo wrote:
Dear Mike,
My current patches, for BIG-REQUESTS and Generic Event Extension, below.
With these, nxproxy works well. (Though, once a crash was observed,
unfortunately not "trapped" or de-bugged, yet...)
Some other patches, that make
Dear Mike,
> Do you mean, I should rather still wait with applying your patch
> upstream? Need more testing? Or do you actually say that the patch
> is stable and the crash has been related to something else?
I believe the patches I sent are correct and stable; but that there
lurks some other an
Hi Paul,
On Do 13 Nov 2014 04:19:24 CET, paul.szabo wrote:
A user just reported to me:
Just had an nxproxy crash, running Dropbox, nautilus, firefox, and gedit.
Didn't start any particular process when it crashed.
[xcb] Unknown sequence number while processing queue
[xcb] Most likely this i
A user just reported to me:
> Just had an nxproxy crash, running Dropbox, nautilus, firefox, and gedit.
> Didn't start any particular process when it crashed.
>
> [xcb] Unknown sequence number while processing queue
> [xcb] Most likely this is a multi-threaded client and XInitThreads has not
> bee
Dear Mike,
My current patches, for BIG-REQUESTS and Generic Event Extension, below.
With these, nxproxy works well. (Though, once a crash was observed,
unfortunately not "trapped" or de-bugged, yet...)
Some other patches, that make nxproxy more useful in my environment,
below also (hoping others
Hi Paul,
On Fr 07 Nov 2014 10:50:33 CET, paul.szabo wrote:
Dear Mike,
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?
Pre-empting anything below: I have now added code to nxpro
Dear Mike,
>> 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?
Pre-empting anything below: I have now added code to nxproxy to
correctly handle (support) "X Generic Event Exte
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/X11
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-su
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.
Cheers, Paul
Paul Szabo p...@maths.usyd.edu.au http://www.maths.usyd.edu.au/u/psz/
School of Mathematics and Statistics University of SydneyAustrali
On So 02 Nov 2014 22:12:00 CET, paul.szabo wrote:
Dear Mike,
While looking into the handling of sequence numbers, I notice:
http://www.x.org/releases/X11R7.7/doc/xproto/x11protocol.html
... Every request on a given connection is implicitly assigned
a sequence number, starting with o
19 matches
Mail list logo
