Cannot submit log
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
This is similar, but not matching to #3934
While reporting #4342, I noticed that the client keeps saying that the log files it's trying to submit don't exist on the path it's trying to use.
✘ [username]@[hostname] ~ 23s $ keybase log send
zsh: correct 'log' to 'logs' [nyae]? n
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
▶ INFO ignoring error getting keybase status: dial unix /run/user/1000/keybase/keybased.sock: connect: connection refused
▶ WARNING error opening log "/home/[username]/.cache/keybase/keybase.kbfs.log": open /home/[username]/.cache/keybase/keybase.kbfs.log: no such file or directory
▶ WARNING error opening log "/home/[username]/.cache/keybase/Keybase.app.log": open /home/[username]/.cache/keybase/Keybase.app.log: no such file or directory
▶ WARNING error opening log "/home/[username]/.cache/keybase/keybase.updater.log": open /home/[username]/.cache/keybase/keybase.updater.log: no such file or directory
▶ WARNING error opening log "/home/[username]/.cache/keybase/keybase.start.log": open /home/[username]/.cache/keybase/keybase.start.log: no such file or directory
System info is the same:
[username]@[hostname] ~ 14s $ gpg --version
gpg (GnuPG) 2.1.15
libgcrypt 1.7.3
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Home: /home/[username]/.gnupg
Támogatott algoritmusok:
Nyilvános kulcsú (pubkey): RSA, ELG, DSA, ECDH, ECDSA, EDDSA
Rejtjelező (cipher): IDEA, 3DES, CAST5, BLOWFISH, AES, AES192,
AES256, TWOFISH, CAMELLIA128, CAMELLIA192,
CAMELLIA256
Kivonatoló (hash): SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Tömörítő (compression): tömörítetlen, ZIP, ZLIB, BZIP2
[username]@[hostname] ~ $ keybase --version
keybase version 1.0.17
[username]@[hostname] ~ $ cat /etc/*-release
DISTRIB_ID=ManjaroLinux
DISTRIB_RELEASE=16.08
DISTRIB_CODENAME=Ellada
DISTRIB_DESCRIPTION="Manjaro Linux"
Manjaro Linux
NAME="Manjaro Linux"
ID=manjaro
PRETTY_NAME="Manjaro Linux"
ANSI_COLOR="1;32"
HOME_URL="http://www.manjaro.org/"
SUPPORT_URL="http://www.manjaro.org/"
BUG_REPORT_URL="http://bugs.manjaro.org/"
my log id: e30c4b0b8227ddae09a2691c
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the keybase log send command on the reported Manjaro and Keybase 1.0.17 setup, then trace how it selects the log paths shown in the warning output. Done means the command finds the applicable logs and submits them without reporting expected log files as missing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100