HackManager

Results 9 comments of HackManager

in an unknown edge case, `bash` may become corrupted by each login unless forced read-only

> Just to confirm you changed your login shell to `/bin/bash` and it broke? It's weird, but yes. I tried in failsafe mode return to "zsh", but: ``` :/data/data/com.termux/files/home $...

in an unknown edge case, `bash` may become corrupted by each login unless forced read-only

> @HackManager please try this command in Termux Failsafe Shell: > > ```bash > rm /data/data/com.termux/files/home/.termux/shell > ``` > > that should reset any accidental misconfiguration of `chsh` to default....

in an unknown edge case, `bash` may become corrupted by each login unless forced read-only

I reinstalled ``bash`` with ``apt`` successfully. But it doesn't see ``pkg``: ``` % apt reinstall pkg Reading package lists... Done Building dependency tree... Done Reading state information... Done E: Unable...

in an unknown edge case, `bash` may become corrupted by each login unless forced read-only

Thank you all very much! For help and including for explaining an issue. I really need to always understand what's happening in system. I liked the move with ``ln``. Did...

in an unknown edge case, `bash` may become corrupted by each login unless forced read-only

Thanks, I understand! > However, in this case, something seems to have happened that corrupted your `bash` file And yes, you right. Because ``bash`` stops to work after Termux reboot,...

in an unknown edge case, `bash` may become corrupted by each login unless forced read-only

I would like to help. What kind of data is needed from my side?

in an unknown edge case, `bash` may become corrupted by each login unless forced read-only

At this moment I have only one main mobile and don't have any other devices. But I can upload recent apt history, names of installed for now pkges, damaged and...

in an unknown edge case, `bash` may become corrupted by each login unless forced read-only

I have already done. You can see everything in my "trmxBadBash" repo.

in an unknown edge case, `bash` may become corrupted by each login unless forced read-only

I see. Maybe it's worth starting with the difference in damaged and original files?