https://bugs.kde.org/show_bug.cgi?id=512307
--- Comment #13 from [email protected] --- (In reply to Jack from comment #12) > Comments 9 and 10 show why KMyMoney is actually calling sqlcipher even if > it's not going to be used, but that doesn't answer the question of why it is > crashing. I would open a siduction bug in addition to this one, not instead > of. > Also, the commit Thomas linked to shows a call sqlite3_key, but the > backtrace posted in above shows a call to sqlite3_key_v2 - I have no idea if > this is a problem or just a deeper call. > I also don't know if we have asked you to test if sqlcipher itself works for > you. If so, I'm tending towards some strange linking/packaging issue, as > Thomas suggested. If it does not work, then that needs to get fixed by the > siduction team. I have filed this to siduction team and already received some hints regarding the apt related sources. I have cleaned the sources directory, removed unnecessary sources and also checked it maches new debian style 822 type repo format. Still, re-installation did not fix anything, same results. What I have found: apparently the kmymoney version in deb was not compiled to include encripted sql data bases, which makes it crash. Only the flak-package installation was compiled to include it and that is why it works. So you probably cannot do anything about this issue as debian has decided to release kmymoney package without encription included. It seems I should compile it myself to include encription and also convert it to a deb package to blend into the system package management. -- You are receiving this mail because: You are watching all bug changes.
