mbrt/gmailctl

Fresh install with snap cannot succeed due to misconfigured network

jessedhillon opened this issue · 5 comments

jessedhillon commented

On the first run of gmailctl init on a fresh set of OAuth credentials, the program tries to start a HTTP server, to facilitate an OAuth flow (/cmd/gmailctl/localcred/local_provider.go:139).

On Ubuntu 20.04 after a sudo snap install gmailctl I tried to do an init and this was the result:

$ gmailctl init
missing or invalid cached token: open /home/jesse/snap/gmailctl/8/.gmailctl/token.json: no such file or directory

Error: starting local server: listen tcp :0: listen: operation not permitted

Note: 
  - gmailctl requires a temporary local HTTP server for the authentication flow.

I'm not knowledgeable enough on how to use snap to reconfigure an installed package, so I wasn't able to get past this. I installed golang instead.

mbrt commented

Thanks Jesse! I honestly don't know how Snap packaging works. It was contributed by @gjolly in 192e97c.

If they are still around, maybe they can easily fix it.

gjolly commented

Yes, I'm still around and I can reproduce. Is it a new authentication flow? I probably need to give more permission to the snap, I will check that.
Thanks for reporting. I need to improve my testing process before pushing new versions of the snap to the store.

jessedhillon commented
gjolly commented

Sorry for the spams. I couldn't decide on a commit message 😅

mbrt commented

Thanks for the super quick fix!

  • 🚀1