Application: kmymoney (4.5.0) KDE Platform Version: 4.5.1 (KDE 4.5.1) Qt Version: 4.7.0 Operating System: Linux 2.6.35-27-generic x86_64 Distribution: Ubuntu 10.10 -- Information about the crash: - What I was doing when the application crashed: I had closed an account and seemed to have problems pulling a budget report and then accidentally deleted that account and still have the same problem. - Custom settings of the application: There were no custom settings. I think the report worked fine until the account was closed. The crash can be reproduced every time. -- Backtrace: Application: KMyMoney (kmymoney), signal: Aborted [Current thread is 1 (Thread 0x7fc499ea2760 (LWP 1819))] Thread 2 (Thread 0x7fc489f8c700 (LWP 1820)): #0 0x00007fc494864203 in poll () from /lib/libc.so.6 #1 0x00007fc48f9bf009 in ?? () from /lib/libglib-2.0.so.0 #2 0x00007fc48f9bf7b5 in g_main_loop_run () from /lib/libglib-2.0.so.0 #3 0x00007fc48a6c33c4 in ?? () from /usr/lib/libgio-2.0.so.0 #4 0x00007fc48f9e47e4 in ?? () from /lib/libglib-2.0.so.0 #5 0x00007fc4974c0971 in start_thread () from /lib/libpthread.so.0 #6 0x00007fc49487092d in clone () from /lib/libc.so.6 #7 0x0000000000000000 in ?? () Thread 1 (Thread 0x7fc499ea2760 (LWP 1819)): [KCrash Handler] #6 0x00007fc4947bdba5 in raise () from /lib/libc.so.6 #7 0x00007fc4947c16b0 in abort () from /lib/libc.so.6 #8 0x00007fc4950616bd in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/libstdc++.so.6 #9 0x00007fc49505f906 in ?? () from /usr/lib/libstdc++.so.6 #10 0x00007fc49505f933 in std::terminate() () from /usr/lib/libstdc++.so.6 #11 0x00007fc49505fa3e in __cxa_throw () from /usr/lib/libstdc++.so.6 #12 0x00000000004541d1 in main (argc=<value optimized out>, argv=<value optimized out>) at /build/buildd/kmymoney-4.5/kmymoney/main.cpp:266 Possible duplicates by query: bug 267764, bug 267665, bug 267635, bug 267598, bug 267589. Reported using DrKonqi
Does this problem persist in newer versions of KMyMoney (e.g. 4.5.3)?
Just updated the status
I deleted the budget, created a new one and have no issues with this problem anymore.