The old logged-in-but-locked thing again
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
This morning when I made a build and updated in the test channel and rebooted, it was in the old logged-in-but-locked state, with no passphrase prompt, and accessing the kbfs drive was all balky, like with previous bugs.
my log id: 551f734d7ebb2c0e664a2a1c
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
Start with the provided log id 551f734d7ebb2c0e664a2a1c and the report of a test-channel update followed by reboot. Investigate the logged-in-but-locked state, missing passphrase prompt, and balky KBFS access; done means identifying and correcting the regression and confirming the prompt and drive access work after reboot.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100