Many X clients break when only the pathname socket is available #10
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
During testing for #1 it appears that X clients refuse to use the pathname socket with
DISPLAY=:0
, and theunix:
syntax appeared to have fixed it. That however turns out to be untrue for many clients due to implementation-specific behaviour or bugs.Programs like Steam and Vial straight up refuse to connect, while MikroTik WinBox somehow works perfectly fine despite also using the qt framework. The silliest failure comes, as expected, from GNU, where the toolkit supports the pathname socket correctly, and the main UI works perfectly fine, however the code responsible for starting the export dialogue somehow turns
unix:/tmp/.X11-unix/X0
intounix:/tmp/.0
, preventing images from being exported.Currently,
acb6931f3e
works around these regressions by allowing individual apps to revert to the abstract socket.