keybase / keybase/client

Installation problems

Open
#19,375 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 just installed on my Galaxy S5 (Marshmallow) phone. That went OK. (josephj11)
Then I went to my kubuntu 18.04 notebook and installed your deb. That went OK.
I tried to link from the phone to the notebook to setup the same account.
Several things wet wrong.
When I tried to scan the qr code displayed on the notebook onto the phone, the scanner window on the phone showed an image with the wrong aspect ratio - big black bands at top and bottom and wouldn't scan.
I tried entering the nine word secret instead twice, but kept getting messages about network timeouts.
I have 100/10 Internet service and fast WiFi, (Spectrum), so that shouldn't happen.
I will try logging in on the phone later to see if the problem is intermittent.

my log id: 98638eb8c1faaa04bacf201c

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

Reproduce the account-linking flow between the Galaxy S5 running Marshmallow and the Kubuntu 18.04 notebook installation. Start with the QR scanner's incorrect aspect ratio, then investigate the reported network timeouts using log ID 98638eb8c1faaa04bacf201c; done means both QR scanning and secret-based setup work reliably.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, ubuntu
Domain
desktop-dev, mobile-dev, networking
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.