keybase / keybase/client

Unable to upload files - kbfs not running?

Open
#9,093 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

acked
Dominant language
Go
Stars
9.2k
Forks
1.3k
Avg merge
12h 58m
Merged PRs (30d)
56

Description

my log id: dae8802f654a347445e4621c

colin@colin-chat-dev ~ % curl -O https://prerelease.keybase.io/keybase_amd64.deb
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 75.0M 100 75.0M 0 0 27.4M 0 0:00:02 0:00:02 --:--:-- 27.4M
colin@colin-chat-dev ~ % sudo dpkg -i keybase_amd64.deb
[sudo] password for colin:
(Reading database ... 174216 files and directories currently installed.)
Preparing to unpack keybase_amd64.deb ...
Unpacking keybase (1.0.34-20171012160058.c282fb227) over (1.0.34-20171012160058.c282fb227) ...
Setting up keybase (1.0.34-20171012160058.c282fb227) ...
Processing triggers for mime-support (3.59ubuntu1) ...
Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
colin@colin-chat-dev ~ % run_keybase
Unmounting /keybase...
Shutting down kbfsfuse...
Shutting down keybase service...
Launching keybase service...
Mounting /keybase...
Launching Keybase GUI...
Success!
▄▄▄▄█▀
╭───────────────────────╮ ▄▄ ▄▄▄█▄▄▀
│ │ ███▄▄▄▄▄▄▄▄▄▄███▄██
│ Encrypt everything! │ ▄▄▄████▄▄▄███████████
│ ├──── ▄▄▄▄▄████▄█████████████
╰───────────────────────╯ ███▄█▄█████████████████▄▄
▀▄███████▄▀ ███████████▄▄
▄▄▄▄███ ███████████▄▄
▄████████ ██████████████
▄███▄█████▄▄ ▀▄████████████
███████▄▄██▄█▄▄ █████████████
▄▄█████████████▄▄ ████████████
▄██▄▄████▄▄▄█▄▄█████ ████████████
███▄▄▄▄▄███████▄▄█████████▄▀
▄█████▄▄█████████████▄█████
█▄██████████▄▄▄▄▄▄▄███████
▄▄▄▄▄██▄▄█████▄████████████
▀▀▀▀▀▀▀▀▄▄▄▄██▄▀ ▀▀▄▄▄▄▄▄▀▀▀
▀▀▀▀▀▀▀▀▀
colin@colin-chat-dev ~ % keybase chat upload ... foo
▶ ERROR Keybase services aren't running - KBFS client not found. On Linux you need to start them after an update with run_keybase command.

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 failure with run_keybase followed by keybase chat upload, using the log and command output in the issue. Trace the KBFS client startup and chat upload entry points to determine why the command reports that services are not running; done means the upload command works after the documented update sequence.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.