Hi @fmgu and thanks for your report. Bit of an assumption, but... congrats on your new Mac 🙂 However I'm sorry to hear you're having this problem with Indigo, it must be frustrating.
Getting lsof to behave is like sticking a fork in one's eye, but unfortunately it's the Apple-recommended way to find out which ports are currently being using by which apps on your machine. While working on Indigo I've sporadically seen (and subsequently worked around) many lsof issues — it is prone to race conditions and so forth — and the errors have been virtually impossible to reliably replicate in my experience.
So in that light I'm very surprised to hear you're seeing this issue replicating itself consistently — particularly since the environment you've described (brand new Mac, running 13.4) is virtually identical to one of the VMs that we run Indigo's tests on regularly.
Thanks for the logs, much appreciated. However I traced through them and unfortunately there's nothing telling in there. Rosetta is unrelated, I believe (incidentally there's no need for a restart after installing it).
Could you try running the following command in your terminal? It's identical to the one Indigo uses internally:
sudo lsof -i +c 0 -P -n -R -sTCP:LISTEN
I suspect it will run just fine, but if you get a chance please let me know either way. I'm going to have to dive deep into this code in Indigo and refactor (again 😡) the methods Indigo uses to communicate with lsof. This is likely to take some time though. Thanks in advance for your patience.
ps I guess you could also try updating to Ventura 13.5. There's no reason it should fix anything in this vicinity but I'm low on better ideas...
