keybase / keybase/client

Can't open keybase GUI after reboot system when I finished installing the new version.

Open
#8,865 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

I downloaded the old version of 1.0.31 setup file and forgot to install it. Today I remembered this app and ran the setup.exe to install it. After installation finished, I found that there was no K: drive in Explorer and the GUI kept saying that my encrypted folders were not showed in Explorer. So I re-download the setup file from official website and ran it again to overwriting existing files. After the new version of 1.0.33 setup finished it asked me to restart computer. I clicked the restart button to do so. When I returned to the desktop I found that I couldn't open it anyway. No error no UI.

My system is Windows 10 Pro.

And I already have a drive named K because I have a lot of hard disks in my computer.

my log id: ea76611e8256bff4db13971c

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 log ID ea76611e8256bff4db13971c and reproduce the Windows 10 installation and reboot sequence described in the report. Check why the GUI does not open after reboot and whether the existing K: drive affects encrypted-folder visibility; done means the GUI opens and the folders appear in Explorer.

Written by the indexing model from the issue text.

Assessment

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