PRoot issues on termux. *

[ghost]

Problem description

PRoot issues with andronix and proot-distro. Log : http://ix.io/3pqf

Steps to reproduce

I don't really know how to reproduce, It only happens on 1 device. I used proot-distro install ubuntu-20.04 and that gave me the results.

Expected behavior

Ubuntu to install and be able to use proot-distro login.

Additional information

• Termux application version: 113 on F-Droid.
• Android OS version: Android 11.
• Device model: LG G3.

[ghost]

It was something with lineage os, issue fixed.

[ghost]

Wasn't fixed, something due to my device?

[freebrowser1]

Maybe you can ask the question on the Andronix forums as it is probably an Andronix issue.

https://forum.andronix.app/

Or try Ubuntu 18.04 which works better on my device than 20.04. The latter did install, but some apps don't run properly. And opening a terminal (within the VNC session to Ubuntu, not in Termux itself !) and then running apt update followed by apt upgrade might help.

[ghost]

it is probably an Andronix issue.

This is proot device-specific issue. Proot is stable on some devices and on some is not. Such issues should be reported to https://github.com/termux/proot/issues and I will move this issue here.

[ghost]

it is probably an Andronix issue.

This is proot device-specific issue. Proot is stable on some devices and on some is not. Such issues should be reported to https://github.com/termux/proot/issues and I will move this issue here.

Let's hope it get's fixed soon.

[ghost]

bump

[michalbednarski]

So far I couldn't reproduce this locally

Looks like tar has crashed before it finished loading dynamic libraries, so this shouldn't be related to arguments, just proot --link2symlink tar should be able to trigger crash on affected device

Also, does crash happen every time or randomly on executions? Does setting PROOT_NO_SECCOMP=1 in env makes it go away?

[ghost]

So far I couldn't reproduce this locally

Looks like tar has crashed before it finished loading dynamic libraries, so this shouldn't be related to arguments, just proot --link2symlink tar should be able to trigger crash on affected device

Also, does crash happen every time or randomly on executions? Does setting PROOT_NO_SECCOMP=1 in env makes it go away?

Already tried PROOT_NO_SECCOMP=1, didn't fix anything. This same crash happens when I try to run it. Should I try to run proot --link2symlink tar?

[michalbednarski]

I'm asking if just running proot --link2symlink tar is causing crash (or does it show tar-s help message)

If so, I'd ask for:

1. /apex/com.android.runtime/bin/linker file from that device
2. Result of running PROOT_NO_SECCOMP=1 PROOT_VERBOSE=9 proot --link2symlink tar

[ghost]

I'm asking if just running proot --link2symlink tar is causing crash (or does it show tar-s help message)

If so, I'd ask for:

1. /apex/com.android.runtime/bin/linker file from that device
2. Result of running PROOT_NO_SECCOMP=1 PROOT_VERBOSE=9 proot --link2symlink tar

A few days ago I recently wiped that install of android and went to the stock kernel which has a unsupported android version. Want me to restore a backup I still have and run that?

[michalbednarski]

Well, if you don't have system on which problem occurs then I'd say issue is resolved

[ghost]

Well, if you don't have system on which problem occurs then I'd say issue is resolved

It's a device issue. I have tried with many roms and I get the same issue everytime.

[bart594]

Hi, i have the same issue

~ $ proot --link2symlink tar

: Error in munmap(): Invalid argument CANNOT LINK EXECUTABLE "tar": file offset for the library "/data/data/com.termux/files/usr/lib/libtermux-exec.so" >= file size: 4294967296 >= 5504 proot info: vpid 1: terminated with signal 11 ~ $ PROOT_NO_SECCOMP=1 PROOT_VERBOSE=2 proot --link2symlink tar proot info: binding = / proot info: vpid 1: translate("/data/data/com.termux/files/home" + "tar") proot info: vpid 1: -> "/data/data/com.termux/files/home/tar" proot info: vpid 1: translate("/" + "/data/data/com.termux/files/usr/bin/tar") proot info: vpid 1: -> "/data/data/com.termux/files/usr/bin/tar" proot info: vpid 1: translate("/" + "/data/data/com.termux/files/usr/bin/tar") proot info: vpid 1: -> "/data/data/com.termux/files/usr/bin/tar" proot info: exe = /data/data/com.termux/files/usr/bin/tar proot info: argv = tar proot info: initial cwd = /data/data/com.termux/files/home proot info: verbose level = 2 proot info: pid 25359: access to "/dev/pts/1" (fd 0) won't be translated until closed proot info: pid 25359: access to "/dev/pts/1" (fd 1) won't be translated until closed proot info: pid 25359: access to "/dev/pts/1" (fd 2) won't be translated until closed proot info: pid 25359: access to "/proc/25359/fd" (fd 3) won't be translated until closed proot info: vpid 1: translate("/" + "/data/data/com.termux/files/usr/bin/tar") proot info: vpid 1: -> "/data/data/com.termux/files/usr/bin/tar" proot info: vpid 1: translate("/" + "/data/data/com.termux/files/usr/bin/tar") proot info: vpid 1: -> "/data/data/com.termux/files/usr/bin/tar" proot info: vpid 1: translate("/" + "/data/data/com.termux/files/usr/bin/tar") proot info: vpid 1: -> "/data/data/com.termux/files/usr/bin/tar" proot info: vpid 1: translate("/" + "/system/bin/linker") proot info: vpid 1: -> "/system/bin/linker" proot info: vpid 1: translate("/" + "/data/data/com.termux/files/usr/bin/tar") proot info: vpid 1: -> "/data/data/com.termux/files/usr/bin/tar" proot info: vpid 1: translate("/" + "/data/data/com.termux/files/usr/bin/tar") proot info: vpid 1: -> "/data/data/com.termux/files/usr/bin/tar" proot info: vpid 1: terminated with signal 11 termux-info: Application version: 0.117 Packages CPU architecture: arm Android version: 8.1.0 Kernel build information: Linux localhost 3.4.113-lineageos-g2e74e53 #1 SMP PREEMPT Mon Feb 25 06:32:24 UTC 2019 armv7l Android Device model: ZUK Z1