keybase / keybase/client

Windows: k: disappeared after starting windows from hibernate

Open
#2,890 5 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

I cannot see k: after starting windows from hibernate, before hibernating windows I was able to access k:

log id: 7ca15103e46440234e6fbd1c

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 Windows-related client code and the log identified by 7ca15103e46440234e6fbd1c, focusing on what happens to the k: drive after hibernation and resume. Reproduce the hibernate cycle and determine why the drive is unavailable; done means k: is accessible after Windows resumes.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
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.