-
Notifications
You must be signed in to change notification settings - Fork 14
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
[Bug]: signal-desktop does not start due to database-error #300
Comments
Hi - is this the first time you've used the snap, or has it started happening since an update? |
I observe this since a few days/weeks. Before it worked without issues for some years. |
Hmm, I'd be interested to see the state of the "corrupted" file - I'd be surprised if this is as a result of the snap packaging. There does seem to be an upstream issue, along with some steps for recovery - are you able to confirm if those steps work for you? signalapp/Signal-Desktop#4513 |
Ahh another potential lead here - how's the disk space on your machine? |
Disk space seem not to be an issue, whence
|
In the first link I did not find hint for recover from a corrupted database. Also if I |
Assuming you have a backup of the messages on another device, you could try |
Yes, that did not change the behavior. |
Hmm, I'm a little lost on this one for now. Are you able to confirm if the behaviour happens if you install Signal from the deb? |
I have no other option than Snap on fedora, afaik. |
Correction: while I did not find signal-desktop in the repositories accessible with |
Hi also happen to me, started on rev673
on fresh install everything ok , but after next run always broken. this is the log when running from console
|
Hi, also happened to me, seems related to cipher change at launch (cipher not recognized while opening database file, so considering database corrupt ?).
I tried to uninstall and re-install, I can launch the app and sync with the phone, but same error occurs at every launch, even on the first launch after a fresh install. I even tried to purge all with: |
Happened to my installation of signal-destop (7.17.0) a few days ago. |
Hmm, okay I think this was a bug in Signal 7.17. Looking at the comparison for 7.18 (released last night), there appear to be a few commits related to the sql database on Linux: signalapp/Signal-Desktop@v7.18.0...v7.17.0 I'll kick off the update now. |
Hi all - still waiting on the full build for arm64, but if you're on an amd64 machine, you should be able to try If you're installing from scratch it'll be |
@jnsgruk Just tried 7.18.0 with a fresh re-link, I still have the same database error upon restarting the application. |
Hmm, looks like this is also an issue on the Flatpak, and on other distros: signalapp/Signal-Desktop#6750 |
Problem is still here on 7.18 for me. I had to install 7.15 to get back on a crash-free version. (Source) So, whether in 7.16, 7.17 or 7.18, launching Signal-desktop causes a database file error that forces you to delete all the data in 7.17 and 7.18, but the error was recoverable in 7.16 (you had to choose to recover the database at launch). |
I've been trying to repro all morning and failed. Interesting that is on Fedora 40, which is also where the reported error is upstream. Is anyone on this thread seeing this with Ubuntu? |
@jnsgruk Yes I'm having that issue on Ubuntu 24.04 (kern 6.9.9) |
having this issue on Fedora 29 |
Now that's super odd. Can I ask if you're able to repro on a clean Noble VM? I've been trying to with that exact setup, and not been able to. |
Out of interest, if you run |
I'll try with a fresh VM and let you know |
I have the same issue, Fedora 40 (Linux 6.10.1-200.fc40.x86_64) here. |
I have the same issue in Ubuntu arm64 (ubuntu 24.04, Linux 6.1.0-1021-rockchip - Joshua Riek), on 4 machines. |
I have this issue on a new pop-os machine, using snap.
Been happening since we got the new machine about a month ago.
I'm trying the |
Yeh, I think this is the problem - this is not a snap packaging issue, and therefore unlikely we're going to be able to fix in this repository. |
I had the same database error this morning on Ubuntu 22.04.4 LTS immediately after installing the snap updates for signal-desktop.
I have the Linux kernel 6.5.0-45-generic I think this is caused by bug #6750 Frequent database errors that crashes Signal. Restart possible, but errors increasingly more frequent Another comment on this thread states that the deb package version also shows the error. What is the official and thus supported way to install Signal-Desktop on Ubuntu? We need to get our Signal-Desktop back on Ubuntu. Should I avoid updates for now? Thanks |
The official way is listed on the signal download page:
|
Works well unless you need arm64, in which case Snap is it. There's no other option. |
I have the exact same problem. Initial install runs good but a close and start will crash and give DB error. Running on: Revision 671 works !!! |
I have recently been having the same "Database Error" message upon opening my Signal desktop app version 7.19.1. while using Ubuntu 20.04 LTS. Have tried "Copy error and quit" but nothing happens. Also tried "Delete data and restart" multiple times and relinked my mobile each time but when I close down my desktop app it fails to start up again without going through the whole process I just described. I have uninstalled/reinstalled my desktop app multiple times as well and that also doesn't work to fix the issue. It appears this issue affects various Ubuntu users regardless of using a deb or snap package. Sure miss using my Signal desktop! |
The problem for me appears to be that the latest bundled version of better-sqlite3 is compiled against GLIBC_2.38 which core22 lacks.
|
Aha that's interesting - I'd not seen that before. That probably is something we can fix by building the better-sqlite binaries as part of our build process (currently we're fetching pre-built binaries from Signal). |
Just installed version 7.22.0 on Fedora 40 but the bug persists. The Flatpak version runs fine but I'd prefer using the snap app, if possible. |
Seems to be fixed by 7.22.1. Please update as soon as possible. |
I've kicked off our update/release process - will comment here when it's ready to test. |
No joy.
|
I installed 7.22.2, copied over the folder from an older version, and got Signal-desktop to start again. I lost all data since i made that copy, but at least it starts again. |
This feels like a separate issue to me, even if related. Can you file an issue to track that separately? Thank you! |
Okay - and you can open multiple times without seeing the original issue? |
Oops. No, I can not. |
@lizthegrey I did some investigation into your glibc library version mismatch, and I think it's a red herring. On 24.04 LTS, the command actually works and looks right (because the snap is built on
I do observe the same results as you on 22.04:
However, this is a little misleading, because we're running
Hopefully this clears things up a bit - although sadly we're no closer to solving the underlying issue, which I still believe to be an upstream bug. |
Are you in contact with upstream? Are they aware of this issue? It's probably better if you, as a maintainer, contacted them, not me as a random user. |
I have the same issue on Fedora 40. Signal is simply unusable. |
Yes, I've raised the issue a few times, contacted them out of band and tried to engage through other Github issues, but so far haven't really got any traction. |
I have same Issue on Rocky Linux 9.4 with latest updates Downgrading to 7.15.0 works as a workaround: |
Does this retain the chat history, done in the initial launch, of a broken version? |
I had different issue now with 7.15.0 when I had it running for a while - QR code to add new device popped up randomly after about 30 mins and chat history was gone on desktop each time I added desktop device back via mobile app. |
I'm still having the same issue with the new version. Testing requires linking a device and opening/closing the application to ensure it opens subsequent times without losing the data. |
...in the meantime, Signal is now available as a flatpak and .deb for aarch64/arm64 - https://signalflatpak.github.io/signal/ |
What happened?
Application starts and an error window pops upDatabase startup error:
When I follow the instructions and delete all data, I can re-connect the device to the account and send a message.
But after I close the app and try to start again, the same error window re-appears.
What should have happened?
signal-desktop should start without forcing me to delete data and re-connect.
Output of
snap info $snap_name
Output of
snap connections $snap_name
Output of
snap version
Relevant log output
Teminal output of app
The text was updated successfully, but these errors were encountered: