S D Rausty

>clash between qemu binary and proot loader. For the most part, 64bit works very well with and without qemu support; 32bit is good too on all devices with the exception...

>proot info: vpid 1: terminated with signal 11 ``` exec proot --verbose=2 --kernel-release=4.9.190 --kill-on-exit --sysvipc --link2symlink -0 -r /data/data/com.termux/files/home/x8 -q /data/data/com.termux/files/usr/bin/qemu-i386 -b /apex -b /storage -b /sys -b /system -b...

>error with the latest PRoot. After logging into an Arch Linux x86_64 PRoot container `dpkg --print-architecture` `getprop | grep -e 32 -e 64` `uname -m` What is the device architecture?

>executing uname twice returns this error ``` grep ame .bashrc alias UM='uname -m' alias Um='uname -m' alias um='uname -m' ``` I cannot reproduce this error.

Thank you for sharing >proot info: vpid 1: terminated with signal 4 Can you also share `proot --verbose=2` output?

>so when i will get answer ? @morealternative does the update resolve the error? @AarizYT ensure that everything is up to date as @michalbednarski has created https://github.com/termux/termux-packages/commit/a5cc417d8de92db5efcd1525193409d388455a5c which resolves `proot...

> Is there any information I could provide that could help solve the issue? > a new command is made called `pinghelp` with the latest commits to help users out...

I don't know by whom my comment was minimized, nor why, and for what reason; Can you please explain your actions and how these actions are helping Termux, and in...

@Grimler91 thank you for replying; I will try to be clearer in future comments as to intent; Github login @broetchenrackete36 is NOT the only Termux user that is still having...

>it looks more like advertisement for your own tool If anyone can promote a sane rooting method for Android without using 3rd party tools like Termux and similar in order...