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

Not working on macOS Sonoma Public Beta #25926

Open
yon opened this issue Sep 13, 2023 · 5 comments
Open

Not working on macOS Sonoma Public Beta #25926

yon opened this issue Sep 13, 2023 · 5 comments

Comments

@yon
Copy link

yon commented Sep 13, 2023

[write something useful and descriptive here]

my log id: 7912226a3c70479c2b67441c

@rex4539
Copy link
Contributor

rex4539 commented Sep 14, 2023

Duplicate of #25718

@vacuumboots
Copy link

Also not working on macOS Sonoma public release 14.0 (23A344)

@jms1voalte
Copy link

Same here.

Tried creating the 14 -> 12 symlink, which has been known to fix things in previous OS major upgrades, rebooted, verified that the symlink existed under /Library/Filesystems/kbfuse.fs/Contents/Extension/. The same "aren't any device slots available" error still popped up.

Log IDs:

  • 78ff75479961a2353997ef1c after upgrade, before symlink
  • 096f95659dcfb04695412b1c after creating symlink and rebooting

Also ... this is the third of fourth time over the past few years I've had to delay using a new OS because of issues like this. Every other company that makes macOS/iOS software, including where I work, tests their stuff with the beta versions ahead of time, and has a working version prior to, or day-of, the public release. Zoom is a rather large company, why can't they do the same? NOT a good look.

@GwynethLlewelyn
Copy link

Well, you can get rid of Keybase's own macFUSE fork, and use the official one instead.

I've written a long tutorial on how to accomplish that; as @rex4539 suggested, this is a duplicate issue of #25718. Just be patient, scroll until the end, and you'll see a link to it.

It's not easy to "get it right", but it should work independently of Keybase's support of future macOS version — so long as macFUSE keeps up with them (they usually do, and there has been "experimental" support for Sonoma almost since the very beginning of the public beta tests).

Enjoy... good luck, though.

@jms1voalte
Copy link

@GwynethLlewelyn You're referring to this link, yes?

I've read through it in the past (very nice write-up by the way, you're a person after my own heart) but I didn't need to actually do it at the time ... and to be honest, nothing about macOS 14 is compelling enough to make me feel like I need to do it now. I'm okay with waiting a few more weeks for somebody to get around to it, although I would feel better seeing some kind of acknowledgement that it is on somebody's to-do list. @chrisnojima @songgao hint hint 😁

What gets me is, we've been through this exact issue several times before. Apple gives developers access to the new macOS versions ahead of time for exactly this reason. Maybe it's silly of me, but I keep hoping somebody at Keybase will start figuring out the FUSE stuff before the new versions are GA, so people don't have to wait like this.

Again, thank you for taking the time to write up that page. If I weren't about to go on vacation (leaving this afternoon) I probably would try that process on the one machine with macOS 14 already installed on it. And if it hasn't been fixed when I get back, maybe I'll try it then.

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
@yon @rex4539 @GwynethLlewelyn @vacuumboots @jms1voalte and others