Yaak silently fails to launch if `localhost` cannot be resolved

I originally filed this as a GitHub issue then forgot to re-open it when the GH issue tracker was closed 😅

But as it says on the tin; if localhost cannot be resolved to 127.0.0.1, the app will silently fail to launch with no indication of why.

I figured out the underlying issue by building the app from source, but I haven’t had an opportunity to reproduce it again to get the real error message. I can probably do that later if it’s needed.

The main thing is that is zero indication of what’s happening when using the regular GUI app, though (at least on macOS). There’s no crash dialog, there’s no output in Console.app on any output streams, etc.

I know it’s exceedingly odd for localhost to fail to resolve. My org’s VPN client gets in to an argument with my hosts file manager sometimes, and it clobbers my /etc/hosts file as a result, which makes localhost fail to resolve.

One solution is obviously to change everything to use 127.0.0.1, but I know there are downsides to that. I think it’s probably fine to leave it as it is, and just make sure there’s indication of the crash to the user.