keybase / keybase/client

run_keybase still stuck on loading

Open
#6,517 9 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

Hi this is a follow up to issue # 6453 Just want to get it back to top of the queue. I also composed this message on #6453...
Hi sorry to bother you again. But I'm still having a problem running on laptop. It still just hangs at loading... I uninstalled/removed all left behind config files and then reinstalled and have been trying to run it without root. I'm still getting the same problem. Just to try to recreate the issue I installed it on a vm that is KDE Neon. Followed the same directions and this one starts right up no problem. More background info...I also decided to reset my keys/account - still no luck. And I've also attempted to login from terminal and get the error... ERROR dial unix /run/user/1000/keybase/keybased.sock: connect: no such file or directory
The new keybase log send id is 4e8e3b0d8b42e7fe924e171c
Thanks for any help you can give. Its not the end of the world I can just use the vm. I'd just like to get it working if possible.
my log id: 4e8e3b0d8b42e7fe924e171c

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 issue #6453 and the Keybase log for ID 4e8e3b0d8b42e7fe924e171c. Investigate the run_keybase startup path and the missing /run/user/1000/keybase/keybased.sock connection described by the terminal error. Done means the client no longer remains stuck on loading and terminal login works on the affected laptop.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.