LinuxDroidMaster
X11 Fatal server error - Debian chroot on Samsung s10e, running LineageOS with Magisk root
My initial problem turned out to be the /tmp permissions issue referenced elsewhere. After chrooting and running the chmod and chroot commands I end up in this situation:
Starting: Intent { cmp=com.termux.x11/.MainActivity } (EE) Fatal server error: (EE) Linking lock file (/data/data/com.termux/files/usr/tmp/.X0-lock) in place failed: Operation not permitted (EE) ... /usr/bin/startxfce4: X server already running on display :0 xrdb: Connection refused xrdb: Can't open display ':0' xfce4-session: Cannot open display: .
I tried looking for answers with the power of my favoured search engine - I couldn't find a solution but what little I understood seemed to suggest this was a hardlink? At least the failure to link the locking file, I don't understand what is happening to know if that's why the desktop never loads.
I can chroot into the folder and access everything, just can't run the GUI.
Before I changed the /tmp permissions, termux-x11 connected but displayed a black screen with an X for a cursor that never progressed.
Any help would be appreciated. I don't know where to start trying to diagnose this.
Testing updates:
I tried installing manually, same issue - everything works fine up until I need to start the X display, then it either hangs on a black screen (if tmp perms are not set right) or kicks up the same error.
Tried changing the install directory for the chroot installation script to termux's home folder. Tried not binding the /tmp mount just throwing anything at the wall wasn't expecting that one to work any way.
I don't know enough about android or X11 to think up solutions to this but if I try anything else I'll update.
Progress has been made!
I dug into the documentation for termux-x11 itself, if su up to root in termux and run this snippit INSTEAD OF the xfce start script, and then run the start_debian.sh script, again as su, it works in so far as I have a responsive, functional gui. I haven't checked anything beyond that, there may be further issues. I also don't know the implications of doing it this way vs what the script attempts to do.
...I just realized I never specified the version of Android, which could make a huge difference. Apologies for the update-spam, I'm just trying to be as helpful as possible. - I'm running LineageOS 22.1 which is based on Android 15.
No one has replied to this. This repo is really unreliable. Im stuck at X11 display
Sorry for anyone who was hoping for updates from me - had to switch phones for medical app compatibility reasons as this one is considered "too old".
I'll leave the issue open in case anyone else has use for it.