Bug 413535

Summary:	Error thrown by mymoneyseqaccessmgr.cpp after removing payees from database and saving
Product:	[Applications] kmymoney	Reporter:	Kevin <metalbird42>
Component:	file	Assignee:	KMyMoney Devel Mailing List <kmymoney-devel>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	metalbird42
Priority:	NOR
Version:	5.0.0
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:

Description Kevin 2019-10-28 03:29:49 UTC

SUMMARY
Deleted several unused payee names and had merged a few others as well. Saved and closed file. Upon attempting to reopen later, received Error dialog stating "Unknown account id 'A000042' in file /build/kmymoney-8Tb1zm/kmymoney-5.0.1/kmymoney/mymoney/storage/mymoneyseqaccessmgr.cpp line 206". Closes kmymoney after acknowledging error.

STEPS TO REPRODUCE
1. Deleted/merged multiple payees
2. Saved file
3. Upon reopening, GUI crashed

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Linux: Kubuntu 18.04
KDE Plasma Version: 5.12.9
KDE Frameworks Version: 5.44.0
Qt Version: 5.9.5

ADDITIONAL INFORMATION
Logged out, logged back in, rebooted, then reinstalled kmymoney before determining error only occurred in file in which I had modified payees.

Comment 1 Thomas Baumgart 2019-10-28 06:25:05 UTC

In case you still have a copy of the file containing the payees make sure to keep it for further investigation. Using a newer version (we are at 5.0.7 in the meantime) might not solve the problem as it is related to your data.

Comment 2 Kevin 2019-10-28 23:15:15 UTC

I fixed the data file manually by opening the file with Kate to view the xml. Located the 'A000042' entry, which was in the scheduled transactions section, second split part. Based on the transaction I knew which account I needed it to actually reference. So I located the correct account id (A000258) in the file and replaced the 'A000042' with that id. Saved and reopened with Kmymoney with no further issues. How that account id got changed would be the bug.

Comment 3 Thomas Baumgart 2020-01-11 17:35:02 UTC

I agree, but it is kind of hard to do that now. So I close the bug.