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

Attempt to write to a read-only database #7096

Open
2 tasks done
seba7236 opened this issue Nov 21, 2024 · 3 comments
Open
2 tasks done

Attempt to write to a read-only database #7096

seba7236 opened this issue Nov 21, 2024 · 3 comments

Comments

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

Signal started automatically on my system, like usual. Except this time, I got this error. I did not do anything out of the ordinary.

Steps to reproduce

  1. Have Signal as a startup task on Windows
  2. Wait for the error to occur (Very random when it happens)

Expected result

The app should start normally.

Actual result

Signal doesnt open, and crashes with this error message.

Unhandled Promise Rejection

SqliteError: attempt to write a readonly database
at createOrUpdate ([REDACTED]\ts\sql\util.js:182:5)
at createOrUpdateItem ([REDACTED]\ts\sql\Server.js:710:41)
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.33.0
OS: win32

Screenshots

No response

Signal version

7.34.0

Operating system

Windows 10

Version of Signal on your phone

No response

Link to debug log

https://debuglogs.org/desktop/7.34.0/d7a3db505b7b4f255910c2ab2da8707a508acc5038156e31b89808ad950b982c.gz

@ayumi-signal
Copy link
Contributor

@seba7236 Hey there, sorry this is happening! Is it possible there was an unclean shutdown of the app or system? Sometimes this leaves the database in a locked state and can result in this error. It might be hard for us to do much about it, besides show an error dialog with a suggestion to restart.

@seba7236
Copy link
Author

The last shutdown was normal, from within Windows. No complaints from Signal when I shut it down. Closing the app and opening it again fixed it. I've never experienced it the past year, its only started happening recently, 2 times so far this month. I haven't changed anything about my setup that could explain it.

@ayumi-signal
Copy link
Contributor

Thanks for the additional info. We do develop on Windows and will check for similar errors.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants