proot info: vpid 1: terminated with signal 4

[morealternative]

• Main Problem
  getting proot info: vpid 1: terminated with signal 4 error
  (after updating proot and proot-distro)

• Info about distro
  Distro Name: ArchLinux
  Distro Architecture: x86_64

• Phone info
  Android Version: 8
  Architecture: aarch64

[morealternative]

proot info: binding = /
proot info: vpid 1: translate("/" + "/bin/sh")
proot error: '/bin/sh' not found (root = /, cwd = /data/data/com.termux/files/home/randomtrash/proot-distro, $PATH=(null))
fatal error: see `proot --help`.

[morealternative]

so when i will get answer ?

[ZhymabekRoman]

Do NOT buy a mixed 32/64 bit architecture device to try to resolve this issue immediatly, as there are known problems with mixed architecture devices.

What do you mean mixed device architecture? So historically, 64 bit processes have backward compatibility with 32 ABI

[morealternative]

so when i will get answer ?

I have been waiting for a software resolution for about one year now; Your best bet is to upgrade to a new device with full 64bit architecture;e.g., aarch64 armv8

Do NOT buy a mixed 32/64 bit architecture device to try to resolve this issue immediatly, as there are known problems with mixed architecture devices. There might be a mobile store nearby with a free 64bit smartphone where you live if you transfer mobile service.

but my phone architecture is aarch64

[ghost]

What do you mean mixed device architecture?

There are devices with AArch64 CPU, but operating system is 32bit only for certain reasons (e.g. small system partition that can hold only one set of native libs). On these devices uname -m reports armv8l.

[ZhymabekRoman]

There are devices with AArch64 CPU, but operating system is 32bit only for certain reasons (e.g. small system partition that can hold only one set of native libs). On these devices uname -m reports armv8l.

Ahhhh, thanks, now I get it. I'm using just such a device, but I haven't noticed any problems with the proot or Termux

[ZhymabekRoman]

[ghost]

This error happens on package compiled for arm. It doesn't matter whether device is armv7l or armv8l - both use arm 32 bit packages.

IMO, the signal 4 error comes from qemu-x86_64 (considering OP's configuration) and not from proot.

[michalbednarski]

Ok, looks like there's a clash between qemu binary and proot loader. I think I'll change proot to skip use of proot loader when using qemu

[michalbednarski]

Fixed version should soon be available in Termux apt as proot_5.1.107-45

[AarizYT]

Still getting the error with the latest PRoot. After logging into an Arch Linux x86_64 PRoot container, executing uname twice returns this error:
talloc: access after free error - first free may be at ./execve/enter.c:661 Bad talloc magic value - access after free proot warning: signal 6 received from process 16991

[AarizYT]

Here's the output:
aarch64

[cache_key.display_info]: [7323236010928765824] [cache_key.has_system_feature]: [7323236010928763981] [cache_key.is_compat_change_enabled]: [7323236010928765817] [cache_key.is_interactive]: [7323236010928765787] [cache_key.is_power_save_mode]: [7323236010928763990] [cache_key.is_user_unlocked]: [7323236010928763999] [cache_key.location_enabled]: [7323236010928763991] [cache_key.package_info]: [7323236010928765818] [cache_key.telephony.get_default_sub_id]: [6070403363833118321] [cache_key.telephony.get_slot_index]: [6070403363833118322] [dalvik.vm.dex2oat-Xms]: [64m] [dalvik.vm.image-dex2oat-Xms]: [64m] [dalvik.vm.image-dex2oat-Xmx]: [64m] [dalvik.vm.isa.arm64.features]: [default] [dalvik.vm.isa.arm64.variant]: [generic] [init.svc.boringssl_self_test32]: [stopped] [init.svc.boringssl_self_test32_vendor]: [stopped] [init.svc.boringssl_self_test64]: [stopped] [init.svc.boringssl_self_test64_vendor]: [stopped] [init.svc.boringssl_self_test_apex32]: [stopped] [init.svc.boringssl_self_test_apex64]: [stopped] [init.svc.snap_utility_64]: [stopped] [persist.sys.xtra_time]: [1633292483106] [ril.modem.board]: [SHANNON327] [ril.modem.board2]: [SHANNON327] [ro.boot.vbmeta.digest]: [3a7d766404aa76eeddbc7af96733065a6c1698634e2d1403e137c8f18d1248b8] [ro.logd.size.stats]: [64K] [ro.odm.product.cpu.abilist]: [arm64-v8a,armeabi-v7a,armeabi] [ro.odm.product.cpu.abilist32]: [armeabi-v7a,armeabi] [ro.odm.product.cpu.abilist64]: [arm64-v8a] [ro.product.cpu.abi]: [arm64-v8a] [ro.product.cpu.abilist]: [arm64-v8a,armeabi-v7a,armeabi] [ro.product.cpu.abilist32]: [armeabi-v7a,armeabi] [ro.product.cpu.abilist64]: [arm64-v8a] [ro.vendor.product.cpu.abilist]: [arm64-v8a,armeabi-v7a,armeabi] [ro.vendor.product.cpu.abilist32]: [armeabi-v7a,armeabi] [ro.vendor.product.cpu.abilist64]: [arm64-v8a] [ro.zygote]: [zygote64_32] [sys.sysctl.extra_free_kbytes]: [33642] [vendor.sec.rild.libpath]: [/vendor/lib64/libsec-ril.so] [vendor.sec.rild.libpath2]: [/vendor/lib64/libsec-ril-dsds.so]

aarch64

I tested a bit more and it seems that even pacman returns the same error. PRoot-Distro has stopped working (with qemu-user-x86-64) since the PRoot commit on 26th September. I get this error when I try to login into an Arch Linux x86_64 PRoot container using PRoot-Distro:
proot info: vpid 1: terminated with signal 4