search

keybase / client

Keybase Go Library, Client, Service, OS X, iOS, Android, Electron
BSD 3-Clause "New" or "Revised" License
8.89k stars 1.23k forks source link

run_keybase still stuck on loading #6517

Open keeGAsIydnA opened 7 years ago

keeGAsIydnA commented 7 years ago

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

cjb commented 7 years ago

Now the error is $HOME/.local/share/keybase/keybase.leveldb: permission denied, suggesting that you missed removing some root-owned config files.

keeGAsIydnA commented 7 years ago

Thank you for putting up with my ignorance. I'll now know to look through the entire home folder when deleting config files. I had deleted .config/keybase but not .local/share. And thank you for all your hard work on this.

Alan-R commented 6 years ago

I have the same problem - but I've never run it as root. I did a killall of everything that was related to keybase, removed the files from the two mentioned directories, and still no joy when trying it over. I'm running Ubuntu 16.04 LTS. { "nodename": "servidor", "operating-system": "GNU/Linux", "machine": "x86_64", "processor": "x86_64", "hardware-platform": "x86_64", "kernel-name": "Linux", "kernel-release": "4.4.0-96-generic", "kernel-version": "#119-Ubuntu SMP Tue Sep 12 14:59:54 UTC 2017", "Distributor ID": "Ubuntu", "Description": "Ubuntu 16.04.3 LTS", "Release": "16.04", "Codename": "xenial" }

educatedwarrior commented 6 years ago

I'm running 18.04 and I'm having the issue right now. I'm not running keybase as root user. Log 59d56ec4fcaa1a19c4eb731c

strib commented 6 years ago

Logs for the above: 59d56ec4fcaa1a19c4eb731c

strib commented 6 years ago

@educatedwarrior your error is:

/opt/keybase/Keybase: error while loading shared libraries: libasound.so.2: cannot open shared object file: No such file or directory

@cjb @oconnor663 @buoyad @joshblum is there a new dependency on libasound that needs to go into the linux packaging?

educatedwarrior commented 6 years ago

Do you guys keep versions of the linux package.. I don't want to blindly install new updated packages if they haven't been tested by our internal team. Also, does keybase autoupdate? That might be risky. I'm running in docker container.

strib commented 6 years ago

@educatedwarrior there are some old linux versions here: https://s3.amazonaws.com/prerelease.keybase.io/linux_binaries/deb/index.html

Though I don't know which one introduced this bug, or even if it's new.

Keybase doesn't auto-update on Linux, we rely on people to update it through their package managers.

educatedwarrior commented 6 years ago

Thanks @strib , I found out what my issue was. In docker I had multiple containers linked to the same docker volume/keybase home directory. I guess it corrupted the directory. Thanks for the help!!