GUI won't start after upgraded to 2.1.0
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
System Environment: Windows 7 x64
v2.0.0 ran pretty well before I chose to upgrade to 2.1.0.
I've tried reinstalling keybase app, renaming the old folder first then reinstall, but had no luck.
CLI client works fine.
While sending this log, there's a message saying:
"- INFO ignoring UI logs: GUI main process wasn't found"
It seems like the GUI refused to start, but I do see "keybase.exe", "upd.exe" and "kbfsdokan.exe" is running in the background.
my log id: 10b486ad4d8064c508da761c
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 by examining the Windows GUI startup path and the supplied log ID 10b486ad4d8064c508da761c, focusing on why the GUI main process is not found after upgrading from 2.0.0 to 2.1.0. Reproduce the upgrade on Windows 7 x64 and compare it with the working CLI client. Done means the GUI starts normally after the upgrade while the CLI and background services continue to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- electron, go
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100