Please see the nxproxy bug
http://bugs.debian.org/766299
about the "X Generic Event Extension"
http://www.x.org/releases/X11R7.7/doc/xextproto/geproto.html
that would need to be supported also, to make dxpc useable.
(I do not provide patches: nxproxy is probably "better" ...
and nxproxy still has,
Please see
http://bugs.debian.org/766299
about the same bug in nxproxy.
Cheers, Paul
Paul Szabo p...@maths.usyd.edu.au http://www.maths.usyd.edu.au/u/psz/
School of Mathematics and Statistics University of SydneyAustralia
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.deb
I wrote:
Comparing dxpc with "ssh -X -C", ssh achieves fewer bytes ...
Is that because dxpc uses LZO compression, while ssh uses zlib (==gzip),
and LZO is known to have better speed but provide less compression?
Or is it because it would be better to forget about the intricacies of
the X protoc
I propose the following patch to support BIG-REQUESTS. Please review.
Cheers, Paul
Paul Szabo p...@maths.usyd.edu.au http://www.maths.usyd.edu.au/u/psz/
School of Mathematics and Statistics University of SydneyAustralia
--- ClientChannel.C-prePSz 2007-02-03 01:25:48.0 +1100
+++
Comparing dxpc with "ssh -X -C", ssh achieves fewer bytes transmitted on
the network. Should not dxpc be at least as good, and maybe (surely!)
better?
Cheers, Paul
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@
I wrote:
... lack of support for BIG-REQUESTS ... working on a solution...
I tried the easy "cheat" ways:
- Turn off support for that extension in the X server, e.g. with
some settings in xorg.conf. But that does not seem to work, e.g.:
psz@como:~$ Xorg -extension BIG-REQUESTS
[mi
I now believe the issue is caused by lack of support for BIG-REQUESTS
(the Big Requests Extension)
http://www.x.org/releases/X11R7.7/doc/bigreqsproto/bigreq.html
in dxpc. (I am working on a solution... will see how that goes.)
Cheers, Paul
Paul Szabo p...@maths.usyd.edu.au http://www.maths.us
Dear Jay,
OK, will contact the upstream author now. (Naively I had thought you
would do that...)
Cheers, Paul
Paul Szabo p...@maths.usyd.edu.au http://www.maths.usyd.edu.au/u/psz/
School of Mathematics and Statistics University of SydneyAustralia
--
To UNSUBSCRIBE, email to debian-b
paul.sz...@sydney.edu.au wrote:
> Looking at the code around line 181 in ClientChannel.C where the
> crash happened, seems to me that format should have one of the
> values 8, 32 and maybe 16. Re-writing the code to explicitly test
> for format==16 so:
>
> . . .
>
> I do not quite understand X
Looking at the code around line 181 in ClientChannel.C where the
crash happened, seems to me that format should have one of the
values 8, 32 and maybe 16. Re-writing the code to explicitly test
for format==16 so:
--- ClientChannel.C-prePSz 2007-02-03 01:25:48.0 +1100
+++ ClientCha
Grabbed dxpc sources
dxpc_3.9.2.orig.tar.gz
dxpc_3.9.2-3.debian.tar.gz
Commented out stripcmd in install-sh so:
psz@como:~/dxpc-3.9.2$ diff install-sh.orig install-sh
124c124
< -s) stripcmd=$stripprog
---
> -s) # stripcmd=$stripprog
and then building, running my own dxpc v
Package: dxpc
Version: 3.9.2-3
Severity: normal
When attempting to run TeXworks (an editor from the TeX distribution),
dxpc fails (crashes?) with message:
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
Can this be fixed? Do you need some other debug out
12 matches
Mail list logo
