-
-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: xorg-server/xorg-server-vfb/xwayland: A problem with shm support [the problem is localized]. #15239
Comments
OK, this also reproduces with |
Well, it looks like xorg-server is right. But xcb is fault. The same snippet works right in proot. What can we do in this case? |
Ok. 130 is a code of |
FWIW, the test case seems to work when using a custom Also FWIW, this reminds me of log message such as follows when invoking some Qt application:
The shm support in xcb seems to be broken in some way. |
Are you talking about this patch? https://github.com/termux/termux-packages/blob/master/x11-packages/firefox/shared_memory_posix.cc.patch |
Why does it work with i.e. libwayland but fails to work with xtrans? Is it possible that sendmsg/recvmsg is somehow broken in bionic but fine in glibc? |
I was wrong. glibc version with ANDROID=1 does not work. I did a mistake. |
I found a root of problem. It is right here.
Are there any other ways to create shared memory file descriptor without implicitly open file on disk? |
It is possible to patch Xorg to support |
Ok, I asked for proot support for this. We can patch xorg-server to support this behaviour. And finally I can patch
But anyway work with chroot will require some additional steps from user... |
Problem description
Hi. The following code works on pc's Xvfb, but returns
BadMatch
on termux's Xvfb.code
If it will help I have xscope log
log.txt
What steps will reproduce the bug?
Compile this code (
gcc ss.c -o ss -lxcb -lxcb-shm -DANDROID=1
), start Xvfb (Xvfb :0 -ac
) and then start ss (DISPLAY=:0 ./ss
).What is the expected behavior?
Program should not fail.
System information
termux-info:
The text was updated successfully, but these errors were encountered: