Summary: | KmyMoney keeps "Checking for overdue scheduled transactions" | ||
---|---|---|---|
Product: | [Applications] kmymoney | Reporter: | highnoon52 |
Component: | general | Assignee: | KMyMoney Devel Mailing List <kmymoney-devel> |
Status: | RESOLVED WAITINGFORINFO | ||
Severity: | crash | CC: | ostroffjh, puydt, rvalkass |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
highnoon52
2010-11-15 01:29:30 UTC
Depending on the amount of overdue schedules, the application can take a long time. Let it finish. Can you create an anonymous version of your file and check that the problem shows up using it? See http://kmymoney2.sourceforge.net/kde4/online-manual/details.formats.anonymous.html for details on how to create that file. *** Bug 266123 has been marked as a duplicate of this bug. *** Could you try to open this file with the newest version of kmymoney? Any news on this? If not, I will close the entry. I can report that KMyMoney is still exhibiting this bug occasionally. When starting KMyMoney the Home screen is greyed out (and never loads), the message of the day displays, but does not respond to mouse clicks, and the status bar in the bottom right states KMyMoney is checking for overdue scheduled transactions. This has been left running for about 20 minutes with no change, so I don't think it's taking a while considering I only have maybe a dozen scheduled transactions. Rather than a crash of any description, this looks like an infinite loop. Unfortunately, I can't make an anonymised version of my data as KMyMoney enters the infinite loop as soon as it opens. Is there a way to generate an anonymised file from the command line? Terminal output: rob@hydrogen:~$ kmymoney KMyMoney reconciliation report plugin loaded KMyMoney printcheck plugin loaded QFSFileEngine::open: No file name specified KMyMoney iCalendar plugin loaded reading file start parsing file startDocument reading accounts reading transactions reading securities reading currencies reading prices reading reports endDocument Killed rob@hydrogen:~$ Backtrace during the infinite loop: (gdb) thread apply all backtrace Thread 2 (Thread 0x7f3c9a874700 (LWP 3855)): #0 0x00007f3cac91a473 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x00007f3ca8093f68 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007f3ca8094429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007f3cae475ed6 in QEventDispatcherGlib::processEvents (this=0x1f49f50, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:422 #4 0x00007f3cae449cf2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149 #5 0x00007f3cae449ef7 in QEventLoop::exec (this=0x7f3c9a873dd0, flags=...) at kernel/qeventloop.cpp:201 #6 0x00007f3cae36127f in QThread::exec (this=<optimized out>) at thread/qthread.cpp:498 #7 0x00007f3cae42ccbf in QInotifyFileSystemWatcherEngine::run (this=0x1f49480) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x00007f3cae363d05 in QThreadPrivate::start (arg=0x1f49480) at thread/qthread_unix.cpp:331 #9 0x00007f3caf58defc in start_thread (arg=0x7f3c9a874700) at pthread_create.c:304 #10 0x00007f3cac92659d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x0000000000000000 in ?? () Thread 1 (Thread 0x7f3cb1f63780 (LWP 3854)): #0 0x00007f3cae44dfea in QCoreApplication::removePostedEvents (receiver=0x8ae2500, eventType=0) at kernel/qcoreapplication.cpp:1525 #1 0x00007f3cad5cd132 in QWidget::~QWidget (this=0x8ae2500, __in_chrg=<optimized out>) at kernel/qwidget.cpp:1653 #2 0x00007f3cad9f6319 in QToolButton::~QToolButton (this=0x8ae2500, __in_chrg=<optimized out>) at widgets/qtoolbutton.cpp:412 #3 0x00007f3cae45cd75 in QObjectPrivate::deleteChildren (this=0x869bb00) at kernel/qobject.cpp:1955 #4 0x00007f3cad5cd12a in QWidget::~QWidget (this=0x86a9950, __in_chrg=<optimized out>) at kernel/qwidget.cpp:1651 #5 0x00007f3cb063d8d9 in KDatePicker::~KDatePicker (this=0x86a9950, __in_chrg=<optimized out>) at ../../kdeui/widgets/kdatepicker.cpp:334 #6 0x00007f3cae45cd75 in QObjectPrivate::deleteChildren (this=0x8503360) at kernel/qobject.cpp:1955 #7 0x00007f3cad5cd12a in QWidget::~QWidget (this=0x8b70a60, __in_chrg=<optimized out>) at kernel/qwidget.cpp:1651 #8 0x00007f3cb0698969 in KVBox::~KVBox (this=0x8b70a60, __in_chrg=<optimized out>) at ../../kdeui/widgets/kvbox.cpp:29 #9 0x00007f3caf9f5a73 in kMyMoneyDateInput::~kMyMoneyDateInput (this=0x7fff65704800, __in_chrg=<optimized out>) at /build/buildd/kmymoney-4.5.3/kmymoney/widgets/kmymoneydateinput.cpp:226 #10 0x00000000005c1949 in KMyMoneyTransactionForm::TransactionForm::adjustColumn (this=0x83e7410, col=KMyMoneyTransactionForm::ValueColumn2) at /build/buildd/kmymoney-4.5.3/kmymoney/widgets/transactionform.cpp:401 #11 0x00000000005c1ae1 in KMyMoneyTransactionForm::TransactionForm::resize (this=0x83e7410, col=1) at /build/buildd/kmymoney-4.5.3/kmymoney/widgets/transactionform.cpp:378 #12 0x00000000005c1e14 in KMyMoneyTransactionForm::TransactionForm::qt_metacall (this=0x83e7410, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0x8b14e20) at /build/buildd/kmymoney-4.5.3/obj-x86_64-linux-gnu/kmymoney/widgets/transactionform.moc:208 #13 0x00007f3cae461a5e in QObject::event (this=0x83e7410, e=<optimized out>) at kernel/qobject.cpp:1217 #14 0x00007f3cad5d173b in QWidget::event (this=0x83e7410, event=0x82ecbb0) at kernel/qwidget.cpp:8754 #15 0x00007f3cad97a5b6 in QFrame::event (this=0x83e7410, e=0x82ecbb0) at widgets/qframe.cpp:557 #16 0x00007f3cad9fc2fb in QAbstractScrollArea::event (this=0x83e7410, e=0x82ecbb0) at widgets/qabstractscrollarea.cpp:996 #17 0x00007f3cada94c1b in QAbstractItemView::event (this=0x83e7410, event=0x82ecbb0) at itemviews/qabstractitemview.cpp:1564 #18 0x00007f3cad581474 in notify_helper (e=0x82ecbb0, receiver=0x83e7410, this=0x185da10) at kernel/qapplication.cpp:4486 #19 QApplicationPrivate::notify_helper (this=0x185da10, receiver=0x83e7410, e=0x82ecbb0) at kernel/qapplication.cpp:4458 #20 0x00007f3cad5862e1 in QApplication::notify (this=0x18542f0, receiver=0x83e7410, e=0x82ecbb0) at kernel/qapplication.cpp:4365 #21 0x00007f3cb05a1466 in KApplication::notify (this=0x18542f0, receiver=0x83e7410, event=0x82ecbb0) at ../../kdeui/kernel/kapplication.cpp:311 #22 0x00007f3cae44aafc in QCoreApplication::notifyInternal (this=0x18542f0, receiver=0x83e7410, event=0x82ecbb0) at kernel/qcoreapplication.cpp:787 #23 0x00007f3cae44e51f in sendEvent (event=0x82ecbb0, receiver=0x83e7410) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #24 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x182d430) at kernel/qcoreapplication.cpp:1428 #25 0x00007f3cae475a73 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220 #26 postEventSourceDispatch (s=<optimized out>) at kernel/qeventdispatcher_glib.cpp:277 #27 0x00007f3ca8093a5d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #28 0x00007f3ca8094258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #29 0x00007f3ca8094429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #30 0x00007f3cae475ed6 in QEventDispatcherGlib::processEvents (this=0x182ef40, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:422 #31 0x00007f3cad62910e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=<optimized out>) at kernel/qguieventdispatcher_glib.cpp:204 #32 0x00007f3cae44e8a9 in QCoreApplication::processEvents (flags=..., maxtime=10) at kernel/qcoreapplication.cpp:1007 #33 0x00000000006d7d14 in TransactionEditor::enterTransactions (this=0x80f74c0, newId=..., askForSchedule=false, suppressBalanceWarnings=false) at /build/buildd/kmymoney-4.5.3/kmymoney/dialogs/transactioneditor.cpp:486 #34 0x0000000000487e0f in KMyMoneyApp::enterSchedule (this=0x19032d0, schedule=..., autoEnter=<optimized out>, extendedKeys=<optimized out>) at /build/buildd/kmymoney-4.5.3/kmymoney/kmymoney.cpp:4444 #35 0x0000000000488e18 in KMyMoneyApp::slotCheckSchedules (this=0x19032d0) at /build/buildd/kmymoney-4.5.3/kmymoney/kmymoney.cpp:6442 #36 0x0000000000493bda in KMyMoneyApp::slotFileOpenRecent (this=0x19032d0, url=...) at /build/buildd/kmymoney-4.5.3/kmymoney/kmymoney.cpp:1514 #37 0x0000000000455146 in main (argc=1, argv=<optimized out>) at /build/buildd/kmymoney-4.5.3/kmymoney/main.cpp:247 Try starting KMM from command line with "kmymoney -n" which will start without reading your data file. Turn off all the options on the home page (Settings/Configure KMyMoney.../Home). Then try to open your file, and run a consistency check. Same problem occurs. As soon as I open the file KMM enters an endless loop "Checking for overdue scheduled transactions...". I thought a consistency check ran every time the file was saved? Seeing as I haven't edited the file in any other application, it should be fine. Seeing as KMM becomes unresponsive as soon as the file is loaded, I'm not sure of any other way to force a consistency check. rvalkass@gmail.com On 15 May 2012 21:47, Jack <ostroffjh@users.sourceforge.net> wrote: > https://bugs.kde.org/show_bug.cgi?id=256945 > > --- Comment #7 from Jack <ostroffjh@users.sourceforge.net> --- > Try starting KMM from command line with "kmymoney -n" which will start > without > reading your data file. Turn off all the options on the home page > (Settings/Configure KMyMoney.../Home). Then try to open your file, and > run a > consistency check. > > -- > You are receiving this mail because: > You are on the CC list for the bug. > Rob - this will probably have to wait for one of the developers to look at the backtrace. However, it would help to know which version of KMM you are using - it looks like 4.5.3 from the backtrace - and that is rather old at this point. It is possible a more recent version (4.6.2 is latest) would avoid the problem. Also, when did you save the file you are trying to open (i.e., was it saved with an earlier version of KMM?) KMM does do a consistency check when it saves a file, but older versions did less checking. It is 4.5.3 - the latest package available from my distro. I will get a newer version of KMM up and running to see if that improves matters. I use the file every day or two, and it has been through a few versions of KMM over the last 3 or 4 years! This is the first time this problem has appeared, and the file has been used with 4.5.3 plenty of times previously. On 16 May 2012 21:20, Jack <ostroffjh@users.sourceforge.net> wrote: > https://bugs.kde.org/show_bug.cgi?id=256945 > > Jack <ostroffjh@users.sourceforge.net> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| |ostroffjh@users.sourceforge > | |.net > > --- Comment #9 from Jack <ostroffjh@users.sourceforge.net> --- > Rob - this will probably have to wait for one of the developers to look at > the > backtrace. However, it would help to know which version of KMM you are > using - > it looks like 4.5.3 from the backtrace - and that is rather old at this > point. > It is possible a more recent version (4.6.2 is latest) would avoid the > problem. Also, when did you save the file you are trying to open (i.e., > was it > saved with an earlier version of KMM?) KMM does do a consistency check > when it > saves a file, but older versions did less checking. > > -- > You are receiving this mail because: > You are on the CC list for the bug. > Rob, can you try starting KMyMoney with option -n again and then turn off the option that runs the checking of schedules at startup? It can be found by opening the settings dialog and switching to the schedules tab. Does that make a difference when you open your file? I am pretty sure that we have fixed this problem since 4.5.3 but cannot find the trace w/o deeply looking into the log messages. And I currently don't have the time to do it. Hi, I've finally got around to compiling the latest version and can confirm the problem is fixed. File opened fine, so I've no idea what KMM had done to bork the file initially, but a newer version recovered it silently it seems. Good job :) On 18 May 2012 09:04, Thomas Baumgart <ipwizard@users.sourceforge.net>wrote: > https://bugs.kde.org/show_bug.cgi?id=256945 > > --- Comment #11 from Thomas Baumgart <ipwizard@users.sourceforge.net> --- > Rob, can you try starting KMyMoney with option -n again and then turn off > the > option that runs the checking of schedules at startup? It can be found by > opening the settings dialog and switching to the schedules tab. Does that > make > a difference when you open your file? > > I am pretty sure that we have fixed this problem since 4.5.3 but cannot > find > the trace w/o deeply looking into the log messages. And I currently don't > have > the time to do it. > > -- > You are receiving this mail because: > You are on the CC list for the bug. > |