michalbednarski

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

Sometimes rootfs contain directories readable by nobody (chmod 000, although root still can access them, `proot -0` temporary chmods them so they can be accessed) I think this can be...

One thing you might run into is that when uid faking is enabled in proot, in order to connect to dbus both dbus-deamon and client must be running under same...

`Could not connect to Systemd: Failed to connect to socket /run/dbus/system_bus_socket: Connection refused` means that system dbus is not running (`dbus-launch` launches only session bus) Chances are you won't do...

As far as I know Termux is already handled by Android as foreground process (because it runs foreground service which displays notification) and as far as I know this status...

Looks like this is problem related to proot loader (Stub application which is `execve`'d instead of actual application and `mmap`s the actual application and dynamic linker (`ld.so`); loader is loaded...

Seems that you're right. Something to test that under Termux would be nice (so far most programs didn't use `fork` syscall and instead used `clone`; `vfork` also seems to be...

I'm afraid there is no dedicated place for that, so you'd have to put it in `translate_syscall_exit` (Note that `switch (syscall_number)` is on rewritten syscall, so add `case PR_setitimer:` and...

In my test this worked okay (except 32-on-64 mode, I'm including patched version below) Differences between 32 and 64 bit itimerval, as gathered by using `gdb` scripting on AOSP build...

I don't have device on which issue reproduces and I'm not sure if this is related or not but you can try using modification described in #107 No idea if...