Bug 468075

Summary:	Closing Investment Accounts causes program crash
Product:	[Applications] kmymoney	Reporter:	Mark Medoff <markm10538>
Component:	general	Assignee:	KMyMoney Devel Mailing List <kmymoney-devel>
Status:	RESOLVED WORKSFORME
Severity:	crash
Priority:	NOR
Version:	5.1.3
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Mark Medoff 2023-04-02 14:21:38 UTC

SUMMARY
Closing Investment account causes program crash
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
I have removed all securities from an investment account and sub-accounts and added the same securities to a new investment account, with similar sub-accounts. I used the entry of a symbol for security without a name to ensure same security was added to the new sub-accounts. I tried to close the various sub-accounts and all attempts to any of the sub-accounts result in program crashing. I get a segmentation fault.

I can successfully re-open and re-close non-investment accounts (ie: bank accounts)


STEPS TO REPRODUCE
1.  Go to Security account or investment sub-account
2.  Make sure there are no balances or schedules for items
3.  Close account

OBSERVED RESULT
Program crashes

EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version:  5.103.0
Qt Version: 5.15.8 (built against 5.15.8)

ADDITIONAL INFORMATION
System:
  Kernel: 5.15.0-69-generic x86_64 bits: 64 compiler: gcc v: 11.3.0 Desktop: Cinnamon 5.6.8

Comment 1 Jack 2023-04-14 22:07:03 UTC

Mark,

Does this still happen, and have you been able to get a backtrace?  Can you also test by creating (possibly in a new data file, so you can post it to the bug if the crash still happens) a new investment account, a new equity, and a new security, and then trying to close the security subaccount.

Thanks.

Jack

Comment 2 Bug Janitor Service 2023-04-29 03:46:16 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 3 Bug Janitor Service 2023-05-14 03:46:01 UTC

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!