Bug 326518 - KMyMoney crashed after reporting an error: "Cannot add split that does not contain an account reference"
Summary: KMyMoney crashed after reporting an error: "Cannot add split that does not co...
Status: RESOLVED WORKSFORME
Alias: None
Product: kmymoney
Classification: Applications
Component: general (show other bugs)
Version: 4.6.3
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords: drkonqi, triaged
Depends on:
Blocks:
 
Reported: 2013-10-23 17:01 UTC by Daniel Hahler
Modified: 2018-10-27 03:52 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Hahler 2013-10-23 17:01:16 UTC
Application: kmymoney (4.6.3)
KDE Platform Version: 4.11.2
Qt Version: 4.8.4
Operating System: Linux 3.11.0-12-generic x86_64
Distribution: Ubuntu 13.10

-- Information about the crash:
I have edit a loan account, trying to remove it (which was greyed out).

Then KMyMoney reported an error, and crashed afterwards:

    Cannot add split that does not contain an account reference in Datei /build/buildd/kmymoney-4.6.3/kmymoney/mymoney/mymoneytransaction.cpp, Zeile 122

-- Backtrace:
Application: KMyMoney (kmymoney), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f8ded75c7c0 (LWP 16929))]

Thread 3 (Thread 0x7f8dd3f52700 (LWP 16938)):
#0  0x00007f8de8074f7d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007f8de36bb694 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f8de36bbafa in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f8ddb1fd9d6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#4  0x00007f8de36e00e5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f8de3d84f6e in start_thread (arg=0x7f8dd3f52700) at pthread_create.c:311
#6  0x00007f8de80819cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 2 (Thread 0x7f8dd3751700 (LWP 16939)):
#0  0x00007f8de8074f7d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007f8de36bb694 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f8de36bb79c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f8de36bb7e9 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f8de36e00e5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f8de3d84f6e in start_thread (arg=0x7f8dd3751700) at pthread_create.c:311
#6  0x00007f8de80819cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 1 (Thread 0x7f8ded75c7c0 (LWP 16929)):
[KCrash Handler]
#5  0x00007f8de7fbdf77 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#6  0x00007f8de7fc15e8 in __GI_abort () at abort.c:90
#7  0x00007f8de88c96e5 in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#8  0x00007f8de88c7856 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#9  0x00007f8de88c7883 in std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#10 0x00007f8de88c7aae in __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#11 0x0000000000456027 in main (argc=1, argv=0x7fff308918b8) at /build/buildd/kmymoney-4.6.3/kmymoney/main.cpp:185

Possible duplicates by query: bug 324432, bug 324013, bug 323830, bug 323692, bug 323586.

Reported using DrKonqi
Comment 1 Cristian Oneț 2014-07-31 09:33:05 UTC
Could you describe in a bit more detail the steps you took while editing the loan?
Comment 2 Andrew Crouthamel 2018-09-25 03:32:05 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 set the bug status 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 Andrew Crouthamel 2018-10-27 03:52:18 UTC
Dear Bug Submitter,

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!