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

Keybase continually tries to install new helper #13997

Open
anthonygreen opened this issue Oct 1, 2018 · 16 comments
Open

Keybase continually tries to install new helper #13997

anthonygreen opened this issue Oct 1, 2018 · 16 comments

Comments

@anthonygreen
Copy link

@anthonygreen anthonygreen commented Oct 1, 2018

Every time Keybase starts it launches a dialogue box asking me to install a new helper.
The install fails every time.
Reinstalling Keybase doesn't resolve the issue
Keybase GUI Version: 2.6.2-20180920205546+0f17a92adc

@maxtaco
Copy link
Contributor

@maxtaco maxtaco commented Oct 1, 2018

Sorry about this, this really sucks! Can you do a keybase log send? That might work if you've previously installed keybase and it worked. Otherwise, one of us will reach out to you. Thank you.

@maxtaco
Copy link
Contributor

@maxtaco maxtaco commented Oct 22, 2018

@anthonygreen is this still an issue? Can you run keybase log send and we can take a look?

@jgjay
Copy link

@jgjay jgjay commented Jan 2, 2019

I'm having the same issue, I've run keybase log send and my log ID was ba18fec1147d10273b2e311c

Additionally after several attempts I get this error dialog:

There was an error trying to install the helper.

exit status 1
There was an error trying to install the mountdir.

exit status 1
We were unable to load the part of Keybase that lets you access your files in your file system. You should be able to do so if you wait a few minutes and restart Keybase.

Please run `keybase log send` to report the error.

@k3ypad
Copy link

@k3ypad k3ypad commented Jan 2, 2019

Just encountered this issue as well, log ID: c6c51fd31a1493b4ecdf441c

OSX 10.14.2

@k3ypad
Copy link

@k3ypad k3ypad commented Jan 2, 2019

Had to reinstall but works fine after that.

@k3ypad
Copy link

@k3ypad k3ypad commented Jan 2, 2019

... and after a while it's gone back to breaking (repeatedly prompting for helper install) - can't access files on kbfs

@maxtaco
Copy link
Contributor

@maxtaco maxtaco commented Jan 2, 2019

If you guys are seeing this issue on 2.12.5, there's a new bug that we need to fix. First check and see if groups | grep staff yields any results. If not, this workaround is tested to work:

  • Add your user to the staff group:
    • sudo dseditgroup -o edit -a $(whoami) -t user staff
  • Quit keybase
  • Restart keybase

@k3ypad
Copy link

@k3ypad k3ypad commented Jan 2, 2019

Workaround worked for me on 2.12.5 - thanks so much @maxtaco !

@maxtaco
Copy link
Contributor

@maxtaco maxtaco commented Jan 2, 2019

Great news, we'll get a proper fix out in the next few days

@jgjay
Copy link

@jgjay jgjay commented Jan 2, 2019

Also worked for me, thanks for providing such a quick workaround. 👍

@chadpalmer
Copy link

@chadpalmer chadpalmer commented Jan 3, 2019

The workaround fixed the issue for me as well. Thanks everyone!

@jorjitop
Copy link

@jorjitop jorjitop commented Jan 4, 2019

I am getting this several times a day. When I click on Got It, I put in my Admin name and password and all seems ok . . . until a bit later when it comes up again.
image

@maxtaco
Copy link
Contributor

@maxtaco maxtaco commented Jan 4, 2019

@jorjitop sorry about the bug, can you keybase log send?

@jorjitop
Copy link

@jorjitop jorjitop commented Jan 4, 2019

@jorjitop
Copy link

@jorjitop jorjitop commented Jan 4, 2019

@maxtaco
Copy link
Contributor

@maxtaco maxtaco commented Jan 4, 2019

Thanks for sending @jorjitop. Unfortunately you're stuck in an situation that you can't update out of, due to our bug. You should be able to fix it with:

sudo dseditgroup -o edit -a $(whoami) -t user admin
keybase update check
sudo dseditgroup -o edit -d $(whoami) -t user admin

That is: add yourself to the admin group, upgrade, then remove yourself. This should fix your broken upgrader. Sorry about that!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants