keybase / keybase/client

post-10.14.6 update Keybase kext can no longer load

Open
#18,922 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
9.2k
Forks
1.3k
Avg merge
12h 58m
Merged PRs (30d)
56

Description

my log id: 3204d0e26ba3aa37a944b81c

The following error message is displayed. I have submitted a log snapshot. Chat functionality still operates. A separate Fuse install does not exist on this system. This happened immediately following the first boot post 10.14.6 update.

Keybase error message

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the supplied log snapshot using ID 3204d0e26ba3aa37a944b81c and the error message shown in the attached image. Investigate the Keybase kext-loading failure immediately after the macOS 10.14.6 update, while confirming that chat still operates and no separate Fuse install exists. Done means the cause is identified and kext loading is verified again.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos
Domain
operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.