Xavier G.

I captured the X11 traffic between `qtdeadsimple` and `nxagent`. When Qt wishes to close the connection, it emits a SendEvent request along with a ClientMessage, the type of which is...

> In that case you should get the same problem when running on a normal X server without window manager. Can you confirm? I killed my window manager and ran...

According to `Atom map in context [nxagentResetAtomMap: Exiting]` (and other calls to `nxagentPrintAtomMapInfo()`), `_QT_CLOSE_CONNECTION` never enters the atom map despite existing (with different values) in both local and remote servers....

Here is a different fix: instead of systematically returning, ProcSendEvent() returns only if ForwardClientMessage() acknowledges it did something (or tried to do something) with the message. ```diff c --- nx-X11/programs/Xserver/hw/nxagent/Events.h...

Hi! Indeed, this PR is getting close to being one year old. In practice, I am not dead, just super busy. Good news, it should get better very soon, and...

> should be fixed for containers by #745 I have not tested yet, but a brief look at https://github.com/containers/ansible-podman-collections/pull/745/files reflects only one item that _might_ be related with this issue:...

This new commit looks definitely better -- I'll give it a try (likely on Friday).

@sshnaidm It works! After git-cloning your latest commits, I removed my 58-line long `container_create_reference` hack and ran `ansible-playbook -C` (with other suitable arguments, of course), and all of my existing,...