Open KlausC opened 1 month ago
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? https://github.com/signalapp/Signal-Desktop/issues/4513
Ahh another potential lead here - how's the disk space on your machine?
Disk space seem not to be an issue, whence /var/lib/snap/
subdirs seem all to be complete:
/dev/loop17 188160 188160 0 100% /var/lib/snapd/snap/spotify/77
/dev/loop18 192384 192384 0 100% /var/lib/snapd/snap/signal-desktop/675
/dev/loop16 52608 52608 0 100% /var/lib/snapd/snap/nps-ssh-askpass/205
/dev/loop19 186240 186240 0 100% /var/lib/snapd/snap/spotify/78
/dev/loop20 84096 84096 0 100% /var/lib/snapd/snap/whatsdesk/28
tmpfs 8036488 92 8036396 1% /tmp
/dev/nvme0n1p2 996780 273304 654664 30% /boot
/dev/nvme0n1p3 975097856 641286056 326005032 67% /btrfs_pool
/dev/nvme0n1p3 975097856 641286056 326005032 67% /home
In the first link I did not find hint for recover from a corrupted database. Also if I snap remove signal-desktop
and check the ~/snap/signal-desktop
is empty, the bug persists after snap install signal-desktop
and re-connect and re-start as described in the OP.
Assuming you have a backup of the messages on another device, you could try snap remove --purge signal-desktop
, then reinstall?
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 dnf
, it was possible to install from the fedora software
GUI. After removing the snap version, that seems to work now with version 7.17.
Of course the local copy of my chats are lost; but still available on my Android mobile.
Hi also happen to me, started on rev673
debian 12 Debian 6.7.12-1~bpo12+1 xfce
snap signal-desktop v7.17.0 rev675
on fresh install everything ok , but after next run always broken. this is the log when running from console a lot of REDACTED part don't know what its means.
{"level":40,"time":"2024-08-01T02:24:49.409Z","msg":"MainSQL: Database log code=26: file is not a database in \"PRAGMA journal_mode = WAL\""}
{"level":30,"time":"2024-08-01T02:24:49.409Z","msg":"MainSQL: migrateDatabase: Migration without cipher change failed"}
{"level":40,"time":"2024-08-01T02:24:49.461Z","msg":"MainSQL: Database log code=26: statement aborts at 2: [PRAGMA user_version] file is not a database"}
{"level":50,"time":"2024-08-01T02:24:49.461Z","msg":"MainSQL: Database startup error: SqliteError: file is not a database\n at Database.pragma ([REDACTED]/node_modules/@signalapp/better-sqlite3/lib/methods/pragma.js:11:31)\n at getUserVersion ([REDACTED]/ts/sql/util.js:132:13)\n at migrateSchemaVersion ([REDACTED]/ts/sql/Server.js:389:54)\n at openAndMigrateDatabase ([REDACTED]/ts/sql/Server.js:420:3)\n at openAndSetUpSQLCipher ([REDACTED]/ts/sql/Server.js:435:14)\n at Object.initialize ([REDACTED]/ts/sql/Server.js:471:16)\n at MessagePort.<anonymous> ([REDACTED]/ts/sql/mainWorker.js:84:35)\n at [nodejs.internal.kHybridDispatch] (node:internal/event_target:820:20)\n at MessagePort.<anonymous> (node:internal/per_context/messageport:23:28)"}
{"level":50,"time":"2024-08-01T02:24:49.462Z","msg":"MainSQL: runCorruptionChecks: not running the check, no writable instance Error: getUnsafeWritableInstance: globalWritableInstance not set!\n at getUnsafeWritableInstance ([REDACTED]/ts/sql/Server.js:600:11)\n at Object.runCorruptionChecks ([REDACTED]/ts/sql/Server.js:4785:10)\n at respond ([REDACTED]/ts/sql/mainWorker.js:40:29)\n at MessagePort.<anonymous> ([REDACTED]/ts/sql/mainWorker.js:115:5)"}
Hi, also happened to me, seems related to cipher change at launch (cipher not recognized while opening database file, so considering database corrupt ?).
{"level":30,"time":"2024-08-01T08:18:27.409Z","msg":"spellcheck: setting languages to: [\"en-US\",\"en\"]"}
{"level":40,"time":"2024-08-01T08:18:27.598Z","msg":"MainSQL: Database log code=26: file is not a database in \"PRAGMA journal_mode = WAL\""}
{"level":30,"time":"2024-08-01T08:18:27.598Z","msg":"MainSQL: migrateDatabase: Migration without cipher change failed"}
{"level":40,"time":"2024-08-01T08:18:27.629Z","msg":"MainSQL: Database log code=26: statement aborts at 2: [PRAGMA user_version] file is not a database"}
{"level":50,"time":"2024-08-01T08:18:27.629Z","msg":"MainSQL: Database startup error: SqliteError: file is not a database\n at Database.pragma ([REDACTED]/node_modules/@signalapp/better-sqlite3/lib/methods/pragma.js:11:31)\n at getUserVersion ([REDACTED]/ts/sql/util.js:132:13)\n at migrateSchemaVersion ([REDACTED]/ts/sql/Server.js:389:54)\n at openAndMigrateDatabase ([REDACTED]/ts/sql/Server.js:420:3)\n at openAndSetUpSQLCipher ([REDACTED]/ts/sql/Server.js:435:14)\n at Object.initialize ([REDACTED]/ts/sql/Server.js:471:16)\n at MessagePort.<anonymous> ([REDACTED]/ts/sql/mainWorker.js:84:35)\n at [nodejs.internal.kHybridDispatch] (node:internal/event_target:820:20)\n at MessagePort.<anonymous> (node:internal/per_context/messageport:23:28)"}
{"level":50,"time":"2024-08-01T08:18:27.630Z","msg":"MainSQL: runCorruptionChecks: not running the check, no writable instance Error: getUnsafeWritableInstance: globalWritableInstance not set!\n at getUnsafeWritableInstance ([REDACTED]/ts/sql/Server.js:600:11)\n at Object.runCorruptionChecks ([REDACTED]/ts/sql/Server.js:4785:10)\n at respond ([REDACTED]/ts/sql/mainWorker.js:40:29)\n at MessagePort.<anonymous> ([REDACTED]/ts/sql/mainWorker.js:115:5)"}
{"level":50,"time":"2024-08-01T08:18:27.630Z","msg":"Failed to get zoom factor {}"}
{"level":30,"time":"2024-08-01T08:18:27.931Z","msg":"got fast theme-setting value system"}
{"level":50,"time":"2024-08-01T08:18:28.342Z","msg":"sql.initialize was unsuccessful; returning early"}
{"level":30,"time":"2024-08-01T08:18:28.343Z","msg":"close event {\"readyForShutdown\":false,\"shouldQuit\":false}"}
{"level":30,"time":"2024-08-01T08:18:28.343Z","msg":"maybeRequestCloseConfirmation: Checking to see if close confirmation is needed"}
{"level":50,"time":"2024-08-01T08:18:30.664Z","msg":"onDatabaseError: Deleting all data"}
{"level":50,"time":"2024-08-01T08:18:30.665Z","msg":"Error occurred in handler for 'sql-channel': {}"}
{"level":40,"time":"2024-08-01T08:18:30.665Z","msg":"MainSQL: removeDB: Removing all database files"}
{"level":30,"time":"2024-08-01T08:18:30.665Z","msg":"main window is ready-to-show"}
{"level":30,"time":"2024-08-01T08:18:30.666Z","msg":"config/remove: Deleting user config from disk"}
{"level":30,"time":"2024-08-01T08:18:30.666Z","msg":"config/remove: Deleted user config from disk"}
{"level":50,"time":"2024-08-01T08:18:30.666Z","msg":"onDatabaseError: Requesting immediate restart after quit"}
{"level":50,"time":"2024-08-01T08:18:30.690Z","msg":"onDatabaseError: Quitting application"}
{"level":30,"time":"2024-08-01T08:18:30.691Z","msg":"main window closed event"}
{"level":30,"time":"2024-08-01T08:18:30.692Z","msg":"quit event {\"hasEventBeenPrevented\":false,\"windowCount\":0,\"mainWindowExists\":false}"}
FATAL ERROR: v8::ToLocalChecked Empty MaybeLocal
----- Native stack trace -----
[1] 8895 IOT instruction signal-desktop
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: snap remove --purge signal-desktop
Happened to my installation of signal-destop (7.17.0) a few days ago. Tried resetting the local data and re linking to phone as proposed by the launcher. Tried reinstalling, same corruption happened three times in a row. Before that, It worked for months without any issue.
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: https://github.com/signalapp/Signal-Desktop/compare/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 sudo snap refresh signal-desktop --channel latest/candidate
to try out the next version and see if that solves the issue.
If you're installing from scratch it'll be sudo snap install signal-desktop --channel latest/candidate
@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: https://github.com/signalapp/Signal-Desktop/issues/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)
# snap install signal-desktop --revision=671
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). Each time you launch Signal-desktop 7.17 or 7.18 (new or existing), you have to delete all the data and resynchronise the phone.
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 6.9.11-100.fc39.x86_64
@jnsgruk Yes I'm having that issue on Ubuntu 24.04 (kern 6.9.9)
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 snap connect signal-desktop:password-manager-service
and re-pair etc., does the issue persist?
@jnsgruk
$ sudo snap connect signal-desktop:password-manager-service
error: snap "signal-desktop" has no plug named "password-manager-service"
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. Tried installing 7.18 (from latest/candidate), snap rev 678, problem persists. With 7.15, snap rev 671, everything works as expected.
I have the same issue in Ubuntu arm64 (ubuntu 24.04, Linux 6.1.0-1021-rockchip - Joshua Riek), on 4 machines.
Rolled back to 7.15.0 (arm64 rev672) because we need Signal Desktop in order to do our work.
sudo snap install signal-desktop --revision=672
sudo snap refresh --hold signal-desktop
I have this issue on a new pop-os machine, using snap.
snap-id: r4LxMVp7zWramXsJQAKdamxy6TAWlaDD
tracking: latest/stable
refresh-date: today at 11:33 EDT
channels:
latest/stable: 7.18.0 2024-08-02 (679) 183MB -
latest/candidate: 7.18.0 2024-08-02 (679) 183MB -
Been happening since we got the new machine about a month ago.
$ cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04.4 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.4 LTS (Jammy Jellyfish)"
I'm trying the revision=671
workaround...and it appears to work. Hopefully this can be resolved before any updates that will break the older client. :-)
Same situation here but also cannot revert. It seems 671 is no longer available, at least for me. I was only able to revert to version 675 and that version did not help resolve the problem. Same errors as everyone above running Fedora as base OS so this seems pretty app specific.
Installed version:
snap-id: r4LxMVp7zWramXsJQAKdamxy6TAWlaDD
tracking: latest/stable
refresh-date: yesterday at 04:35 EDT
channels:
latest/stable: 7.18.0 2024-08-02 (679) 183MB -
latest/candidate: 7.18.0 2024-08-02 (679) 183MB -
latest/beta: ↑
latest/edge: ↑
installed: 7.18.0 (679) 183MB -
Attempt to revert to 671:
$ sudo snap revert signal-desktop --revision=671
error: cannot revert "signal-desktop": cannot find revision 671 for snap "signal-desktop"
Attempt to revert to anything at all, found successful revert (but still broken) with 675:
$ sudo snap revert signal-desktop --revision=675
signal-desktop reverted to 7.17.0
Same issue. Ubuntu 24.04 Kernel 6.9.11 Previous update gave me the error and I reluctantly deleted the data.. It worked for after, then this last update 7.18.0 rev 679 now throws the error on every attempt to run it. Even after purging and re-installing.
level":50,"time":"2024-08-05T00:57:16.461Z","msg":"MainSQL: Database startup error: Error: setupSQLCipher: key '�>8!���˯�I�M�u0��L�W�r'i߉AM�� cOB\u0019\t�Y�Oa�6�P�g\\\u0019���'\u0019�C�U ���w
��Cg�' is not valid\n at openAndSetUpSQLCipher ([REDACTED]/ts/sql/Server.js:438:11)\n at Object.initialize ([REDACTED]/ts/sql/Server.js:476:16)\n at MessagePort.
@torrycrass
Attempt to revert to anything at all, found successful revert (but still broken) with 675:
$ sudo snap revert signal-desktop --revision=675 signal-desktop reverted to 7.17.0
Apparently with snap
, revert
only works for recently installed versions.
You should try the following:
snap remove --purge signal-desktop # remove latest version
snap install signal-desktop --revision=671 # install 7.15
snap list # ensure you installed the 7.15 version
snap refresh --hold=forever signal-desktop # freeze updates for this package
@torrycrass
Attempt to revert to anything at all, found successful revert (but still broken) with 675:
$ sudo snap revert signal-desktop --revision=675 signal-desktop reverted to 7.17.0
Apparently with
snap
,revert
only works for recently installed versions.You should try the following:
snap remove --purge signal-desktop # remove latest version snap install signal-desktop --revision=671 # install 7.15 snap list # ensure you installed the 7.15 version snap refresh --hold=forever signal-desktop # freeze updates for this package
Did work on my Fedora 39, after renaming desktop file:
sudo mv /var/lib/snapd/desktop/applications/signal-desktop_signal-desktop.desktop /var/lib/snapd/desktop/applications/signal-desktop.desktop
However, this is only a workaround and updates are blocked. What's the true cause for this bug?
I'm pretty sure this is an upstream bug, and unfortunately not one I can reproduce so I'm having trouble making progress at the moment.
One option I can try is to add the password-manager-service
plug, and publish a candidate build for you to try. I'll work on that today.
@digital-codes or @digiphaze are you able to test the new revison?
sudo snap remove --purge signal-desktop
sudo snap install signal-desktop --channel latest/candidate
sudo snap connect signal-desktop:password-manager-service
Then try linking/restarting, etc.?
I'm experiencing the same issue, on Ubuntu 23.10, x86-64 CPU. However, I'm using the .deb version. Is there any information I can provide to aid debugging this issue?
After closing the first error (Database Error, same as OP), a second error popup appears:
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. The error crashes the app because the only two buttons in the popup are quit and copy error and quit. I rebooted the laptop to no effect on the bug. Reverting to version 671 removed the error.
$ sudo snap install signal-desktop --revision=671
signal-desktop 7.15.0 from Snapcrafters✪ installed
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. I wonder if a complete purge of software and data is required before testing the deb package after seeing the error from the Snap package.
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:
Linux (Debian-based) Install Instructions
# NOTE: These instructions only work for 64-bit Debian-based
# Linux distributions such as Ubuntu, Mint etc.
# 1. Install our official public software signing key:
wget -O- https://updates.signal.org/desktop/apt/keys.asc | gpg --dearmor > signal-desktop-keyring.gpg
cat signal-desktop-keyring.gpg | sudo tee /usr/share/keyrings/signal-desktop-keyring.gpg > /dev/null
# 2. Add our repository to your list of repositories:
echo 'deb [arch=amd64 signed-by=/usr/share/keyrings/signal-desktop-keyring.gpg] https://updates.signal.org/desktop/apt xenial main' |\
sudo tee /etc/apt/sources.list.d/signal-xenial.list
# 3. Update your package database and install Signal:
sudo apt update && sudo apt install signal-desktop
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: Distributor ID: Ubuntu Description: Ubuntu 24.04 LTS Release: 24.04 Codename: noble
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.
$ signal-dekstop
...
{"level":50,"time":"2024-08-29T16:04:50.049Z","msg":"MainSQL: Database startup error: Error: /snap/core22/current/usr/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by [REDACTED].unpacked/node_modules/@signalapp/better-sqlite3/build/Release/better_sqlite3.node)\n at process.func [as dlopen] (node:electron/js2c/node_init:2:2559)\n at Module._extensions..node (node:internal/modules/cjs/loader:1470:18)\n at Object.func [as .node] (node:electron/js2c/node_init:2:2786)\n at Module.load (node:internal/modules/cjs/loader:1215:32)\n at Module._load (node:internal/modules/cjs/loader:1031:12)\n at c._load (node:electron/js2c/node_init:2:17025)\n at Module.require (node:internal/modules/cjs/loader:1240:19)\n at require (node:internal/modules/helpers:179:18)\n at bindings ([REDACTED]/node_modules/@signalapp/better-sqlite3/node_modules/bindings/bindings.js:112:48)\n at new Database ([REDACTED]/node_modules/@signalapp/better-sqlite3/lib/database.js:48:64)"}
...
$ ldd /snap/signal-desktop/694/opt/Signal/resources/app.asar.unpacked/node_modules/@signalapp/better-sqlite3/build/Release/better_sqlite3.node
/snap/signal-desktop/694/opt/Signal/resources/app.asar.unpacked/node_modules/@signalapp/better-sqlite3/build/Release/better_sqlite3.node: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /snap/signal-desktop/694/opt/Signal/resources/app.asar.unpacked/node_modules/@signalapp/better-sqlite3/build/Release/better_sqlite3.node)
/snap/signal-desktop/694/opt/Signal/resources/app.asar.unpacked/node_modules/@signalapp/better-sqlite3/build/Release/better_sqlite3.node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /snap/signal-desktop/694/opt/Signal/resources/app.asar.unpacked/node_modules/@signalapp/better-sqlite3/build/Release/better_sqlite3.node)
linux-vdso.so.1 (0x00007ffca01c3000)
libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f6a8da00000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f6a8e4ef000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f6a8e4cf000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f6a8d600000)
/lib64/ld-linux-x86-64.so.2 (0x00007f6a8e5e8000)
The problem for me appears to be that the latest bundled version of better-sqlite3 is compiled against GLIBC_2.38 which core22 lacks.
$ signal-dekstop ... {"level":50,"time":"2024-08-29T16:04:50.049Z","msg":"MainSQL: Database startup error: Error: /snap/core22/current/usr/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by [REDACTED].unpacked/node_modules/@signalapp/better-sqlite3/build/Release/better_sqlite3.node)\n at process.func [as dlopen] (node:electron/js2c/node_init:2:2559)\n at Module._extensions..node (node:internal/modules/cjs/loader:1470:18)\n at Object.func [as .node] (node:electron/js2c/node_init:2:2786)\n at Module.load (node:internal/modules/cjs/loader:1215:32)\n at Module._load (node:internal/modules/cjs/loader:1031:12)\n at c._load (node:electron/js2c/node_init:2:17025)\n at Module.require (node:internal/modules/cjs/loader:1240:19)\n at require (node:internal/modules/helpers:179:18)\n at bindings ([REDACTED]/node_modules/@signalapp/better-sqlite3/node_modules/bindings/bindings.js:112:48)\n at new Database ([REDACTED]/node_modules/@signalapp/better-sqlite3/lib/database.js:48:64)"} ... $ ldd /snap/signal-desktop/694/opt/Signal/resources/app.asar.unpacked/node_modules/@signalapp/better-sqlite3/build/Release/better_sqlite3.node /snap/signal-desktop/694/opt/Signal/resources/app.asar.unpacked/node_modules/@signalapp/better-sqlite3/build/Release/better_sqlite3.node: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /snap/signal-desktop/694/opt/Signal/resources/app.asar.unpacked/node_modules/@signalapp/better-sqlite3/build/Release/better_sqlite3.node) /snap/signal-desktop/694/opt/Signal/resources/app.asar.unpacked/node_modules/@signalapp/better-sqlite3/build/Release/better_sqlite3.node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /snap/signal-desktop/694/opt/Signal/resources/app.asar.unpacked/node_modules/@signalapp/better-sqlite3/build/Release/better_sqlite3.node) linux-vdso.so.1 (0x00007ffca01c3000) libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f6a8da00000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f6a8e4ef000) libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f6a8e4cf000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f6a8d600000) /lib64/ld-linux-x86-64.so.2 (0x00007f6a8e5e8000)
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. https://github.com/signalapp/Signal-Desktop/issues/6996#issuecomment-2318323039
@jnsgruk
I've kicked off our update/release process - will comment here when it's ready to test.
No joy.
$ ldd /snap/signal-desktop/696/opt/Signal/resources/app.asar.unpacked/node_modules/@signalapp/better-sqlite3/build/Release/better_sqlite3.node
/snap/signal-desktop/696/opt/Signal/resources/app.asar.unpacked/node_modules/@signalapp/better-sqlite3/build/Release/better_sqlite3.node: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /snap/signal-desktop/696/opt/Signal/resources/app.asar.unpacked/node_modules/@signalapp/better-sqlite3/build/Release/better_sqlite3.node)
/snap/signal-desktop/696/opt/Signal/resources/app.asar.unpacked/node_modules/@signalapp/better-sqlite3/build/Release/better_sqlite3.node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /snap/signal-desktop/696/opt/Signal/resources/app.asar.unpacked/node_modules/@signalapp/better-sqlite3/build/Release/better_sqlite3.node)
linux-vdso.so.1 (0x00007ffcc1ce3000)
libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f9254800000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f9254b19000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f92552c9000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f9254400000)
/lib64/ld-linux-x86-64.so.2 (0x00007f92552fb000)
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.
No joy.
$ ldd /snap/signal-desktop/696/opt/Signal/resources/app.asar.unpacked/node_modules/@signalapp/better-sqlite3/build/Release/better_sqlite3.node /snap/signal-desktop/696/opt/Signal/resources/app.asar.unpacked/node_modules/@signalapp/better-sqlite3/build/Release/better_sqlite3.node: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /snap/signal-desktop/696/opt/Signal/resources/app.asar.unpacked/node_modules/@signalapp/better-sqlite3/build/Release/better_sqlite3.node) /snap/signal-desktop/696/opt/Signal/resources/app.asar.unpacked/node_modules/@signalapp/better-sqlite3/build/Release/better_sqlite3.node: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /snap/signal-desktop/696/opt/Signal/resources/app.asar.unpacked/node_modules/@signalapp/better-sqlite3/build/Release/better_sqlite3.node) linux-vdso.so.1 (0x00007ffcc1ce3000) libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f9254800000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f9254b19000) libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f92552c9000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f9254400000) /lib64/ld-linux-x86-64.so.2 (0x00007f92552fb000)
This feels like a separate issue to me, even if related. Can you file an issue to track that separately? Thank you!
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