-
-
Notifications
You must be signed in to change notification settings - Fork 909
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
htop does not run #273
Comments
I can confirm, same behavior on iOS 13 as well. |
Yup...still does not work.
…______________________________________________________________
Robert Weiss
*Professor of Natural Hazards*
Department of Geosciences
Virginia Tech
4044 Derring Hall (0420)
Blacksburg, VA 24061, U.S.A.
Office: 1068A Derring
Phone:+1-540-231-2334
Fax: +1-540-231-3386
Research Web: http://coastalhazardsvt.weebly.com
Education Web: https://fralin.vt.edu/DRRM.html
Twitter: @VTCoastal
--
--
On Thu, Jun 27, 2019 at 2:26 AM Marco Visin ***@***.***> wrote:
I can confirm, same behavior on iOS 13 as well.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#273>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAKYINUEHAQYTEPVLNP3HSTP4RMRNANCNFSM4GPSTXYQ>
.
|
I believe it is a problem with ncurses. |
Many other ncurses programs run fine, it's much more likely to be a problem with /proc. |
What are some ncurses commands/programs that you tested? |
nano, ncdu |
I don’t believe this is related to ncurses, I’ve been able to install and use tmux which so far has worked for me. |
it won't respond to SIGKILL as well. |
Anyone really good with stack traces? Maybe this might shed light on what's going on with htop? |
@tbodt, hello. I made these changes:
Originally posted by @nimelehin in #1066 (comment) https://discord.com/channels/508839261924229141/510973900209913857/811252086557114378 htop also gives me yes htop and non-busybox tops are broken |
im having this issue too, build 1.2.3 298 |
I successfully install htop, but nothing is shown (no screen output at all).
The text was updated successfully, but these errors were encountered: