https://bugs.kde.org/show_bug.cgi?id=398410
NSLW <lukasz.wojnilow...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |lukasz.wojnilow...@gmail.co
| |m
--- Comment #6 from NSLW <lukasz.wojnilow...@gmail.com> ---
MySQL storage does not crash for me with a simple test case.
Please do these roughly described steps and report if they work for you:
1) create new basic (one account, one transaction, one payee, one category) XML
storage
2) save it as SQL (MySQL) storage
3) close KMyMoney
4) open KMyMoney (MySQL storage should be loaded automatically)
5) add one more transaction and hit save button
Following snippet from your dump looks suspicious:
"Title: kmymoney crashed with SIGSEGV in __GI___pthread_mutex_lock()
UnreportableReason: This package does not seem to be installed correctly
UpgradeStatus: Upgraded to bionic on 2018-05-26 (119 days ago)"
I suspect that something may be not right either with your system (maybe you
could provide us with some info) or with your specific payload to MySQL (you
should follow the steps from the top)
(In reply to Eleazar from comment #3)
> Was the logic changed in the way interaction with a DB is done in KMM5?
>
> In KMM 4.8 any entry made it sends it straight to the DB where as in KMM5 it
> seems to be stored locally until I push the save button.
Yes it has been changed. SQL now works just as XML. The approach from KMM 4.8
was slow, required duplicate code and in my opinion offered no benefits.
> I am wondering if it creates a temporary file and the file is deleted by the
> system and KMM is not aware of it which is why it crashes when I hit the
> save button.
AFAIK MySQL isn't file based database as it is in case of SQLite. MySQL and SQL
roughly follow the same code paths and in case of SQLite no temporary file is
created to save database. A database is open and stays open till its close or
KMM close.
--
You are receiving this mail because:
You are the assignee for the bug.
