-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Frequent database errors that crashes Signal. Restart possible, but errors increasingly more frequent #6750
Comments
@cyberwolfie1 Could you provide a full debuglog? |
@jamiebuilds-signal Here you go: https://debuglogs.org/desktop/6.44.0/695b30fe47078784c0a2a70354901062db05cd55a9e055cb5188537693e7da45.gz To add: I can't see that any particular action causes this. It happens seemingly randomly, and often when I don't have focus on the window as well. No messages received at the time of crash. It can crash within the first minute of opening, and sometimes it can stay open for longer durations. |
Thank you for the log. We'll take a look! |
I had a similar thing happen just now.
|
@maxguru oof, I'm sorry to say it, but in your case the database appears to be pretty badly corrupted and cannot be automatically recovered. Was there a sudden crash or maybe power went out recently? |
No, it just randomly crashed with some sort of JS error popup. No power issues whatsoever. Uptime is 18 days. However, I was having strange issues with flatpak (apps not starting in some situations), so, maybe flatpak caused it. Otherwise, maybe it was some kind of hack coming from an inbound message. |
An update from my side: it has been very stable the last couple of days with no crashes. I have not updated the client. |
started crashing same way for me too now |
@emko sorry this is happening for you, can you please share a debug log? and i'm curious if anything happened prior to the issue (app update, system power lost, etc) |
|
@emko Thanks for the log! First, I noticed you're using flatpak and we currently don't support unofficial builds. We will do our best effort. Regarding the actual error, it looks like If you continue to experience it, please open a new issue for |
Just fyi: Same experience on |
@theborakompanioni Sorry this is happening -- is this also on the flatpak? If so I'd suggest to check the maintainer's issue tracker to see if there's anything relevant there. |
Don't be sorry. Might be totally outside of your control. As far as I am aware, this was installed via |
Hello there,
|
I also ran into this issue on 7.17 (it started crashing on some of the startups, possibly Wayland-related, and sometimes complained about the database, but was recoverable) and 7.18 ( |
Having the same issue with 7.17 and 7.18 (snap version) |
This issue has diverged from OP's issue, which was database corruption during normal operation. Regarding community packages such as flatpak or snap, we don't build them and we also don't have bandwidth to develop on them right now. It seems like in the packaged environment there's an issue using the GNOME keyring and/or electron safeStorage API. You could experiment with turning it off by running the app with the command line arg More info on the |
Has Signal's usage of the keyring fundamentally changed? It doesn't make a lot of sense to me that this is a confinement issue - particularly that it's happening across two completely discrete packaging systems? What's in the logs there that suggests no communication with the GNOME keyring? |
I'm using a Fedora COPR, by the way. Yes, I understand it's not supported. |
Similar reports of the deb version supplied by Signal exhibiting the same behaviour on Ubuntu: snapcrafters/signal-desktop#300 (comment) |
So, the version from the snapstore should be avoided for now? |
The snap is not maintained or supported by Signal - and never has been. That said, given that people are experiencing this with the official deb, the Fedora COPR package, and the snap - it seems likely that it's not a packaging issue. |
Since my last post, where this issue had completely gone, it has now started again. I am still on the .deb-package. Double error message now, same as is mentioned in the issue @jnsgruk linked to. |
@cyberwolfie1 What's the exact error message you see when it crashes? If it's a database corruption error, is there anything that might have prevented Signal Desktop from accessing your database password through Electron's safeStorage API? Or perhaps you've changed desktop environments, and Signal Desktop no longer has access to your previous protected storage system? |
+1, experiencing the same on Fedora 40 with Signal installed via Flathub. Running via terminal I see these errors:
|
@adioe3 What is the history of your desktop instance, and the computer it's installed on? Did you have a hard reset or power loss? That can sometimes cause database corruption. Also, taking a backup in the middle of the application running then restoring it - the database file can be only partially-written in that case, and can cause this. |
Cannot speak for @adioe3, but here happens every time the app is started. Needs re-linking, after closing the app, the problem reappears. |
Came here because of the same issue on freshly installed Bazzite, even just logging out the current user makes Signal throw the "database error occurred" next time I try to start it up. Installed with a flatpak. |
Same as @theborakompanioni , nothing special simply started the app. It's a Framework 13 laptop so it could be it ran out of battery and powered off but doubt that would cause corruption. Today I get this error:
Note I have made no changes aside from keeping my system up-to-date with At the moment, I cannot start Signal at all and have lost all the data I had on this laptop which is, not gonna lie, a little frustrating. |
Error log:
|
After manually deleting the database from
This line is very interesting:
thing is you don't seem to actually log the SQL errors so it's hard to say what goes wrong. |
Happens with 100% reproducibility on my current Fedora 40 laptop. Signal-desktop is installed as a snap application (as there are no native Fedora RPMs.) |
What fixes it for me was:
and now I can use desktop again until this is fixed. |
Hi, I'm relatively new to Linux and I'm experiencing the same issue with Signal on Fedora. I want to understand the command better. Additionally, the This information is pretty clear. However, could you please explain what the name org.freedesktop.Secrets is? |
"Same," although I suspect in my case it is (almost) always after crash / power loss. I don't think that a power loss should be able to corrupt my chat history so hard it needs to be wiped... file ~/.config/Signal/sql
# db.sqlite: data
sqlite3 ~/.config/Signal/db.sqlite ".dump" # ".recover" doesn't work either
# sql error: file is not a database (26)
# PRAGMA foreign_keys=OFF;
# BEGIN TRANSACTION;
# /**** ERROR: (26) file is not a database *****/
# ROLLBACK; -- due to errors I'm on Arch, signal-desktop 7.28.0-1 from extra, no snap/flatpak.
|
To anyone who finds this thread and happens to be on Fedora, use the NATIVE PACKAGE. The flatpak build seems to cause this issue |
Using a supported version?
Overall summary
This is possibly related/duplicate of #6639 and #3180, although different operating systems and not the same behavior, so I am submitted a separate ticket because of that.
For some time I have been getting database errors occasionally when opening Signal. I would not have to delete the database, but could click "Copy error and exit" and then immediately reopen Signal and it would work fine.
Recently (during the last week) Signal has also started crashing in use. It would never do this before. I can still restart Signal as I would before when this happens, without having to delete the database.
Whenever I click "Copy error and exit", nothing is copied to my clipboard, but I have pasted in the last lines of
~/.config/Signal/logs/main.log
below that shows that there is some corruption in the SQL database.I have as of yet not experienced any issues running the mobile version on Android.
I am running Signal v. 6.44.0 on Tuxedo OS 2, installed via commands found here https://signal.org/download/linux/
Steps to reproduce
Before:
Now:
2a. Occasionally get Database error-popup
3a. Click "Copy error and exit" and relaunch Signal
or.
2b. Successfully use Signal for a while, then Signal crashes and Database error-popup shows
3b. Click "Copy error and exit" and relaunch Signnal
Expected result
That Signal should not crash.
Actual result
Signal sometimes crashes upon start and during operation with an error message saying there is a Database error. I can restart Signal and use it again for some time before it crashes again.
Last lines from
~/.config/Signal/logs/main.log
:Screenshots
Signal version
6.44.0
Operating system
Tuxedo OS 2
Version of Signal on your phone
No response
Link to debug log
No response
The text was updated successfully, but these errors were encountered: