keybase / keybase/client

Errors when logging into Keybase using the GUI

Open
#5,072 0 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've had a couple of different errors appear when trying to set a friendly name for a new device that I've just logged into from the Keybase GUI. One of them mentioned something about getHostNode(); the other was different but I have, alas, forgotten the message.

I've since had an email confirming that the device has, in fact, been added to Keybase, but I can't get the GUI to move beyond the name-setting screen.

Ubuntu Linux, 64bit, amd64 package.

my log id: 1da20982fbc11df4f7c4261c

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

The report concerns the Keybase GUI login and device-friendly-name flow and mentions getHostNode() plus log ID 1da20982fbc11df4f7c4261c; start by searching the client for getHostNode() and correlating that log. Done means reproducing the issue on Ubuntu Linux amd64 and allowing a newly added device to leave the naming screen without errors.

Written by the indexing model from the issue text.

Assessment

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