keybase / keybase/client

Hibernation on Windows seems to cause KBFS to fail upon awkening.

Open
#5,890 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

The KBFS environment seems to get corrupted after every hibernation. Restarting generally fixes it. There's an unreachable K: drive left around and it seems like this prevents resuming.

my log id: 0fbc494a03b21b246c42d41c

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 ID 0fbc494a03b21b246c42d41c and reproduce the Windows hibernation and resume sequence described in the issue. Investigate KBFS behavior around the unreachable K: drive after resume. Done means hibernation no longer leaves KBFS corrupted or requires a restart.

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.