-
Notifications
You must be signed in to change notification settings - Fork 37
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 update to 7.29 #774
Comments
So, with the previous versions, you set |
Yes, I set that specifically on the last version (7.28). After setting it, I had quit Signal once and restarted it, and everything worked correctly. I think I'll give up on restoring my profile and test switching the password store back and forth to see if I can contribute helpful information. |
You can't reverse the change once you used the keyring (e.g. with It is a one-way ticket. This will also have an effect, if someone changes from Gnome to KDE. |
Understood. I have done that and determined that this is not a 7.29 upgrade issue. |
When launching signal after the latest update
76af70909d865cc325ad167c2cc52961491bcd5e290daa902d7e39833ea4796b
, I got the following dialog"Copy error and quit" doesn't copy anything, so I relaunched Signal from terminal
I thought this is just an issue with the latest update, so I downgraded and relaunched signal, but issue persists
$ sudo flatpak update --commit=be19a23652d102b0f87106609b06a7f50972bfae7540a02767a04bf1ae169cd7 org.signal.Signal
If it's relevant at all, I have recently changed the following environment variable
SIGNAL_PASSWORD_STORE=basic
->SIGNAL_PASSWORD_STORE=gnome-libsecret
But I had since relaunched Signal and verified that it worked ok with the new setting.
For troubleshooting this, I tried reverting the change but I got a different (expected) Databse Error:
The text was updated successfully, but these errors were encountered: