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 startup error version >= 7.24.1 #7025

Closed
2 tasks done
rkarimov opened this issue Sep 25, 2024 · 4 comments
Closed
2 tasks done

Database startup error version >= 7.24.1 #7025

rkarimov opened this issue Sep 25, 2024 · 4 comments

Comments

@rkarimov
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

The signal for the Desktop stopped working and is prompting with "Database startup error" after my computer shut down overnight due to power issues.

Steps to reproduce

  1. Launch signal desktop app (version 7.24.1) from Macbook Pro
  2. Error is shown, click "
  3. Restarted my macbook
  4. Upgraded to latest App Version: 7.25.0 (downloaded for signal's website and replaced existing package)
  5. Restarted device again
  6. still getting database error

Database error:
"Database startup error:

SqliteError: database disk image is malformed
at getMessagesBySentAt ([REDACTED]/ts/sql/Server.js:3308:34)
at MessagePort. ([REDACTED]/ts/sql/mainWorker.js:123:22)
at [nodejs.internal.kHybridDispatch] (node:internal/event_target:820:20)
at MessagePort. (node:internal/per_context/messageport:23:28)

App Version: 7.25.0
OS: darwin"

Expected result

Signal desktop is launched w/o interruption

Actual result

Signal launches into a database error

Screenshots

No response

Signal version

7.24.1

Operating system

MacOS 12.7.6

Version of Signal on your phone

No response

Link to debug log

https://debuglogs.org/desktop/7.25.0/1aa497cab1f25496ade7d33712c7f47cc903ddee00750a1fe9759a5cd3c282dc.gz

@rkarimov rkarimov changed the title Getting Database startup error after unexpected interruption of powersource Database startup error version >= 7.24.1 Sep 25, 2024
@indutny-signal
Copy link
Contributor

I'm sorry, but it does look like your database got corrupted in the process. If the error persists - the only way forward might be erasing the data and starting over. 😭

@toppk
Copy link

toppk commented Sep 26, 2024

I'm sorry, but it does look like your database got corrupted in the process. If the error persists - the only way forward might be erasing the data and starting over. 😭

what is "the process"? what does "starting over mean?" do you lose everything? What if you're logged in elsewhere?

@scottnonnenberg-signal
Copy link
Contributor

@toppk Yes, you'll need to unlink that Desktop from your mobile device. If you have a backup of your desktop data, you can copy that into place while Signal Desktop is not running, then start up and re-link it to your mobile device. Otherwise, yes, you will need to start over from scratch, like you installed Signal Desktop afresh.

@toppk
Copy link

toppk commented Sep 27, 2024

@toppk Yes, you'll need to unlink that Desktop from your mobile device. If you have a backup of your desktop data, you can copy that into place while Signal Desktop is not running, then start up and re-link it to your mobile device. Otherwise, yes, you will need to start over from scratch, like you installed Signal Desktop afresh.

As I mentioned in another issue I have recovered, and now I'm trying to figure out how to get to the latest version of signal. It seems like the best way forward isn't trying to make permanent the legacy way of unencrypted key in config.json, but figure out how to proceed with a conversion to encryptedKey that actually works. Is there any undestanding of why the key upgrade failed for me (and many others?) I cannot find that info. fwiw I think this is the PR that introduced the key upgrade.

#6849

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

4 participants