Bug 290069 - KMymoney crashed after deleting category and saving
Summary: KMymoney crashed after deleting category and saving
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: kmymoney
Classification: Applications
Component: general (show other bugs)
Version: 4.5.3
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-29 08:38 UTC by Alexander Krivács Schrøder
Modified: 2012-02-19 16:56 UTC (History)
0 users

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 Alexander Krivács Schrøder 2011-12-29 08:38:20 UTC
Application: kmymoney (4.5.3)
KDE Platform Version: 4.7.3 (4.7.3)
Qt Version: 4.7.4
Operating System: Linux 3.0.0-14-generic x86_64
Distribution: Ubuntu 11.10

-- Information about the crash:
- What I was doing when the application crashed:

I had just deleted a category (transferring its entries to another category) and hit save. Then the application crashed during or right after save (hard to tell).

-- Backtrace:
Application: KMyMoney (kmymoney), signal: Aborted
[KCrash Handler]
#6  0x00007fb825c203a5 in raise () from /lib/x86_64-linux-gnu/libc.so.6
#7  0x00007fb825c23b0b in abort () from /lib/x86_64-linux-gnu/libc.so.6
#8  0x00007fb8264ded7d in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#9  0x00007fb8264dcf26 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#10 0x00007fb8264dcf53 in std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#11 0x00007fb8264dd04e in __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#12 0x0000000000455599 in main (argc=1, argv=<optimized out>) at /build/buildd/kmymoney-4.5.3/kmymoney/main.cpp:266

Possible duplicates by query: bug 290055, bug 290054, bug 290053, bug 290016, bug 290015.

Reported using DrKonqi
Comment 1 Thomas Baumgart 2011-12-29 09:12:09 UTC
We made significant changes in that area which should resolve this issue. Please try to upgrade to 4.6.1 and report here if the problem persists or not. Thanks in advance.