Closed ghost closed 5 years ago
Thank you very much for your really detailed report, but I'm afraid that doesn't make the problem more clear to me. My only supported device, Samsung SM-T719 with a similar CPU, has it working OK under LineageOS 16.
You're not the only one who reports this, if that makes things better =)
I suppose that installing prebuilt software works fine, but does building anything fail in a similar manner?
My list of erratic ideas that you could try:
install
invocations fail like this.-0
option to proot
invocation in /data/data/com.termux.nix/usr/bin/login
.-v 9
to proot
invocation (will make things even more noisy).cp
+chmod
and calling it a day.install
invocation and see if the problem goes away (a bit crazy).nixpkgs
channel.If you don't feel like going through that hassle, just update and try to proceed without installing home-manager and see if all install
s fail like this one.
Note that you forgot -v -D -m755
. Not like it would change anything though...
8. Updating to my latest build (wipe the data and relaunch the app. probably won't change much, but installing home-manager is optional since 0f8ba89).
Same error, but I can use it without home-manager :) Thank you!
- Checking if all
install
invocations fail like this.
It looks like it is.
I am getting same error while building clearsans from NUR
But I can use install
in console (for example touch test; install test test1
works fine there)
- Adding
-0
option toproot
invocation in/data/data/com.termux.nix/usr/bin/login
.
Same error
- Setting SELinux to permissive. Probably doesn't matter, but it should be a quick check.
Phone in not rooted, so I can't do this for now
- Trying unstable
nixpkgs
channel.
Same
Note that you forgot
-v -D -m755
. Not like it would change anything though...
Yeah, I did it on purpose to check ptrace output on "minimal" command
Thank you for the guidance, I think it is worth take another spin after https://github.com/NixOS/nixpkgs/pull/57339
Oh, I have a plausible idea that my precompiled proot
is to blame.
What you could do to test it:
Try install
ing into and out of /nix
and see if these fail.
If that's the case, which I really hope it is, you may try recompiling proot
in termux on your device. There is a sketch of a guide in the repo, feel free to ask questions.
- Try
install
ing into and out of/nix
and see if these fail.
Nope, it's OK :( (install test /nix/test1
and install /nix/test1 test2
)
Then I can't comprehend what on Earth makes these invocations failing inside nix builds any different. =/
Due to bd7335a bringing all-new way to build proot, I kindly ask you to either
nix-on-droid-install
or, if you have a valuable setup that you don't want to backup and restore
proot
binary with the new, reproducible cross-compiled one.While I still don't understand the nature of the bus error, the new binary is not tied to my tablet in any way and it works for me, so I really hope it will work on all devices.
Works like a charm :) Thank you very much!
You're welcome. That makes two bus-error-begone reports, so 'yay' indeed!
ptrace on relevant line:
Device: Xiaomi Redmi 4X, LineageOS 15.1-20181114-NIGHTLY-santoni