-
-
Notifications
You must be signed in to change notification settings - Fork 99
The error "IMEX failed to complete: could not export database: [...] Error code 1: SQL error or missing database" should list the actual errno or the actual SQL error message in full #6551
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
Comments
Another similar bug #5933, also flathub |
I could be wrong but I think the person mentioned using Linux Mint. |
Perhaps a more detailed error message, e.g. one that shows the errno, would help with figuring out what the underlying problem is? |
Possibly fixed by flathub/chat.delta.desktop#158 |
I don't think we can do anything here. The error comes from here: Lines 796 to 798 in 483f4ea
and "disk I/O error: Error code 1: SQL error or missing database" is what rusqlite gives us. Maybe it could be fixed in rusqlite, maybe in SQLite, I don't know. Since there is nothing actionable here, I think we can close this issue? |
Thanks so much for looking into this. |
I've seen a user, who apparently tried to export a backup in delta chat desktop, come to me with the following error:
IMEX failed to complete: could not export database: failed to export attached backup data base: disk I/O error: Error code 1: SQL error or missing database
In the log file, there doesn't seem to be anything more specific either than this vague error message.If I'm reading this error correctly, it might include 1. any errno like EIO with an actual disk error indicating a hardware problem, 2. or any errno like EPERM indicating a permission problem, 3. or any errno like ENOENT indicating the database was moved around or the path somehow assembled wrongly indicating an install problem, 4. or any SQL error indicating any sort of schema problem with the underlying database.
This seems like too many potential error sources mapped to a single error message. I suggest that the error message should include either the actual system errno on Linux, or the actual SQL error in case of a schema issue.
The text was updated successfully, but these errors were encountered: