Opened 7 weeks ago

Last modified 6 days ago

#59415 assigned defect

Htop does not show on Catalina

Reported by: knightjp Owned by: neverpanic (Clemens Lang)
Priority: Normal Milestone:
Component: ports Version: 2.6.1
Keywords: catalina Cc: knightjp, cjones051073 (Chris Jones), kurthindenburg (Kurt Hindenburg)
Port: htop

Description

I'm having a weird problem with htop. It installed just fine on Catalina. No issues there. But when you try to run it. It shows a blank terminal window. Then it appears suddenly after a while like it was taking time to render.

Attachments (2)

Screen Shot 2019-10-21 at 11.03.21 PM.png (165.7 KB) - added by knightjp 7 weeks ago.
blank screen
dtruss.rtf (3.3 KB) - added by knightjp 3 weeks ago.
copy of the errors

Download all attachments as: .zip

Change History (16)

Changed 7 weeks ago by knightjp

blank screen

comment:1 Changed 7 weeks ago by knightjp

Cc: knightjp added
Version: 2.6.1

comment:2 Changed 7 weeks ago by jmroot (Joshua Root)

Keywords: catalina added; htop Catalina removed
Owner: set to neverpanic
Priority: Not setNormal
Status: newassigned

comment:3 Changed 7 weeks ago by cjones051073 (Chris Jones)

I see no such issue here, on macOS 10.15, Xcode 11.1.

Using either Apple's Terminal application, or MacPorts iTerm2 build, htop starts and renders immediately. I am also, incase it is relevant, using the new zsh default shell.

what terminal / shell are you using ?

comment:4 Changed 7 weeks ago by cjones051073 (Chris Jones)

Cc: cjones051073 added

comment:5 Changed 7 weeks ago by neverpanic (Clemens Lang)

I'm not on Catalina yet, so I can't debug this.

comment:6 in reply to:  3 Changed 7 weeks ago by knightjp

Replying to cjones051073:

I see no such issue here, on macOS 10.15, Xcode 11.1.

Using either Apple's Terminal application, or MacPorts iTerm2 build, htop starts and renders immediately. I am also, incase it is relevant, using the new zsh default shell.

what terminal / shell are you using ?

I am using the standard MacOS Terminal.app and the zsh shell.

It is rather weird. I am not sure. Honestly wish I was a developer so that I could find a way to assist with this.

comment:7 Changed 7 weeks ago by cjones051073 (Chris Jones)

I am afraid, but until someone else chimes in to say they also see this, then only you can make progress on resolving it.

Do you have a custom htop configuration ? Its normally kept under ~/.config/htop . If so, try moving it out the way.

Do you have anything in your shell profile, ~/.zshrc or ~/.zprofile that could be affecting this ?

comment:8 Changed 4 weeks ago by kurthindenburg (Kurt Hindenburg)

Cc: kurthindenburg added

It works here - are you running in it a terminal with system zsh?

comment:9 in reply to:  8 Changed 3 weeks ago by knightjp

Replying to kurthindenburg:

It works here - are you running in it a terminal with system zsh?

yes I am.. I am not sure what to do here. Everything is stock MacOS. I haven't done anything to the stock zshrc or zprofile.

comment:10 Changed 3 weeks ago by cjones051073 (Chris Jones)

I understand it is annoying, but the fact is until someone else can reproduce the issue, the evidence has to point to it being something specific to your setup.

Maybe you could send a mail to one of the mailing list, just asking people running 10.15 to give it a try, to see if you can find someone else with the issue ?

comment:11 Changed 3 weeks ago by kurthindenburg (Kurt Hindenburg)

maybe try 'sudo dtruss htop ' and see what it is doing when it is "stuck" - I get a lot of errors due to system restrictions but it might show something for you.

Changed 3 weeks ago by knightjp

Attachment: dtruss.rtf added

copy of the errors

comment:12 Changed 3 weeks ago by knightjp

I attached a copy of the results of the command

'sudo dtruss htop'

comment:13 Changed 3 weeks ago by kurthindenburg (Kurt Hindenburg)

This is beyond me- can you make a new user and try it on that w/ everything the default? Try using bash?

Here's the reporters:

SYSCALL(args) 		 = return

Here's the first few lines for me

dtrace: system integrity protection is on, some features will not be available

SYSCALL(args) 		 = return
select(0x1, 0x7FFEEC4BB750, 0x0, 0x0, 0x7FFEEC4BB7D8)		 = 1 0
dtrace: error on enabled probe ID 2186 (ID 165: syscall::read:return): invalid kernel access in action #12 at DIF offset 68
sigaction(0x12, 0x7FFEEC4BB918, 0x1037A5C48)		 = 0 0
select(0x1, 0x7FFEEC4BB890, 0x0, 0x0, 0x7FFEEC4BB918)		 = 0 0
dtrace: error on enabled probe ID 2184 (ID 167: syscall::write:return): invalid kernel access in action #12 at DIF offset 68

comment:14 Changed 6 days ago by tracuser

Hi, I'm having the same problem, on Catalina 10.15.1 using Bash 3.2, here is the dtruss htop dump:

bash-3.2$ sudo dtruss htop
Password:
dtrace: system integrity protection is on, some features will not be available

SYSCALL(args) = return
select(0x1, 0x7FFEEC7688D0, 0x0, 0x0, 0x7FFEEC768958) = 1 0
dtrace: error on enabled probe ID 2186 (ID 165: syscall::read:return): invalid kernel access in action #12 at DIF offset 68
sigaction(0x12, 0x7FFEEC768AA8, 0x1034FEBF8) = 0 0\ select(0x1, 0x7FFEEC768A20, 0x0, 0x0, 0x7FFEEC768AA8) = 0 0
dtrace: error on enabled probe ID 2184 (ID 167: syscall::write:return): invalid kernel access in action #12 at DIF offset 68
select(0x1, 0x7FFEEC768A20, 0x0, 0x0, 0x7FFEEC768AA8) = 0 proc_info0
dtrace: error on enabled probe ID 2184 (ID 167: syscall::write:return): invalid kernel access in action #12 at DIF offset 68 sigaction(0x12, 0x7FFEEC768A88, 0x0) = 0 0 dtrace: error on enabled probe ID 2184 (ID 167: syscall::write:return): invalid kernel access in action #12 at DIF offset 68 dtrace: error on enabled probe ID 2184 (ID 167: syscall::write:return): invalid kernel access in action #12 at DIF offset 68 dtrace: error on enabled probe ID 2184 (ID 167: syscall::write:return): invalid kernel access in action #12 at DIF offset 68 ioctl(0x1, 0x80487415, 0x7FAB56C03ED0) = 0 0

Last edited 6 days ago by tracuser (previous) (diff)
Note: See TracTickets for help on using tickets.