Unable to start UI on new Linux install
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
[write something useful and descriptive here]
my log id: 6b2d5e2ccdaf3912f3e86f1c
○ → keybase log send
This command will send recent keybase log entries to keybase.io
for debugging purposes only.
These logs don’t include your private keys, encrypted data or file names,
but they will include metadata Keybase normally can't read
(like file sizes and git repo names), for debugging purposes.
Continue sending logs to keybase.io? (type 'YES' to confirm): yes
Enter feedback (or to send): Fails to start the UI on linux desktop
More feedback (or press when done): Running Fedora 30 on new laptop.
More feedback (or press when done):
▶ INFO ignoring UI logs: GUI main process wasn't found
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 reproducing the UI startup failure on Fedora 30 using the reported log id 6b2d5e2ccdaf3912f3e86f1c and the feedback that the GUI main process was not found. Identify the relevant UI startup entry point from the repository, then confirm the cause and document a verified fix or reproduction result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100