Summary: | Crash on American Express OFX Direct Download | ||
---|---|---|---|
Product: | [Applications] kmymoney | Reporter: | Mike Wolfe <wolfemi1> |
Component: | general | Assignee: | KMyMoney Devel Mailing List <kmymoney-devel> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | crash | CC: | novosirj, ohernandez3, onet.cristian, rbowers28, ubuntujock, wolfemi1 |
Priority: | NOR | ||
Version: | SVN | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | New crash information added by DrKonqi |
Description
Mike Wolfe
2011-02-09 16:25:39 UTC
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----- |