keybase / keybase/client

keybase.updater.log: no such file or directory

Open
#3,934 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 ran keybase -d --gpg /usr/bin/gpg2 pgp select 838c6d6c91d0aa8e09e621a1c3e294dcc05b414 then keybase log send.

$ keybase log send
This command will send recent keybase log entries to keybase.io
for debugging purposes only.

These logs don’t include your private keys or encrypted data,
but they will include filenames and other metadata keybase normally
can’t read, for debugging purposes.

Continue sending logs to keybase.io? (type 'YES' to confirm): YES
▶ WARNING error opening log "/home/yautweh/.cache/keybase/keybase.updater.log": open /home/yautweh/.cache/keybase/keybase.updater.log: no such file or directory


------------
Success! Your log ID is:

  559c73e2b32b5de05bf1521c

Here's a URL to submit new bug reports containing this ID:

  https://github.com/keybase/client/issues/new?body=[write%20something%20useful%20and%20descriptive%20here]%0A%0Amy%20log%20id:%20559c73e2b32b5de05bf1521c

Thanks!
------------

This error also occurred when sending the log referencing this comment.

$ keybase version
Client:  1.0.17-20160816160049+f27f469
Service: 1.0.17-20160816160049+f27f469

On latest stable Ubuntu Xenial (server; no gtk/gui).

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 keybase log send on Ubuntu Xenial and inspect how it handles the reported /home/yautweh/.cache/keybase/keybase.updater.log path. Use the reported Keybase version and command output as the baseline; done means the missing updater log is handled without the warning while log sending still completes.

Written by the indexing model from the issue text.

Assessment

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