| Summary: | Getting "unable to fetch row" error when making any change whatsover to a large document | ||
|---|---|---|---|
| Product: | [Applications] skrooge | Reporter: | Johannes Goller <jogojapan> |
| Component: | general | Assignee: | Stephane MANKOWSKI <stephane> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | 2.30.0 | ||
| Target Milestone: | 25.1.0 | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Johannes Goller
2024-10-02 20:40:46 UTC
I now created a new document and imported the old one completely. In the new one, I can now add and make changes as usual. So that is fine as a workaround. Interestingly, the size of my old document was about 11 MB, the size of the new one is 56 MB. Hi, Could you tell me what is the sqlcipher version of your system ? You can have this kind of issue when the document is created with sqlcipher 3 and the new sqlcipher 4 is installed. For the size of the document, this could be due to a huge history. If you clean the history from the "History" doc, you should reduce the size of the document. 🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone! Indeed the sqlcipher version is 4.5.2, but that must have been the case for quite a while before I started getting that problem. It's been that version in Fedora 39 and Fedora 40, so I must have been using it for more than a year. (On a separate note, the document size has meanwhile decreased back to 11MB. I didn't do anything, but perhaps it removed the history automatically?) Hi, I have in skrooge all my transaction since 2004 without issue. I think the issue is due to sqlcipher 4. Could you try this from a console ? - export SKGTRACE=1 - skrooge Now you should have a new "Debug" item in the left list. Open it and launch the following commands ? PRAGMA cipher_page_size pragma cipher_integrity_check PRAGMA cipher_provider PRAGMA cipher_version PRAGMA cipher_compatibility Could you put here the result of each of them ? You can have some details about those command here: https://www.zetetic.net/sqlcipher/sqlcipher-api/#cipher_settings I can also to propose you the following workaround: - Open skrooge - Export you document in SQLCipher format (sqlcipher_export() will be used an clean your document). - Create a new document - Import the exported SQLCipher document You should have exactly the same content but without the "database disk image is malformed" issue. 🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone! 🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME. |