| Summary: | kmymoney crashes with sqlcipher 4.7.0+ | ||
|---|---|---|---|
| Product: | [Applications] kmymoney | Reporter: | Boyuan Yang <073plan> |
| Component: | database | Assignee: | KMyMoney Devel Mailing List <kmymoney-devel> |
| Status: | REPORTED --- | ||
| Severity: | crash | CC: | 073plan, kernefahey, marillat, s.hohrein |
| Priority: | NOR | ||
| Version First Reported In: | 5.2.1 | ||
| Target Milestone: | --- | ||
| Platform: | Debian unstable | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Boyuan Yang
2025-11-22 19:24:50 UTC
Are you sure about these version numbers? I see 4.11.0 as the most recent release, from October. (In reply to Jack from comment #1) > Are you sure about these version numbers? I see 4.11.0 as the most recent > release, from October. I am not sure about the exact version. I can bisect them if you find that necessary. Maybe the issue would only occur after this commit: https://github.com/sqlcipher/sqlcipher/commit/291dc9bb45bd608e9c3a6ec046619f9abb6b05f0 This commit explicitly mentions the guarding against "misuse" of the APIs, which looks pretty likely to be the cause of the current cause. This commit exists in sqlcipher 5.7.0 and all later versions. I am not questioning when the issue was created - just the released version numbers. The most recent version I can find is 4.11, not 5.11, so I'm wondering if you really mean 4.7.0 and later, not 5.7.0. (In reply to Jack from comment #4) > I am not questioning when the issue was created - just the released version > numbers. The most recent version I can find is 4.11, not 5.11, so I'm > wondering if you really mean 4.7.0 and later, not 5.7.0. Sure. I just found there are version typos all around above in my comments. When I said 5.7.0, I actually meant sqlcipher 4.7.0. Similarly it should be sqlcipher 4.11.0 not 5.11.0. Sorry for the confusion. A related discussion has been opened on sqlcipher's issue list: https://github.com/sqlcipher/sqlcipher/issues/578 *** Bug 512525 has been marked as a duplicate of this bug. *** *** Bug 512599 has been marked as a duplicate of this bug. *** |