Bug 408833

Summary: Receiving import unable to parse error message when using AppImage stable or nightly build
Product: [Applications] kmymoney Reporter: Michael Carpino <mfcarpino>
Component: bugtrackerAssignee: KMyMoney Devel Mailing List <kmymoney-devel>
Status: RESOLVED WORKSFORME    
Severity: normal    
Priority: NOR    
Version: 5.0.4   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: Screenshot error message
attachment-19924-0.html
io-slave error message

Description Michael Carpino 2019-06-17 15:02:16 UTC
Created attachment 120951 [details]
Screenshot error message

SUMMARY When I attempt to online update a mapped account when using KMM I'm receiving an "Unable to parse" error message.  This problem is with both the stable or nightly build AppImage.  Here are the 2 versions I tried, KMyMoney-5.0.4-7949caa-x86_64.AppImage and KMyMoney-5.0.80-885d683-x86_64.AppImage. If I use the software application version 5.0.1-2 the problem doesn't exist.


STEPS TO REPRODUCE
1. Use Zorin 15 - Ubuntu
2. Install AppImage
3. Update a mapped account using the Account > Update Account feature

OBSERVED RESULT
Receiving Unable to parse error message

EXPECTED RESULT
Account to be updated with current transactions

SOFTWARE/OS VERSIONS
 
Linux Zorin 15
Kernel Linux 4.18.0-21-generic #22~18.04.1-Ubuntu SMP
Gnome Version: 3.30.2

ADDITIONAL INFORMATION
Comment 1 Jack 2019-06-17 15:20:19 UTC
If you run from command line, is there any more informative error?  Have you tried downloading an OFX file and then importing the file?  If you get the same error, you can then actually look at the file to see if anything looks odd.

Also, you can capture the online update OFX as a file (~/ofx.log) For that, go to the KMM configuration window, General view, Support tab.
Comment 2 Michael Carpino 2019-06-18 13:40:00 UTC
I tried importing the OFX transactions via QFX by downloading it and then using the import feature and received the same error message with AppImage 5.0.4.

Then I captured the OFX transactions for both KMM 5.0.1 & 5.0.4 and compared the content.  The only difference is the timestamp information which should be the case.
Comment 3 Thomas Baumgart 2019-06-18 16:28:28 UTC
Scanning the source code, I see that this message is presented in case no account information and no statement information is reported by the OFX library. 

This logic is present for more than 10 years.

Do you see anything suspicious when you run the file through ofxdump?
Comment 4 Michael Carpino 2019-06-18 20:02:46 UTC
Nothing appears to be suspicious.  The only difference I see when I look at the 1 that completed and the errored file is NEWFILEUID:, <DTCLIENT>, TRNUID, NEWFILEUID:, STATUS><DTSERVER>.
Comment 5 Bug Janitor Service 2019-07-03 04:33:09 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Thomas Baumgart 2019-07-03 06:16:41 UTC
Oops, did not spot your answer. Sorry.

Strange. Did you ever run the file through 'ofxdump'? Does that reveal any more information?
Comment 7 Michael Carpino 2019-07-03 12:39:40 UTC
Created attachment 121304 [details]
attachment-19924-0.html

NW's.  I was doing some research last night online and there just isn't
much info regarding problems with io-slave issues.

On Wed, Jul 3, 2019 at 12:16 AM Thomas Baumgart <bugzilla_noreply@kde.org>
wrote:

> https://bugs.kde.org/show_bug.cgi?id=408833
>
> --- Comment #6 from Thomas Baumgart <tbaumgart@kde.org> ---
> Oops, did not spot your answer. Sorry.
>
> Strange. Did you ever run the file through 'ofxdump'? Does that reveal any
> more
> information?
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 8 Michael Carpino 2019-07-04 12:43:15 UTC
Created attachment 121318 [details]
io-slave error message

I realized after I posted my comment that there might be a little confusion with it.  The message I'm receiving now is different than my original post.  Somehow the error message has morphed into a "io-slave" error.  I've attached a copy of the screenshot message.
Comment 9 Jack 2019-07-04 15:07:36 UTC
unable to parse and io-slave errors are (I think) totally separate issues.  If the "unable to parse" error is gone, I'd close this bug.  I don't have time to check right now if there are already any open bugs about the io-slave error, but I know it has been discussed, although I don't recall any definitive cause/solution.  Separately - if the original problem was only with the appimage and not the Ubuntu package, I would change the Platform label for the bug.

On the io-slave, since it is specifially complaining about https, what versions of openssh and openssl do you have installed.  Perhaps there is a mismatch of some sort between your versions and the versions used to compile the appimage?
Comment 10 Michael Carpino 2019-07-04 15:58:14 UTC
OpenSSH_7.9p1 Ubuntu-10, OpenSSL 1.1.1b 26 Feb 2019
Comment 11 Bug Janitor Service 2019-07-19 04:33:09 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 12 Bug Janitor Service 2019-08-03 04:33:12 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!