keybase / keybase/client

Creating a new private folder for a tracked person fails without info (Win10)

Open
#3,234 1 comment 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

Keybase GUI Version: 1.0.16-20160622134333+f8bd1e6
LogID: 15f15f67f37a258e225ae71c

Windows 10

Keybase seems to be unable to create folders for shared directories from either GUI or console application (even when the console application is started as administrator).
Console commands do not output an error, commands like "keybase id", "keybase add", etc. can be run w/o problems, the shared folders never get created though.

Creating a shared folder did work before for me once, the only difference I can make out was a reboot in between (therefore keybase prompting me for the password after the login, which was pasted from a password manager and should therefore be correct - also there was no error message regarding the password)

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 by reproducing shared-folder creation on Windows 10 from both the GUI and console, using the provided LogID to inspect available diagnostics. Done means the folder is created successfully or the failure produces a useful error message; the payload names no source files or tests.

Written by the indexing model from the issue text.

Assessment

Domain
desktop-dev, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.