wtfutil unresponsive in new macOS brew install

greycubesgav commented 1 year ago

What's broken?

Similar to this issue Cant quit out of wtfutil ( https://github.com/wtfutil/wtf/issues/1318) I can't seem to quit wtfutil at all on macOS Ventura 13.0 (22A380)

Steps to reproduce

Install wtfutil through brew with no previous install

> brew install wtfutil
Running `brew update --auto-update`...
==> Auto-updated Homebrew!
Updated 2 taps (homebrew/core and homebrew/cask).

You have 3 outdated formulae and 1 outdated cask installed.
You can upgrade them with brew upgrade
or list them with brew outdated.

==> Downloading https://ghcr.io/v2/homebrew/core/wtfutil/manifests/0.42.0
######################################################################## 100.0%
==> Downloading https://ghcr.io/v2/homebrew/core/wtfutil/blobs/sha256:29ce9ac3f0f4cd80a0f1d2bf2819c9c2b75313851bd0acac9a6c766c684bcaec
==> Downloading from https://pkg-containers.githubusercontent.com/ghcr1/blobs/sha256:29ce9ac3f0f4cd80a0f1d2bf2819c9c2b75313851bd0acac9a6c766
######################################################################## 100.0%
==> Pouring wtfutil--0.42.0.arm64_ventura.bottle.tar.gz
🍺  /opt/homebrew/Cellar/wtfutil/0.42.0: 6 files, 62.2MB
==> Running `brew cleanup wtfutil`...
Disable this behaviour by setting HOMEBREW_NO_INSTALL_CLEANUP.
Hide these hints with HOMEBREW_NO_ENV_HINTS (see `man brew`).

Run wtfutil with no commands

wtfutil

Initial screen

Press 'tab'

First module is highlighted

Press 'tab' 2nd time

Second module is highlighted

Press 'esc'

No modules are not highlighted

Press 'q' no response app stays like the last screen grab above

Press 'Q', 'tab', 'esc', ctrl-c , all have no effect, app must be killed to stop it

Notes:

I'm running on M1 MacBook Pro in iTerm2 under macOS Ventura 13.0 (22A380)
It's actually not possible to quit the app at all, i.e. no need to follow above, just load, hit q, Q or ctrl-c, app becomes unresponsive, tab no longer selects modules.

Network related?

I have internet connection, so didn't think it was related to @Moizsohail's issue (https://github.com/wtfutil/wtf/issues/1318). However I've noticed few seconds I get the error in the middle right hand widget:

 Get "http://feeds.bbci.co.uk/news/rss.xml": dial tcp 2.21.184.113:80: i/o timeout

However running curl in the same terminal window before running wtfutil shows successful connection to feeds.bbci.co.uk

So it looks like wtfutil can't connect to the internet and this causes it to lockup?

greycubesgav commented 1 year ago

Ok I can confirm it is related to internet access.

I came back to my machine today and when opening vscode fullscreen, I was presented with a Little Snitch (a software firewall software for macOS), asking if wtfutil should be able to connect to the internet.

Accepting this now allows wtfutil to run smoothly.

Stangeness (Unlikely related to wtfutil)

I didn't run wtfutil today and the little snitch popup did not appear when running wtfutil previous days.
I'm putting this down to a bug somewhere between Little Snitch and macOS Ventura.

Remaining wtfutil issue

It does seem there's a bug somewhere in wtfutil (at least under macOS) related to internet access. I would assume that when wtfutil is trying to open an internet connection, little snitch is not responding until the user selects yes/no on their allow dialogue. This non-response, no success or failure, is causing wtfutil to hang indefinably.

hslatman commented 1 year ago

Had a similar issue, but with the ipinfo module. No interaction with wtfutil possible at all. Commenting the ipinfo module out from the config made it work, so I assumed a connection issue. Then noticed Lulu blocked the connection. After approving the new binary all started working again, including the ipinfo module.

stale[bot] commented 1 year ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

wtfutil / wtf