-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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 folders don't work #11763
Comments
@stephthegeek did you enable Filesystem access via the UI? You can do that via [Gear icon] -> Files -> Enable Keybase in Finder |
Same here. If I enable filesystem acces via the UI I see the Label "Action needed!". I followed the instructions (open System Preferences / Security & Privacy, unlock by clicking the padlock and click the "Allow" button. But still no success… Any ideas? |
@rekomat are you using an enterprise distribution of macOS (i..e, one provided by your workplace)? It might have locked down external kernel modules even more. |
@strib Nope… just "normal" macOS High Sierra v.10.13.6 as downloaded/updated from the App Store. |
@rekomat maybe try restarting Keybase, and/or restarting your computer, to see if that helps. If not, please do a |
@strib Thanks for your help! I restarted the computer twice — no success. The log ID is e219f2238d4ff35cf83b001c |
@rekomat do any of these troubleshooting steps apply to you? https://github.com/keybase/client/wiki/Troubleshooting |
@strib Nope… no success.
|
Ok, please try |
Thanks for your patience, Jeremy! — Here the console output (error in last line):
|
Ah ok, that -603946981 error code means you're still getting the security permissions error from macOS: http://github.com/osxfuse/support/b-603946981lob/master/load_osxfuse/fuse_kext.c#L111 It seems like, for some reason, macOS isn't respecting your decision to allow our kernel extension. I'm not sure why! If this was a more locked-down version of macOS, I'd recommend booting into recovery mode and using the One user reported they needed to disable SIP for some reason, though it was a different error code: #12720 (comment) |
I found a workaround - although very strange. It seems as if it's the click to "Allow" that isn't acknowledged by MacOS. They have added quite a lot of security around the "allow" button, to prevent it from being clicked from third party apps or remote desktop applications. And for some reason, they don't trust their own trackpad in some situations. I followed https://apple.stackexchange.com/a/325768 to enable the "allow" button to be triggered by the keyboard (will need to restart System Preferences between enabling tab-ing between controls and going into Security and Privacy). Then it worked. Strange, indeed. Brand new computer running High Sierra, no custom software at all or any strange Enterprise stuff. |
Commenting here as I think seeing the same problem but so far unable to get things resolved. Let me know if this should go into a separate bug. macOS 10.13.6 (17G14042) Keybase > Settings > Files > Enable Finder Integration > Tick Checkbox > Yes, enable Running
results in https://bin.disroot.org/?71256b8b64798ef7#DAHriuiap8fjW1URuGaMkCX33w8Txg4fvnwC2y3KgdGh with the interesting lines
Was trying to follow the StackExchange suggestion by boivie. Had "All controls" selected already. But I am not seeing "Allow" in Any ideas how to enable keybase Finder integration? |
my log id: 732a5e1a9a73fc0ee8c2001c
The text was updated successfully, but these errors were encountered: