Bug 460554

Summary:	Crashed while working with the app
Product:	[Applications] kmymoney	Reporter:	Dawid Wróbel <me>
Component:	general	Assignee:	KMyMoney Devel Mailing List <kmymoney-devel>
Status:	RESOLVED WORKSFORME
Severity:	crash
Priority:	NOR
Version First Reported In:	git (master)
Target Milestone:	---
Platform:	Other
OS:	Other
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Dawid Wróbel 2022-10-16 20:40:25 UTC

SUMMARY
I had a ledger open in the background while I was working with another app in the foreground. I switched back to kmymoney and the app crashed — I believe I also attempted to move its window, although not sure if this could be related

From the terminal output:

qt.core.qabstractitemmodel.checkindex: Index QModelIndex(-1,-1,0x0,QObject(0x0)) is not valid (expected valid)
ASSERT: "checkIndex(index, CheckIndexOption::IndexIsValid)" in file /Users/cromo/Documents/Sourcecode/vcpkg/buildtrees/qt5-base/src/5.15.6-98c6389ac2.clean/src/corelib/itemmodels/qconcatenatetablesproxymodel.cpp, line 192

The error message is quite vague, I'm reporting it nonetheless to see if I can reproduce it.

SOFTWARE/OS VERSIONS
macOS: 12.6
KDE Frameworks Version: 5.98
Qt Version: 5.15.6

ADDITIONAL INFORMATION

Comment 1 Thomas Baumgart 2022-10-17 18:23:05 UTC

I doubt that simply switching back to KMyMoney causes this crash. As you mention, doing something else that influences the course of action could well be the reason.

Comment 2 Thomas Baumgart 2024-07-11 16:03:00 UTC

Can you still reproduce this problem? I am asking, because I fixed a problem lately that showed the same symptom (invalid QModelIndex) in connection with the investment view.

Comment 3 Dawid Wróbel 2024-07-12 15:48:52 UTC

I haven't touched master in a while, working with stable for a while (have a bunch of overdue finances to work through).

Comment 4 Bug Janitor Service 2024-07-27 03:46:08 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 5 Bug Janitor Service 2024-08-11 03:46:39 UTC

🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.