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

Nheko loose auth when secret service is inactive #912

Closed
1 task
brainrom opened this issue Jan 30, 2022 · 2 comments
Closed
1 task

Nheko loose auth when secret service is inactive #912

brainrom opened this issue Jan 30, 2022 · 2 comments
Labels
bug Something isn't working secrets-service Issues relating to the secret service support required by Nheko

Comments

@brainrom
Copy link

Describe the bug

If nheko is unable to get secret key from secret service (keepass/gpasswd/kwallet), for example, if database is locked, nheko reset the authorization.

To Reproduce

  1. Login to matrix via nheko
  2. Close the nheko
  3. Close the secret service database
  4. Open nheko again and see that the auth is deleted.

What happened?

auth section disappears from nheko.conf, I need to re-login every time if I forgot to start keepass before nheko.

Expected behavior

Nheko should wait for secret service availability until user manually re-login to matrix.

Screenshots

No response

Version

0.9.1

Operating system

Linux

Installation method

Some repository (AUR, homebrew, distribution repository, PPA, etc)

Qt version

No response

C++ compiler

No response

Desktop Environment

No response

Did you use profiles?

  • Profiles used?

Relevant log output

[2022-01-30 18:04:44.617] [ui] [info] starting nheko 0.9.1
[2022-01-30 18:04:44.723] [db] [debug] setting up cache
[2022-01-30 18:04:44.779] [db] [debug] Restored empty secret 'matrix........=.m.cross_signing.master'.
[2022-01-30 18:04:44.780] [db] [debug] Restored empty secret 'matrix......=.m.cross_signing.self_signing'.
[2022-01-30 18:04:44.780] [db] [debug] Restored empty secret 'matrix......=.m.cross_signing.user_signing'.
[2022-01-30 18:04:44.780] [db] [debug] Restored empty secret 'matrix......=.m.megolm_backup.v1'.
[2022-01-30 18:04:44.781] [db] [debug] Restored empty secret 'nheko........=.pickle_secret'.
[2022-01-30 18:04:44.781] [db] [info] database ready
[2022-01-30 18:04:44.781] [db] [info] restoring state from cache
[2022-01-30 18:04:44.783] [crypto] [critical] failed to restore olm account: unpickle: BAD_ACCOUNT_KEY
[2022-01-30 18:04:44.783] [ui] [info] dropping to the login page: Не удалось восстановить учетную запись OLM. Пожалуйста, войдите снова.
[2022-01-30 18:04:44.784] [db] [info] deleted cache files from disk
[2022-01-30 18:04:44.812] [db] [warning] Storing secret 'pickle_secret' failed: No such object path '/org/freedesktop/secrets/aliases/default'

Backtrace

No response

@brainrom brainrom added the bug Something isn't working label Jan 30, 2022
@brainrom brainrom changed the title Nheko loose auth when secrete service is inactive Nheko loose auth when secret service is inactive Jan 30, 2022
@deepbluev7
Copy link
Member

Are you sure that happens with all secrets services or just keepassXC? Because the latter has a known bug in 2.6.6 and a fix for that is in 2.7.0. See #802 and keepassxreboot/keepassxc#6943

@deepbluev7 deepbluev7 added the secrets-service Issues relating to the secret service support required by Nheko label Jan 30, 2022
@deepbluev7
Copy link
Member

Because of a lack of feedback and because I am assuming this is just #802, I'll close this for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working secrets-service Issues relating to the secret service support required by Nheko
Projects
None yet
Development

No branches or pull requests

2 participants