Skip to content
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

wtfutil unresponsive in new macOS brew install #1406

Open
greycubesgav opened this issue Nov 5, 2022 · 3 comments
Open

wtfutil unresponsive in new macOS brew install #1406

greycubesgav opened this issue Nov 5, 2022 · 3 comments
Labels
🐛 bug "Houston, we've had a problem." wontfix

Comments

@greycubesgav
Copy link

What's broken?

Similar to this issue Cant quit out of wtfutil ( #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

Screenshot 2022-11-06 at 01 31 03

Press 'tab'

First module is highlighted
Screenshot 2022-11-06 at 01 31 55

Press 'tab' 2nd time

Second module is highlighted
Screenshot 2022-11-06 at 01 32 41

Press 'esc'

No modules are not highlighted

Screenshot 2022-11-06 at 01 33 43

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 (#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 

Screenshot 2022-11-06 at 01 40 48

However running curl in the same terminal window before running wtfutil shows successful connection to feeds.bbci.co.uk
Screenshot 2022-11-06 at 01 44 49

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

@greycubesgav
Copy link
Author

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.

Screenshot 2022-11-07 at 13 59 36

Accepting this now allows wtfutil to run smoothly.

Untitled

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.

@senorprogrammer senorprogrammer added the 🐛 bug "Houston, we've had a problem." label Nov 25, 2022
@hslatman
Copy link

hslatman commented Nov 29, 2022

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
Copy link

stale bot commented May 31, 2023

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.

@stale stale bot added the wontfix label May 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 bug "Houston, we've had a problem." wontfix
Development

No branches or pull requests

3 participants