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

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

Open
ell1e opened this issue Feb 17, 2025 · 4 comments

Comments

@ell1e
Copy link

ell1e commented Feb 17, 2025

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.

  • Operating System (Linux/Mac/Windows/iOS/Android): Linux
  • Delta Chat Version: Delta Chat Desktop 1.52.1 from flathub, Delta Chat Core v1.155.1
  • Expected behavior: The error message gives either the exact system errno on Linux, or the SQL error message in full, or at least logs this information to the log file.
  • Actual behavior: Neither the error message nor the log file seem to include the detailed underlying error.
  • Steps to reproduce the problem: 1. Not sure how exactly users commonly run into this error
  • Screenshots:
  • Logs:
@Simon-Laux Simon-Laux transferred this issue from deltachat/deltachat-desktop Feb 17, 2025
@link2xt
Copy link
Collaborator

link2xt commented Feb 17, 2025

Another similar bug #5933, also flathub

@ell1e
Copy link
Author

ell1e commented Feb 17, 2025

I could be wrong but I think the person mentioned using Linux Mint.

@ell1e
Copy link
Author

ell1e commented Feb 17, 2025

Perhaps a more detailed error message, e.g. one that shows the errno, would help with figuring out what the underlying problem is?

@link2xt
Copy link
Collaborator

link2xt commented Feb 18, 2025

Possibly fixed by flathub/chat.delta.desktop#158

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

No branches or pull requests

2 participants