Bug 479836

Summary:	crash closing an old account .
Product:	[Applications] kmymoney	Reporter:	rzeta <erre.zeta>
Component:	general	Assignee:	KMyMoney Devel Mailing List <kmymoney-devel>
Status:	RESOLVED WORKSFORME
Severity:	crash	Keywords:	drkonqi
Priority:	NOR
Version First Reported In:	5.1.3
Target Milestone:	---
Platform:	Mint (Debian based)
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description rzeta 2024-01-15 11:12:39 UTC

Application: kmymoney (5.1.3)

Qt Version: 5.15.8
Frameworks Version: 5.103.0
Operating System: Linux 6.1.0-10-amd64 x86_64
Windowing System: X11
Distribution: Debian GNU/Linux 12 (bookworm)
DrKonqi: 5.27.5 [KCrashBackend]

-- Information about the crash:
The account is zero balance, reconciled, with no movements for many years.

The crash can be reproduced every time.

-- Backtrace:
Application: KMyMoney (kmymoney), signal: Segmentation fault

[KCrash Handler]
#4  0x00007f46ece02a09 in InstitutionsModel::slotObjectModified(eMyMoney::File::Object, QString const&) () from /lib/x86_64-linux-gnu/libkmm_models.so.5
#5  0x00007f46e80e8f4f in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00007f46e9f18576 in MyMoneyFile::objectModified(eMyMoney::File::Object, QString const&) () from /lib/x86_64-linux-gnu/libkmm_mymoney.so.5
#7  0x00007f46e9f28763 in MyMoneyFile::commitTransaction() () from /lib/x86_64-linux-gnu/libkmm_mymoney.so.5
#8  0x00007f46e9f2887d in MyMoneyFileTransaction::commit() () from /lib/x86_64-linux-gnu/libkmm_mymoney.so.5
#9  0x000055ce6816ae8c in ?? ()
#10 0x00007f46e80e8f4f in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x00007f46e8d5c782 in QAction::triggered(bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#12 0x00007f46e8d5f3ab in QAction::activate(QAction::ActionEvent) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x00007f46e8ee3b62 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x00007f46e8eeb994 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x00007f46e8da4db8 in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#16 0x00007f46e8d62fae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#17 0x00007f46e8d6b552 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#18 0x00007f46e80b16f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x00007f46e8d6965e in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool, bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#20 0x00007f46e8dbe025 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#21 0x00007f46e8dc0f60 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#22 0x00007f46e8d62fae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#23 0x00007f46e80b16f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x00007f46e853d3ed in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#25 0x00007f46e8511cac in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#26 0x00007f46e1572eca in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#27 0x00007f46e5e6f7a9 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#28 0x00007f46e5e6fa38 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#29 0x00007f46e5e6facc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#30 0x00007f46e8109836 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#31 0x00007f46e80b017b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#32 0x00007f46e80b82d6 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#33 0x000055ce6813ab26 in ?? ()
#34 0x00007f46e78461ca in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#35 0x00007f46e7846285 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
#36 0x000055ce6813b1c1 in ?? ()
[Inferior 1 (process 10275) detached]

Reported using DrKonqi

Comment 1 Thomas Baumgart 2024-01-15 13:04:15 UTC

This is a bit weird and should not happen. I noticed the crash happens in the institution area of the application. Please try the following and report back here:
- make a backup of your file (always a good idea)
- open the account in the accound editor (Account/Edit account..)
- select the Institution tab
- Click on the drop down combobox at the top
- Select "(No institution)"
- Press OK
Hopefully, this does not crash. If it does, we're done here and need to follow a different path. If it did not crash, please try to close the account now.

Comment 2 rzeta 2024-01-15 15:40:27 UTC

(In reply to Thomas Baumgart from comment #1)
> This is a bit weird and should not happen. I noticed the crash happens in
> the institution area of the application. Please try the following and report
> back here:
> - make a backup of your file (always a good idea)
> - open the account in the accound editor (Account/Edit account..)
> - select the Institution tab
> - Click on the drop down combobox at the top
> - Select "(No institution)"
> - Press OK
> Hopefully, this does not crash. If it does, we're done here and need to
> follow a different path. If it did not crash, please try to close the
> account now.

Hi Thomas,
All perfect. It worked.
I got the message below and the account was closed without crashing the application.

> You have closed this account. It remains in the system because there are transactions that still refer to that account, but it is not shown in the views. You can make it visible again from the View menu and by selecting Show all accounts or unchecking the Do not show closed accounts setting.

Is there a system or addon that allows all movements from one date to another to be archived?
Now I have 12 years of transactions inside database.

Thank you very much
Roberto

Comment 3 Thomas Baumgart 2024-01-15 19:35:18 UTC

Glad that it worked out for you. No, there is no feature to archive data. BTW, I have 20+ years of transactions in my DB.

p.s. In case you answer by email, please don't include anything of the original. Doing otherwise makes processing the bugs on the web more complicated than necessary. Thx.