Bug 319548

Summary: KMYMONEY Crashes when opening any "Budget" report
Product: [Applications] kmymoney Reporter: jchadeau
Component: generalAssignee: KMyMoney Devel Mailing List <kmymoney-devel>
Status: RESOLVED DUPLICATE    
Severity: crash CC: agander93, mk-lists, onet.cristian
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description jchadeau 2013-05-08 21:54:57 UTC
Application: kmymoney (4.5.3)
KDE Platform Version: 4.7.4 (4.7.4)
Qt Version: 4.7.4
Operating System: Linux 3.0.0-32-generic x86_64
Distribution: Ubuntu 11.10

-- Information about the crash:
- What I was doing when the application crashed: Opened a "budget" report

This crash happens systematically and crashes the app on startup if budget is ticked on the welcome window.
Seems to come back over and over whenever I change anything in categorisation (i think I've "repaired" it sometimes by altering something in the budget)

- Custom settings of the application:

The crash can be reproduced every time.

-- Backtrace:
Application: KMyMoney (kmymoney), signal: Aborted
[Current thread is 1 (Thread 0x7fc4779d9780 (LWP 16657))]

Thread 3 (Thread 0x7fc45f90d700 (LWP 16660)):
#0  0x00007fc47238ce63 in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x00007fc46db04f68 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fc46db05792 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fc46702e516 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#4  0x00007fc46db2a2b6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007fc475000efc in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#6  0x00007fc472398f8d in clone () from /lib/x86_64-linux-gnu/libc.so.6
#7  0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7fc46010e700 (LWP 16793)):
#0  0x00007fc47238ce63 in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x00007fc46db04f68 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fc46db05429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fc473ee8f3e in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#4  0x00007fc473ebccf2 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#5  0x00007fc473ebcef7 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#6  0x00007fc473dd427f in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#7  0x00007fc473e9fcbf in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#8  0x00007fc473dd6d05 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#9  0x00007fc475000efc in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#10 0x00007fc472398f8d in clone () from /lib/x86_64-linux-gnu/libc.so.6
#11 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fc4779d9780 (LWP 16657)):
[KCrash Handler]
#6  0x00007fc4722ea3e5 in raise () from /lib/x86_64-linux-gnu/libc.so.6
#7  0x00007fc4722edb4b in abort () from /lib/x86_64-linux-gnu/libc.so.6
#8  0x00007fc472bacd7d in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#9  0x00007fc472baaf26 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#10 0x00007fc472baaf53 in std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#11 0x00007fc472bab096 in __cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#12 0x00007fc473ebd02e in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#13 0x00007fc473ec1789 in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#14 0x0000000000454115 in main (argc=1, argv=<optimized out>) at /build/buildd/kmymoney-4.5.3/kmymoney/main.cpp:260

Possible duplicates by query: bug 319540, bug 319478, bug 319471, bug 319469, bug 319457.

Reported using DrKonqi
Comment 1 Marko Käning 2013-05-09 17:56:24 UTC
Can you upgrade to the latest version 4.6.3 and test wether the error persists with your KMM file?
Comment 2 jchadeau 2013-05-09 20:55:12 UTC
Hi and thanks,

ok I will upgrade and try again with the same file. It might take some
time though as i am on the verge of moving house and will not have
internet for a few days, I'll let you know asap,

Good night,




Le jeudi 09 mai 2013 à 17:56 +0000, Marko Käning a écrit :
> https://bugs.kde.org/show_bug.cgi?id=319548
> 
> Marko Käning <mk-lists@email.de> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                  CC|                            |mk-lists@email.de
> 
> --- Comment #1 from Marko Käning <mk-lists@email.de> ---
> Can you upgrade to the latest version 4.6.3 and test wether the error persists
> with your KMM file?
>
Comment 3 Marko Käning 2013-07-21 11:56:27 UTC
Did you have a chance to test whether the problem persists with the new version?

BTW, I recall that a few days ago it was recommended to delete the old budget reports and create new ones from scratch, which could be a viable workaround perhaps.
Comment 4 jchadeau 2013-07-21 13:33:22 UTC
Hi Marko,

Sorry, as i have been moving house, job and everything and I am not a
fluent linux user I am a bit scared to mess everything up as I have very
few time for it. Thx for yr help anyway ! I need to upgrade the whole OS
and everything, hope I can do it this summer,but kitchen need to be done
first...

Thanx and I will let you know !


 Bye

Le dimanche 21 juillet 2013 à 11:56 +0000, Marko Käning a écrit :
> https://bugs.kde.org/show_bug.cgi?id=319548
> 
> --- Comment #3 from Marko Käning <mk-lists@email.de> ---
> Did you have a chance to test whether the problem persists with the new
> version?
> 
> BTW, I recall that a few days ago it was recommended to delete the old budget
> reports and create new ones from scratch, which could be a viable workaround
> perhaps.
>
Comment 5 Cristian Oneț 2013-08-29 12:51:27 UTC
Did the update help?
Comment 6 jchadeau 2013-08-29 19:53:10 UTC
Hi Cristian,

Thanks for your help but I am unable to update to newer version, I am
just Ubuntu and Synaptic user, I've tried to look in the sourceforge
website but I can't cope with build, make, cvs and so on... and I don't
know if I can run better with my outdated no-kde system

Many thanks again, have a good evening,

Jb Chadeau  


Le jeudi 29 août 2013 à 12:51 +0000, Cristian Oneț a écrit :
> https://bugs.kde.org/show_bug.cgi?id=319548
> 
> Cristian Oneț <onet.cristian@gmail.com> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>              Status|UNCONFIRMED                 |NEEDSINFO
>                  CC|                            |onet.cristian@gmail.com
>          Resolution|---                         |WAITINGFORINFO
> 
> --- Comment #5 from Cristian Oneț <onet.cristian@gmail.com> ---
> Did the update help?
>
Comment 7 allan 2013-08-29 20:01:49 UTC
Have a look for the Claydoh PPA, which has available a pretty up-to-date .deb version, so no build required, and it will be recognised by synaptic.
Comment 8 jchadeau 2013-09-10 20:57:53 UTC
Dear all,

I finally got round the update to 4.6.3 with the claydoh rep and it
seems to have solved the problem. Thanks to all of you for the help !

Bye


Le jeudi 29 août 2013 à 20:01 +0000, allan a écrit :
> https://bugs.kde.org/show_bug.cgi?id=319548
> 
> allan <agander93@gmail.com> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                  CC|                            |agander93@gmail.com
> 
> --- Comment #7 from allan <agander93@gmail.com> ---
> Have a look for the Claydoh PPA, which has available a pretty up-to-date .deb
> version, so no build required, and it will be recognised by synaptic.
>
Comment 9 Cristian Oneț 2013-09-11 06:48:05 UTC
Thanks for the follow up, marking it at resolved.
Comment 10 Alvaro Soliverez 2013-09-11 10:54:42 UTC

*** This bug has been marked as a duplicate of bug 290737 ***