keybase / keybase/client

Path not set in Windows for GUI installation

Open
#3,843 5 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

Keybase GUI Version: 1.0.16-20160713110836+a1c00b3

I first installed the keybase GUI version on my computer that already had keybase installed on it. I was running command line keybase commands to try and enroll my other computer, as suggested in the GUI, but the commands wouldn't work. So I ran a keybase update figuring there was a further update. However, I quickly figured out that I was still using the "old" keybase, so two things here.

  1. the old version of keybase should be uninstalled prior to installing GUI keybase. There's nothing in the instructions that this should happen, or instructions on HOW to make this happen
  2. the path doesn't get set in Windows by the installation. This should be part of the installation package or the user should be told to set the path to the new installation directory and what that directory is

Thanks!

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 reviewing the Windows GUI installation flow and the instructions for users who already have command-line Keybase installed. Reproduce the installation on Windows, then verify that the old version is handled and that the new installation directory is available on PATH.

Written by the indexing model from the issue text.

Assessment

Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.