keybase / keybase/client

Client fails to load profile after install

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

When first installing Keybase from RPM and running run_keybase in a terminal, everything seems to work nicely, the squirrel comes up on the terminal and the GUI opens. Everything looks to be okay but the profile page comes up empty:
Keybase GUI

When navigating to devices tab, a prompt appears saying "Can't load devices". Other tabs seem to work just fine by the looks of it.

Quitting the client and then starting it again from the app drawer, the GUI loads up with the profile page and now I am presented with a PIN-prompt for the keybase passphrase. Entering the passphrase shows the policy change dialogue and confirming it leaves me with the empty profile page once more.

Devices tab lists all my devices and going back to the profile page finally loads the content as expected.

OS: Fedora 25 (64bit)
Keybase: version 1.0.20-20170329160043+6d18a6a
SELinux: Enforcing
Log ID after first start: a831fe31167bb188172db51c
Log ID after restart of the client: cdd49b7a83af6661f2d6081c

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 reproducing the first-launch path using the RPM and run_keybase on Fedora 25, then compare it with launching the client from the app drawer. Review the provided log IDs and verify that the profile and Devices tabs load correctly on the initial launch; the issue is done when they do.

Written by the indexing model from the issue text.

Assessment

Tech stack
fedora, go
Domain
desktop, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.