keybase / keybase/client

KBFS not usable after computer reset

Open
#6,426 2 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

Here is my signed message (including $(date))
BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5wcIkHbsAlog7c gpTtNGIpaCtIeyN y5OiQnRPXscLpw5 gwNMuae1NV5fEP0 uYk3NdJk1d0EEc9 meuEiUGmH40St9w GpSzYy36MQ4tOOL PgoxA4JVRD1K0jU 7bNxynkicGav7IN fRlQwMxCiZSuJyD TQhanl5PkRMTCMO s1XcmtzrbgYzQr2 r4A1FcP6ldGkEKd Te7d6JwpE12wdI0 0c9vek7BZt9yeGg aw08Skd80lHr7T3 wEyOI0sinHFxVgB a31ZFxvuJJ7cPer TkecL7t4vipzhgO cDKXtx3yjstiJge Csiy0luPVBdhraP DLrY8ZYHlMkOV6D KXZTfuvHQFIp4Yz NfgwDVQ5x2lY3ab jDdWu5j9FJ0yup2 qKNT0H9gj69hs3i hRnG3CSGkVmrgvs 7JKWVk7BYeYIMyg scrk6f9Dsz8enwv VeFdPfgqBvHjo9k yPYPA6F8D3I. END KEYBASE SALTPACK SIGNED MESSAGE.
my log id: f8bb239353d8f886a108c51c

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 investigating the reported KBFS failure after a computer reset, using the supplied signed message and log id f8bb239353d8f886a108c51c. No source file, test, reproduction steps, or environment details are identified; done would mean KBFS is usable again after the reset.

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
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.