Bug 431492

Summary: kmymoney crash
Product: [Applications] kmymoney Reporter: Andriy Gapon <avg>
Component: generalAssignee: KMyMoney Devel Mailing List <kmymoney-devel>
Status: RESOLVED WORKSFORME    
Severity: crash Keywords: drkonqi
Priority: NOR    
Version: 5.0.3   
Target Milestone: ---   
Platform: unspecified   
OS: FreeBSD   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Andriy Gapon 2021-01-12 12:45:07 UTC 
Application: kmymoney (5.0.3)
 (Compiled from sources)
Qt Version: 5.12.2
Frameworks Version: 5.59.0
Operating System: FreeBSD 12.0-CURRENT amd64
Distribution (Platform): FreeBSD Ports

-- Information about the crash:
All of a sudden started happening when trying to enter a particular scheduled transaction.
Worked without any issues before.

The crash can be reproduced every time.

-- Backtrace:
Application: KMyMoney (kmymoney), signal: Segmentation fault
[KCrash Handler]
#8  0x0000000805384a9f in MyMoneySplit::accountId() const () at /usr/local/lib/libkmm_mymoney.so.5
#9  0x00000000005e2b03 in  ()
#10 0x0000000000515f34 in  ()
#11 0x0000000000510992 in  ()
#12 0x000000080a6b5eff in QMetaObject::activate(QObject*, int, int, void**) () at /usr/local/lib/qt5/libQt5Core.so.5
#13 0x00000008081703a9 in QAction::activate(QAction::ActionEvent) () at /usr/local/lib/qt5/libQt5Widgets.so.5
#14 0x000000080a6af021 in QObject::event(QEvent*) () at /usr/local/lib/qt5/libQt5Core.so.5
#15 0x0000000808179660 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/local/lib/qt5/libQt5Widgets.so.5
#16 0x000000080817ac26 in QApplication::notify(QObject*, QEvent*) () at /usr/local/lib/qt5/libQt5Widgets.so.5
#17 0x000000080a682d80 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/local/lib/qt5/libQt5Core.so.5
#18 0x000000080a683dd2 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/local/lib/qt5/libQt5Core.so.5
#19 0x000000080a6dc3e8 in  () at /usr/local/lib/qt5/libQt5Core.so.5
#20 0x00000008115d9796 in g_main_context_dispatch () at /usr/local/lib/libglib-2.0.so.0
#21 0x00000008115d9b35 in  () at /usr/local/lib/libglib-2.0.so.0
#22 0x00000008115d9be4 in g_main_context_iteration () at /usr/local/lib/libglib-2.0.so.0
#23 0x000000080a6dbdeb in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/local/lib/qt5/libQt5Core.so.5
#24 0x000000080a67e76e in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/local/lib/qt5/libQt5Core.so.5
#25 0x000000080a68343e in QCoreApplication::exec() () at /usr/local/lib/qt5/libQt5Core.so.5
#26 0x0000000000458170 in  ()
#27 0x00000000004560a8 in  ()
#28 0x000000000045397f in  ()
#29 0x0000000800a09000 in  ()
#30 0x0000000000000000 in  ()
[Inferior 1 (process 64714) detached]

Reported using DrKonqi
Comment 1 Jack 2021-01-12 18:41:37 UTC 
Can you try a more recent version?  5.1.1 was released last month, and 5.0.3 is almost a year old.

Especially if the problem still happens, does a consistency check show any problem?  If you save as an anonymous file, and the problem still occurs, you can attach the anonymous file to the bug.
Comment 2 Bug Janitor Service 2021-01-27 04:33:26 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 2021-02-11 04:33:23 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!