proot info: vpid 1: terminated with signal 4
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.1k
- Forks
- 276
- PR merge metrics
- No merged PRs in 30d
Description
I was trying to setup proxy chain for kali linux in termux
root@localhost:~# wget https://kuburan.github.io/kuburan-repo.sh
-2019-11-01 02:00:33-- https://kuburan.github.io/kuburan-repo.sh
Resolving kuburan.github.io (kuburan.github.io)... 185.199.110.153, 185.199.108.153, 185.199.111.153, ...
Connecting to kuburan.github.io (kuburan.github.io)|185.199.110.153|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1646 (1.6K) [application/x-sh]
Saving to: ‘kuburan-repo.sh’
kuburan-rep 0% 0 --.-KB/s kuburan-rep 100% 1.61K --.-KB/s in 0.001s
2019-11-01 02:00:34 (1.77 MB/s) - ‘kuburan-repo.sh’ saved [1646/1646]
root@localhost:~ chmod +x kuburan-repo.sh
root@localhost:~ ./kuburan-repo.sh
bash: ./kuburan-repo.sh: /data/data/com.termux/files/usr/bin/sh: bad interpreter: No such file or directory
To solve this, I followed termux-chroot from here
But now i am getting this errors
$ls
binds start-ubuntu.sh ubuntu.sh
kali-armhf storage
kalinethunter ubuntu-fs
$./start-ubuntu.sh
proot info: vpid 1: terminated with signal 4
proot error: trying to remove a directory outside of '/data/data/com.termux/files/usr/tmp', please report this error.
$startkali
proot warning: can't sanitize binding "/sys/": No such file or directory
proot info: vpid 1: terminated with signal 4
proot error: trying to remove a directory outside of '/data/data/com.termux/files/usr/tmp', please report this error.
I am not able to enter in my linux distro. How to fix this?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the mentioned start-ubuntu.sh and ubuntu.sh scripts, then reproduce the failure with proot and inspect the /sys binding warning, signal 4, and cleanup error. Done means the affected Linux distribution starts successfully without these proot errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, linux, shell
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100