Keybase: Bad folder (Mac OS X)
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
An OS X Notification consistently reports this message when starting the Keybase.app:
/keybase/System is not a Keybase folder. All folders begin with /keybase/private or /keybase/public.
This is likely being triggered by something I have installed that's looking for mounted disks. Based on what I'm seeing with "opensnoop", I would guess Carbon Copy Cloner. Maybe I'll hack up pathopens.d later to find out for sure.
In general, notifications like this are pretty much out of the user's control, especially when it's third party software triggering it. If you can only notify when it is initiated by a user initiated operation (tty linked execution) as opposed to a LaunchAgent/LaunchDaemon, that would be better.
my log id: cd5c1d799ce79bb59c6b2f1c
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the notification while launching Keybase.app and use the reported log id, cd5c1d799ce79bb59c6b2f1c, to trace the event. Compare the Carbon Copy Cloner-style mounted-disk probe with a user-initiated operation; done means third-party LaunchAgent or LaunchDaemon activity no longer produces this notification while user-initiated checks still do.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100