-
Notifications
You must be signed in to change notification settings - Fork 234
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]: Unable to use Termux-X11 with x86 proot distributions #495
Comments
I built Arch Linux aarch64 and x86 manually with the same result. aarch64 works perfectly. x86 has a black screen. |
I'm also unable to use Termux-X11 with Ubuntu x86, but Ubuntu aarch64 works perfectly. Interestingly, the logs are a bit different. I see a |
Alpine x86 fails as well. I think this is enough to indicate this issue affects all x86 proot distributions (possibly all QEMU proot distributions). Let me change the title to reflect it. |
Tested a different desktop environment and Ubuntu aarch64 GNOME works. Ubuntu x86 GNOME has the same black screen issue. |
Don't assume that shmflg != 0 means SHM_RDONLY termux/proot-distro#495
Problem description
Arch Linux aarch64 works perfectly on my device. I'm able to run Termux-X11 and run xfce4 with no issues. Arch Linux x86 however, I cannot for the life of me get to work. The same commands that work perfectly on Arch Linux aarch64, fail for x86. All I see in Termux-X11 is a black screen with the default X cursor. No clear errors in the logs from my untrained eye.
Device: Pixel 9
OS: Android 15 (GrapheneOS)
Version: proot-distro latest (v4.21.0)
Arch Linux aarch64 working startxfce4 log
Arch Linux aarch64 working Termux-X11 debug log
Arch Linux x86 not working startxfce4 log
Arch Linux x86 not working Termux-X11 log
What steps will reproduce the bug?
Arch Linux aarch64
Termux
startxfce4_arch.sh
Arch Linux x86
Termux
startxfce4_archx86.sh
What is the expected behavior?
Able to see and use the xfce4 desktop environment in Termux-X11 on Arch Linux x86.
The text was updated successfully, but these errors were encountered: