Le 09/02/2025 à 20:26, Carsten Haitzler a écrit :
using mit-shm is entirely a choice by the x client itself. invariably the right
thing to do is try use the mit-shm extension - set up a xshmimage ansds then
try xshmattach and see if you get an error. if you do - it's not going to work
(not local)
Le 09/02/2025 à 22:08, Vladimir Dergachev a écrit :
This reminds me of the difference between ssh -X and ssh -Y options,
maybe a look at ssh code will give you ideas.
Indeed, ssh has several tricks to make the X11 forwarding
with some restrictions between -X and -Y "... too many programs
Le 09/02/2025 à 20:26, Carsten Haitzler a écrit :
using mit-shm is entirely a choice by the x client itself. invariably the right
thing to do is try use the mit-shm extension - set up a xshmimage ansds then
try xshmattach and see if you get an error.
If I guess correctly what's happening with my
On Mon, 10 Feb 2025 09:47:01 +0100 Christophe Lohr
said:
> Le 09/02/2025 à 20:26, Carsten Haitzler a écrit :
> > using mit-shm is entirely a choice by the x client itself. invariably the
> > right thing to do is try use the mit-shm extension - set up a xshmimage
> > ansds then try xshmattach and
On Mon, 10 Feb 2025 09:02:40 +0100 Christophe Lohr
said:
> Le 09/02/2025 à 20:26, Carsten Haitzler a écrit :
> > using mit-shm is entirely a choice by the x client itself. invariably the
> > right thing to do is try use the mit-shm extension - set up a xshmimage
> > ansds then try xshmattach and
On 2/7/25 07:38, Christophe Lohr wrote:
Then I can use it:
$ DISPLAY=localhost:1 xeyes
Try exporting the DISPLAY environment variable.
I've run into programs that do things that work with the variable
exported but don't work when it's not exported.
--
Grant. . . .
Le 10/02/2025 à 11:19, Carsten Haitzler a écrit :
If I guess correctly what's happening with my test: X clients never get
this error, and so they wait. Is that it?
they should...
strace would be the next port of call - but i shall assume they are sitting in
select/epoll waiting on something.
f
