keybase / keybase/client

Linux client UnlockFolders paper key entry field does not receive keyboard input

Open
#12,461 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
9.2k
Forks
1.3k
Avg merge
12h 58m
Merged PRs (30d)
56

Description

#### Issue description
When attempting to enter a paper key into the client UI UnlockFolders window, none of my keyboard input is entered into the entry field. I can enter the paper key just fine if I initiate a rekey via the command line with `keybase rekey paper`.

Devices involved:
device_a : macOS 10.13.4 - keybase v 2.0.0-201806044163023+f899a761a7
device_b : Android 8.1.0 - keybase v 1.0.49-21080605022941+da5061f5ff
device_c : Pop!_OS (Ubuntu) 18.04 - keybase v 2.1.0-20180615162035+8625b772b1

#### Steps to reproduce the issue

1. add `device_c` using mobile app on `device_b`
2. create new paper key on `device_c` when prompted by client UI
3. rekey event is triggered
4. client UI opens UnlockFolders prompt for rekey using another connected client or paper key
5. click `Use a paper key instead`
6. Type

#### What's the expected result?

- Field populates with the characters I type or paste in

#### What's the actual result?

- Nothing gets entered into the field. Attempting to proceed results in an error 204 - not enough words entered for a paper key

#### Additional details / screenshot

- ![UnlockFolders1](http://s3.us-west-2.amazonaws.com/com.dsmall.general/share/screenshots/UnlockFolders_007.png)
- ![UnlockFolders2](http://s3.us-west-2.amazonaws.com/com.dsmall.general/share/screenshots/UnlockFolders_008.png)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the UnlockFolders paper-key prompt on the Linux client, then compare it with the working `keybase rekey paper` command. Done means the field accepts typed or pasted paper-key words and proceeding no longer reports error 204.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, linux
Domain
desktop, operating-systems
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.