Application: kmymoney (4.5.90-svn1217243) KDE Platform Version: 4.4.5 (KDE 4.4.5) Qt Version: 4.6.2 Operating System: Linux 2.6.32-28-generic i686 Distribution: Ubuntu 10.04.2 LTS -- Information about the crash: Same as previous crashing problem. I suspect bad input from American Express. If it is the same problem as last time (associated bug), I expect that this will go away soon. Is there any other information I can get while the problem still exists? The crash can be reproduced every time. -- Backtrace: Application: KMyMoney (kmymoney), signal: Aborted [Current thread is 1 (Thread 0xb7859950 (LWP 10746))] Thread 2 (Thread 0xb3d8cb70 (LWP 10747)): #0 0x008e8344 in __pthread_mutex_unlock_usercnt () from /lib/tls/i686/cmov/libpthread.so.0 #1 0x060d4e56 in ?? () from /lib/libglib-2.0.so.0 #2 0x060d54b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #3 0x03f7660f in QEventDispatcherGlib::processEvents (this=0x9d23bb0, flags=...) at kernel/qeventdispatcher_glib.cpp:414 #4 0x03f49059 in QEventLoop::processEvents (this=0xb3d8c270, flags=) at kernel/qeventloop.cpp:149 #5 0x03f494aa in QEventLoop::exec (this=0xb3d8c270, flags=...) at kernel/qeventloop.cpp:201 #6 0x03e455a8 in QThread::exec (this=0x9d0eba8) at thread/qthread.cpp:487 #7 0x03f28c1b in QInotifyFileSystemWatcherEngine::run (this=0x9d0eba8) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x03e4832e in QThreadPrivate::start (arg=0x9d0eba8) at thread/qthread_unix.cpp:248 #9 0x008e496e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #10 0x00e47a4e in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 1 (Thread 0xb7859950 (LWP 10746)): [KCrash Handler] #6 0x00641422 in __kernel_vsyscall () #7 0x00da4651 in raise () from /lib/tls/i686/cmov/libc.so.6 #8 0x00da7a82 in abort () from /lib/tls/i686/cmov/libc.so.6 #9 0x0079352f in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/libstdc++.so.6 #10 0x00791465 in ?? () from /usr/lib/libstdc++.so.6 #11 0x007914a2 in std::terminate() () from /usr/lib/libstdc++.so.6 #12 0x0079155b in __cxa_rethrow () from /usr/lib/libstdc++.so.6 #13 0x03f5e75a in QMetaObject::activate (sender=0xab2e240, m=0x22d4c88, local_signal_index=3, argv=0xbfc34d18) at kernel/qobject.cpp:3303 #14 0x021661e3 in KJob::result (this=0xab2e240, _t1=0xab2e240) at ./kjob.moc:194 #15 0x02166548 in KJob::emitResult (this=0xab2e240) at ../../kdecore/jobs/kjob.cpp:312 #16 0x075b2c60 in KIO::SimpleJob::slotFinished (this=0xab2e240) at ../../kio/kio/job.cpp:517 #17 0x075b36a0 in KIO::TransferJob::slotFinished (this=0xab2e240) at ../../kio/kio/job.cpp:1097 #18 0x075b0ac3 in KIO::TransferJob::qt_metacall (this=0xab2e240, _c=QMetaObject::InvokeMetaMethod, _id=47, _a=0xbfc34fac) at ./jobclasses.moc:367 #19 0x03f4fc9a in QMetaObject::metacall (object=0xab2e240, cl=10746, idx=47, argv=0xbfc34fac) at kernel/qmetaobject.cpp:237 #20 0x03f5e3d5 in QMetaObject::activate (sender=0xac543c0, m=0x7761f44, local_signal_index=4, argv=0x0) at kernel/qobject.cpp:3293 #21 0x0767d2a7 in KIO::SlaveInterface::finished (this=0xac543c0) at ./slaveinterface.moc:171 #22 0x076805cd in KIO::SlaveInterface::dispatch (this=0xac543c0, _cmd=104, rawdata=...) at ../../kio/kio/slaveinterface.cpp:175 #23 0x0767d763 in KIO::SlaveInterface::dispatch (this=0xac543c0) at ../../kio/kio/slaveinterface.cpp:91 #24 0x07670c28 in KIO::Slave::gotInput (this=0xac543c0) at ../../kio/kio/slave.cpp:324 #25 0x07670e33 in KIO::Slave::qt_metacall (this=0xac543c0, _c=QMetaObject::InvokeMetaMethod, _id=30, _a=0xbfc352bc) at ./slave.moc:82 #26 0x03f4fc9a in QMetaObject::metacall (object=0xac543c0, cl=10746, idx=30, argv=0xbfc352bc) at kernel/qmetaobject.cpp:237 #27 0x03f5e3d5 in QMetaObject::activate (sender=0xac48230, m=0x775e820, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3293 #28 0x0757abd7 in KIO::Connection::readyRead (this=0xac48230) at ./connection.moc:92 #29 0x0757cf8e in KIO::ConnectionPrivate::dequeue (this=0xb0e1638) at ../../kio/kio/connection.cpp:82 #30 0x0757d0be in KIO::Connection::qt_metacall (this=0xac48230, _c=QMetaObject::InvokeMetaMethod, _id=5, _a=0xa89d618) at ./connection.moc:79 #31 0x03f4fc9a in QMetaObject::metacall (object=0xac48230, cl=10746, idx=5, argv=0xa89d618) at kernel/qmetaobject.cpp:237 #32 0x03f5a336 in QMetaCallEvent::placeMetaCall (this=0xad5a7e0, object=0xac48230) at kernel/qobject.cpp:561 #33 0x03f5b3fe in QObject::event (this=0xac48230, e=0xad5a7e0) at kernel/qobject.cpp:1248 #34 0x0173a4dc in QApplicationPrivate::notify_helper (this=0x987efb0, receiver=0xac48230, e=0xad5a7e0) at kernel/qapplication.cpp:4300 #35 0x0174105e in QApplication::notify (this=0x987ef30, receiver=0xac48230, e=0xad5a7e0) at kernel/qapplication.cpp:3704 #36 0x003ed40a in KApplication::notify (this=0x987ef30, receiver=0xac48230, event=0xad5a7e0) at ../../kdeui/kernel/kapplication.cpp:302 #37 0x03f4aa3b in QCoreApplication::notifyInternal (this=0x987ef30, receiver=0xac48230, event=0xad5a7e0) at kernel/qcoreapplication.cpp:704 #38 0x03f4d473 in QCoreApplication::sendEvent (receiver=0x0, event_type=0, data=0x98652e0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #39 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x98652e0) at kernel/qcoreapplication.cpp:1345 #40 0x03f4d5dd in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1238 #41 0x03f76adf in QCoreApplication::sendPostedEvents (s=0x9881310) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220 #42 postEventSourceDispatch (s=0x9881310) at kernel/qeventdispatcher_glib.cpp:276 #43 0x060d15e5 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #44 0x060d52d8 in ?? () from /lib/libglib-2.0.so.0 #45 0x060d54b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #46 0x03f765d5 in QEventDispatcherGlib::processEvents (this=0x98654c0, flags=...) at kernel/qeventdispatcher_glib.cpp:412 #47 0x017fa135 in QGuiEventDispatcherGlib::processEvents (this=0x98654c0, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #48 0x03f49059 in QEventLoop::processEvents (this=0xbfc35b70, flags=) at kernel/qeventloop.cpp:149 #49 0x03f494aa in QEventLoop::exec (this=0xbfc35b70, flags=...) at kernel/qeventloop.cpp:201 #50 0x01c794f3 in QDialog::exec (this=0xb0cbcd0) at dialogs/qdialog.cpp:546 #51 0x067829eb in OfxImporterPlugin::updateAccount (this=0xa2170e8, acc=..., moreAccounts=true) at /home/wolfemi1/svn/kmymoney/kmymoney/plugins/ofximport/ofximporterplugin.cpp:653 #52 0x080b199e in KMyMoneyApp::slotAccountUpdateOnlineAll (this=0x98b0328) at /home/wolfemi1/svn/kmymoney/kmymoney/kmymoney.cpp:6896 #53 0x080ddad5 in KMyMoneyApp::qt_metacall (this=0x98b0328, _c=QMetaObject::InvokeMetaMethod, _id=103, _a=0xbfc36038) at /home/wolfemi1/svn/kmymoney/build/kmymoney/kmymoney.moc:506 #54 0x03f4fc9a in QMetaObject::metacall (object=0x98b0328, cl=10746, idx=149, argv=0xbfc36038) at kernel/qmetaobject.cpp:237 #55 0x03f5e3d5 in QMetaObject::activate (sender=0x9a0a748, m=0x2062d58, local_signal_index=1, argv=0xbfc36038) at kernel/qobject.cpp:3293 #56 0x01733bd9 in QAction::triggered (this=0x9a0a748, _t1=false) at .moc/release-shared/moc_qaction.cpp:263 #57 0x01735dcc in QAction::activate (this=0x9a0a748, event=QAction::Trigger) at kernel/qaction.cpp:1255 #58 0x01c28bd2 in QAction::trigger (this=0x6) at ../../include/QtGui/../../src/gui/kernel/qaction.h:218 #59 QToolButton::nextCheckState (this=0x6) at widgets/qtoolbutton.cpp:1147 #60 0x01b45cb3 in QAbstractButtonPrivate::click (this=0x9a729f0) at widgets/qabstractbutton.cpp:528 #61 0x01b45fae in QAbstractButton::mouseReleaseEvent (this=0x9a72998, e=0xbfc367a0) at widgets/qabstractbutton.cpp:1121 #62 0x01c2909c in QToolButton::mouseReleaseEvent (this=0x9a72998, e=0xbfc367a0) at widgets/qtoolbutton.cpp:721 #63 0x017987f8 in QWidget::event (this=0x9a72998, event=0xbfc367a0) at kernel/qwidget.cpp:7998 #64 0x01b44d4e in QAbstractButton::event (this=0x9a72998, e=0x6) at widgets/qabstractbutton.cpp:1080 #65 0x01c2bbca in QToolButton::event (this=0x9a72998, event=0xbfc367a0) at widgets/qtoolbutton.cpp:1163 #66 0x0173a4dc in QApplicationPrivate::notify_helper (this=0x987efb0, receiver=0x9a72998, e=0xbfc367a0) at kernel/qapplication.cpp:4300 #67 0x017419f7 in QApplication::notify (this=0x987ef30, receiver=0x9a72998, e=0xbfc367a0) at kernel/qapplication.cpp:3865 #68 0x003ed40a in KApplication::notify (this=0x987ef30, receiver=0x9a72998, event=0xbfc367a0) at ../../kdeui/kernel/kapplication.cpp:302 #69 0x03f4aa3b in QCoreApplication::notifyInternal (this=0x987ef30, receiver=0x9a72998, event=0xbfc367a0) at kernel/qcoreapplication.cpp:704 #70 0x01740952 in QCoreApplication::sendEvent (receiver=0x9a72998, event=0xbfc367a0, alienWidget=0x9a72998, nativeWidget=0x9a6a850, buttonDown=0x207e058, lastMouseReceiver=..., spontaneous=true) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #71 QApplicationPrivate::sendMouseEvent (receiver=0x9a72998, event=0xbfc367a0, alienWidget=0x9a72998, nativeWidget=0x9a6a850, buttonDown=0x207e058, lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:2965 #72 0x017cc088 in QETWidget::translateMouseEvent (this=0x9a6a850, event=0xbfc36cbc) at kernel/qapplication_x11.cpp:4368 #73 0x017cb511 in QApplication::x11ProcessEvent (this=0x987ef30, event=0xbfc36cbc) at kernel/qapplication_x11.cpp:3379 #74 0x017fa60a in x11EventSourceDispatch (s=0x9881cf8, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146 #75 0x060d15e5 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #76 0x060d52d8 in ?? () from /lib/libglib-2.0.so.0 #77 0x060d54b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #78 0x03f765d5 in QEventDispatcherGlib::processEvents (this=0x98654c0, flags=...) at kernel/qeventdispatcher_glib.cpp:412 #79 0x017fa135 in QGuiEventDispatcherGlib::processEvents (this=0x98654c0, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #80 0x03f49059 in QEventLoop::processEvents (this=0xbfc36fb4, flags=) at kernel/qeventloop.cpp:149 #81 0x03f494aa in QEventLoop::exec (this=0xbfc36fb4, flags=...) at kernel/qeventloop.cpp:201 #82 0x03f4d69f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981 #83 0x0173a577 in QApplication::exec () at kernel/qapplication.cpp:3579 #84 0x0808ba07 in main (argc=1, argv=0xbfc37444) at /home/wolfemi1/svn/kmymoney/kmymoney/main.cpp:260 This bug may be a duplicate of or related to bug 251737. Possible duplicates by query: bug 265838, bug 262289, bug 260683, bug 259916, bug 255512. Reported using DrKonqi
More information: Crash still happens on command, but I can make it NOT crash by setting the number of days to go back in "Account Settings" from 60 to 59 (I also tried 30, 50, 55, and 57, all of which worked correctly with no crash). This account is one of the more frequently used of mine; could it be the number of transactions is a problem? At 59 days, I got 94 imported transactions from this. Is there a limit to the amount of data that can be sent in an OFX response?
Hi, does the file contain very long lines? If so it might be the old bug in LibOFX... Regards Martin On Donnerstag 10 Februar 2011, Mike Wolfe wrote: > https://bugs.kde.org/show_bug.cgi?id=265889 > > > > > > --- Comment #1 from Mike Wolfe <wolfemi1 gmail com> 2011-02-10 05:42:05 > --- More information: Crash still happens on command, but I can make it > NOT crash by setting the number of days to go back in "Account Settings" > from 60 to 59 (I also tried 30, 50, 55, and 57, all of which worked > correctly with no crash). This account is one of the more frequently used > of mine; could it be the number of transactions is a problem? At 59 days, > I got 94 imported transactions from this. Is there a limit to the amount > of data that can be sent in an OFX response?
I'm not sure, how could I find this out? -Mike On 2/10/2011 11:49 AM, martin@aqbanking.de wrote: > https://bugs.kde.org/show_bug.cgi?id=265889 > > > > > > --- Comment #2 from<martin aqbanking de> 2011-02-10 18:49:29 --- > Hi, > > does the file contain very long lines? If so it might be the old bug in > LibOFX... > > > Regards > Martin > > > On Donnerstag 10 Februar 2011, Mike Wolfe wrote: >> https://bugs.kde.org/show_bug.cgi?id=265889 >> >> >> >> >> >> --- Comment #1 from Mike Wolfe<wolfemi1 gmail com> 2011-02-10 05:42:05 >> --- More information: Crash still happens on command, but I can make it >> NOT crash by setting the number of days to go back in "Account Settings" >> from 60 to 59 (I also tried 30, 50, 55, and 57, all of which worked >> correctly with no crash). This account is one of the more frequently used >> of mine; could it be the number of transactions is a problem? At 59 days, >> I got 94 imported transactions from this. Is there a limit to the amount >> of data that can be sent in an OFX response?
Create a file called "ofxlog.txt" in the home directory of the user you start KMyMoney in. (A simple 'touch ~/ofxlog.txt' does that). Then run KMyMoney and start downloading your data. Be aware that the file also contains sensible data. If you start the download multiple times, the new data will be appended to the file. Simply removing the file stops tracing.
Okay, I tried to get logging enabled and created the file, but now everything works again. I tried removing the file, increasing the length of time to go back in the OFX request, but everything works fine now. I hate phantom problems. :( By the way, I did apply the latest update to the code, which were changes in revision 1220036 (changes to kstartuplogo.cpp, kwelcomepage.cpp, and CMakeLists.txt). I strongly doubt that those changes made the difference though. I'll keep in touch if you would like me to try anything else to diagnose/reproduce the problem, otherwise it looks like it's vanished again. -Mike On 2/11/2011 3:14 AM, Thomas Baumgart wrote: > https://bugs.kde.org/show_bug.cgi?id=265889 > > > > > > --- Comment #4 from Thomas Baumgart<ipwizard users sourceforge net> 2011-02-11 10:14:21 --- > Create a file called "ofxlog.txt" in the home directory of the user you start > KMyMoney in. (A simple 'touch ~/ofxlog.txt' does that). Then run KMyMoney and > start downloading your data. > > Be aware that the file also contains sensible data. If you start the download > multiple times, the new data will be appended to the file. > > Simply removing the file stops tracing. >
Created attachment 57696 [details] New crash information added by DrKonqi kmymoney (4.5.90-svn1223783) on KDE Platform 4.5.1 (KDE 4.5.1) using Qt 4.7.0 - What I was doing when the application crashed: Automatic OFX download causes a crash, verified by using several different accounts. Note: this is after upgrading to Kubuntu 10.10. This time the crash is completely reproducible, from ANY account update, and changing the number of days to download in the properties seems to have no effect. I may have been doing it wrong, but I put a file named ofxlog.txt in my home directory, and it has not been modified. Is this the correct file and location to try to capture OFX log data? -- Backtrace (Reduced): #15 0x08d7d8a3 in KJob::result (this=0xbe9a0a0, _t1=0xbe9a0a0) at ./kjob.moc:194 #16 0x08d7dc08 in KJob::emitResult (this=0xbe9a0a0) at ../../kdecore/jobs/kjob.cpp:312 #17 0x04b5e480 in KIO::SimpleJob::slotFinished (this=0xbe9a0a0) at ../../kio/kio/job.cpp:522 #18 0x04b5e960 in KIO::TransferJob::slotFinished (this=0xbe9a0a0) at ../../kio/kio/job.cpp:1111 #19 0x04b5c453 in KIO::TransferJob::qt_metacall (this=0xbe9a0a0, _c=QMetaObject::InvokeMetaMethod, _id=47, _a=0xbf80033c) at ./jobclasses.moc:367
I am having this problem and I touched the ofxlog.txt file. The crash occurs before getting to the point where anything is written to this file. I've verified that it does work by updating an account that doesn't have this problem.
*** Bug 268717 has been marked as a duplicate of this bug. ***
*** Bug 259611 has been marked as a duplicate of this bug. ***
*** Bug 272261 has been marked as a duplicate of this bug. ***
Any news on this since it seems it got quite a few reports?
Current SVN trunk has a modification that will start writing to the log file earlier so that we should see something in it. Can someone use this version to do some more testing, please?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This appears to be the result of a condition in my account (which has since disappeared, reappeared at some later time, and disappeared again). The next time it happens, I can give this a whack. It seems that the next time you have a transaction on the card, it will clear up whatever the problem is. On 07/02/2011 01:09 PM, Thomas Baumgart wrote: > https://bugs.kde.org/show_bug.cgi?id=265889 > > > Thomas Baumgart <ipwizard@users.sourceforge.net> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|UNCONFIRMED |NEEDSINFO > Resolution| |WAITINGFORINFO > > > > > --- Comment #12 from Thomas Baumgart <ipwizard users sourceforge net> 2011-07-02 17:09:07 --- > Current SVN trunk has a modification that will start writing to the log file > earlier so that we should see something in it. Can someone use this version to > do some more testing, please? > - -- - ---- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Sr. Systems Programmer |$&| |__| | | |__/ | \| _| |novosirj@umdnj.edu - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/CST-Academic Svcs. - ADMC 450, Newark -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk4PWHAACgkQmb+gadEcsb7JIQCeOFXJQ1AuRKOhuZz5CqTWm9eh jn4An1xPPYjoNjPop7SBGXhHGZVRhUbe =0ewh -----END PGP SIGNATURE-----
Any news yet? Or did the problem not show up until now?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 For me, this seems to be directly related to the data being fed from AmEx. The data either causes the problem (once in a blue moon) or does not (the overwhelming majority of the time). When my account is in such a state to cause a crash, the next time I use my card and that transaction goes in, the problem is solved. It hasn't happened in about a year (but I've not changed KMyMoney versions either so an upgrade was not the fix). On 07/21/2011 02:58 PM, Thomas Baumgart wrote: > https://bugs.kde.org/show_bug.cgi?id=265889 > > > > > > --- Comment #14 from Thomas Baumgart <ipwizard users sourceforge net> 2011-07-21 18:58:35 --- > Any news yet? Or did the problem not show up until now? > - -- - ---- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Sr. Systems Programmer |$&| |__| | | |__/ | \| _| |novosirj@umdnj.edu - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/CST-Academic Svcs. - ADMC 450, Newark -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk4oeiQACgkQmb+gadEcsb6rHgCg3ttaFGdrvLtxU/4YUNWQqbPb YG8AoItuT8+8zbLWHrUq7B79/kIv+bhT =K9Tv -----END PGP SIGNATURE-----