Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem: Adding chain-maind keys will not be actually stored in disk #437

Closed
maannajjar opened this issue Mar 27, 2021 · 10 comments
Closed
Assignees

Comments

@maannajjar
Copy link

Describe the bug
Whenever I try to add new key, or import new one. Then type list the keys it returns an empty list

To Reproduce

  1. chain-maind keys add Default (or chain-maind keys import Default key_file)
  2. Type the encryption password for the key
  3. chain-maind will print new key details with recovery keys
  4. Run chain-maind keys list, the output will be []

Expected behavior
chain-maind keys list should output list including the newly added key

Screenshots
See following example (those keys are for testing only and are not used or maintained)
chain-maind

Desktop (please complete the following information):

  • OS: Linux , Pop OS 20.10 (Based on Ubuntu 20.10)
  • Browser None
  • Version Ubuntu 20.10 / Linux 5.8.0-7642-generic #47~1612288990~20.10~b8113e7-Ubuntu SMP Wed Feb 3 02:27:26 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

Additional context
I tested the same commands in macOS and I was unable to reproduce this bug. Seems to be only happening in Linux

@tomtau
Copy link
Contributor

tomtau commented Mar 29, 2021

@maannajjar can you try with 1.2.0? also, do you run a headless distribution or do you have some GUI (e.g. gnome)? For the default keyring backend: https://docs.cosmos.network/master/run-node/keyring.html#the-os-backend -- one may need e.g. Seahorse on Linux.

@maannajjar
Copy link
Author

@tomtau I tried with 1.2.0 but it didn't work too. I'm running with Gnome GUI. When adding new key I do get the keyring prompt to create password for the new key (screenshot 1). I also opened the keyring management and I saw all the keys that were created by chain-maind (screenshot 2). I was able to unlock them using the passwords I used. I also tried unencrypted key (empty password), but that also didn't work.

keyring-prompt

keyring

@wolfwolker
Copy link

same behaviour described by @maannajjar happening here. I'm using popOS 18.04 [derivated from ubuntu]

@leejw51crypto
Copy link
Contributor

i'm checking this issue in ubuntu

@leejw51crypto
Copy link
Contributor

reproduced it, i'll fix it

before fixed, you can use)
chain-maind keys list --keyring-backend file

@leejw51crypto
Copy link
Contributor

found the cause, working on now.

@crypto-org-chain crypto-org-chain deleted a comment Mar 31, 2021
@crypto-org-chain crypto-org-chain deleted a comment Mar 31, 2021
@crypto-org-chain crypto-org-chain deleted a comment Mar 31, 2021
@crypto-org-chain crypto-org-chain deleted a comment Mar 31, 2021
@crypto-org-chain crypto-org-chain deleted a comment Mar 31, 2021
@tomtau
Copy link
Contributor

tomtau commented Mar 31, 2021

should be fixed with 99designs/keyring#83

@leejw51crypto
Copy link
Contributor

leejw51crypto commented Mar 31, 2021

to make it work on linux
keyrings folder)
$HOME/.local/share/keyrings

  1. add this line, top folder's go.mod
replace github.com/99designs/keyring => github.com/leejw51crypto/keyring v1.1.6-gnome
  1. make

leejw51crypto added a commit to leejw51crypto/chain-main that referenced this issue Mar 31, 2021
@leejw51crypto
Copy link
Contributor

before keyring is changed,
please use this branch @maannajjar

https://github.com/leejw51crypto/chain-main/tree/feature/437

@maannajjar
Copy link
Author

Awesome thanks @leejw51crypto I will try it out!

leejw51crypto added a commit to leejw51crypto/chain-main that referenced this issue Apr 20, 2021
leejw51crypto added a commit to leejw51crypto/chain-main that referenced this issue Apr 20, 2021
…ix crypto-org-chain#437)

update vendorsha256

Update go.mod

thanks

Co-authored-by: Tomas Tauber <2410580+tomtau@users.noreply.github.com>

go mod tidy
leejw51crypto added a commit to leejw51crypto/chain-main that referenced this issue Apr 20, 2021
…ix crypto-org-chain#437)

update vendorsha256

Update go.mod

thanks

Co-authored-by: Tomas Tauber <2410580+tomtau@users.noreply.github.com>

go mod tidy

add todo
leejw51crypto added a commit to leejw51crypto/chain-main that referenced this issue Apr 21, 2021
…ix crypto-org-chain#437)

update vendorsha256

Update go.mod

thanks

Co-authored-by: Tomas Tauber <2410580+tomtau@users.noreply.github.com>

go mod tidy

add todo

increase time

fix lint issue
leejw51crypto added a commit to leejw51crypto/chain-main that referenced this issue Apr 21, 2021
…ix crypto-org-chain#437)

update vendorsha256

Update go.mod

thanks

Co-authored-by: Tomas Tauber <2410580+tomtau@users.noreply.github.com>

go mod tidy

add todo

increase time

fix lint issue

replace jwt-go

update nix

fix gomod2nix

restore gomod2nix

remove vendorPath
@tomtau tomtau closed this as completed in 4286599 Apr 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants