KBFS file greyed out after moving to private folder
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
OS X 10.12.4 (16E195)
my log id: 5a3a6263959aa76340e8d61c
- Copy a file into /keybase/private/username/
- The file appears to be successfully copied
- Notification appears: encrypting and uploading
- After a few moments, the file becomes greyed out
Double clicking the file to open it has no effect within the keybase folder. Copying it to desktop does work, although there is a warning that the file is in use.
The file appears on other devices in the same greyed out state.

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
No source files or tests are named. Start by reproducing the copy into /keybase/private/username/ on OS X 10.12.4 and inspect the behavior associated with log ID 5a3a6263959aa76340e8d61c. Done means the copied file is not greyed out, opens within the Keybase folder, and works on other devices.
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
- 30/100