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

Database Error after upgrading from kdewallet5 to kdewallet6 #7117

Closed
2 tasks done
andrewrk opened this issue Dec 12, 2024 · 2 comments
Closed
2 tasks done

Database Error after upgrading from kdewallet5 to kdewallet6 #7117

andrewrk opened this issue Dec 12, 2024 · 2 comments

Comments

@andrewrk
Copy link

Using a supported version?

  • I have searched searched open and closed issues for duplicates.
  • I am using Signal-Desktop as provided by the Signal team, not a 3rd-party package.

Overall summary

Database Error

Unable to access the database encryption key because the OS encryption keyring backend has changed from kwallet5 to kwallet6. This can occur if the desktop environment changes, for example between GNOME and KDE.

Please switch to the previous desktop environment or try to run signal with the command line flag --password-store="kwallet5"

Frankly, as a user, this advice is offensive. I'm not going to revert to the previous desktop environment, I'm going to keep using my damn computer. Just make it fucking work, or you're going to hemorrhage users.

Steps to reproduce

  1. Install signal-desktop on KDE Plasma 5
  2. Send a message
  3. Close signal-desktop and upgrade system to KDE Plasma 6
  4. Run signal-desktop and observe the faulty behavior

Expected result

Start the application.

Actual result

Application not started.

Screenshots

image

By the way the "Copy error and quit" button fails to copy the text.

Signal version

7.35.0

Operating system

Linux 6.12.3

Version of Signal on your phone

No response

Link to debug log

No response

@andrewrk
Copy link
Author

By the way, running the app with --password-store="kwallet5" works - so just make the application do that instead of printing an error and quitting!

@trevor-signal
Copy link
Contributor

By the way, running the app with --password-store="kwallet5" works - so just make the application do that instead of printing an error and quitting!

Thank you for this suggestion, and I'm sorry for the bad experience. We are actively looking into ways of making this experience nicer while ensuring the encryption of your database.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants