Bug 392703 - crash importing directly from firefox, no crash importing from file menu
Summary: crash importing directly from firefox, no crash importing from file menu
Status: RESOLVED FIXED
Alias: None
Product: kmymoney
Classification: Applications
Component: importer (show other bugs)
Version: 5.0.1
Platform: Mageia RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Thomas Baumgart
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-04-04 09:41 UTC by José JORGE
Modified: 2019-01-20 14:36 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
anonymised ofx file that triggers the bug (7.22 KB, text/plain)
2018-04-05 10:28 UTC, José JORGE
Details

Note You need to log in before you can comment on or make changes to this bug.
Description José JORGE 2018-04-04 09:41:11 UTC
I have associated kmymoney with ofx files in firefox. With version 4.x I had no problem with this. Now with kmymoney 5.0.1, it crashes at the end of the import, after the resume screen saying import was done with success.

If instead I open the ofx file from the menu import ofx, I get no crash.
Comment 1 Thomas Baumgart 2018-04-04 12:20:08 UTC
Can you provide a sample file (without personal data) that causes the crash to happen? Also, can you provide a backtrace of the crash?
Comment 2 José JORGE 2018-04-04 18:46:24 UTC
(In reply to Thomas Baumgart from comment #1)
> Can you provide a sample file (without personal data) that causes the crash
> to happen? Also, can you provide a backtrace of the crash?

I think the file is not the problem, as I have no segfault if I open it from the file import menu...

Well, it did not segfault when I tried to xdg-open the ofxfile under gdb the first 2 tries, but the third segfaulted :

(gdb) backtrace
#0  0x00007ffff19002f4 in QMetaObject::activate(QObject*, int, int, void**) () from /lib64/libQt5Core.so.5
#1  0x00007ffff18040b1 in QIODevice::channelReadyRead(int) () from /lib64/libQt5Core.so.5
#2  0x00007ffff1c8525c in QAbstractSocketPrivate::canReadNotification() () from /lib64/libQt5Network.so.5
#3  0x00007ffff1c94fc1 in QReadNotifier::event(QEvent*) () from /lib64/libQt5Network.so.5
#4  0x00007ffff23b951c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5
#5  0x00007ffff23c09c7 in QApplication::notify(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5
#6  0x00007ffff18d5c68 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5
#7  0x00007ffff19293cd in socketNotifierSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5
#8  0x00007fffe7867ac7 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#9  0x00007fffe7867cf8 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0
#10 0x00007fffe7867d9c in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#11 0x00007ffff1928776 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
   from /lib64/libQt5Core.so.5
#12 0x00007ffff18d3e0a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#13 0x00007ffff18dc9c8 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5
#14 0x0000000000471182 in runKMyMoney(QApplication&, std::unique_ptr<QSplashScreen, std::default_delete<QSplashScreen> >, QUrl const&, bool) ()
#15 0x000000000046fc5e in main ()

Is this enough?
Comment 3 Thomas Baumgart 2018-04-05 09:49:01 UTC
Not really. I was asking for (the/a) file to duplicate the problem myself. I know, that the contents is not the problem and that it rather seems to be the method.
Comment 4 José JORGE 2018-04-05 10:28:50 UTC
Created attachment 111840 [details]
anonymised ofx file that triggers the bug

I can trigger the bug opening this file with xdg-open
Comment 5 Jonatan Cloutier 2018-05-06 20:32:06 UTC
I get this problem as well, just to add precision on when it happens. I found out that it does crash when opening directly from Firefox and kmymoney is already running. When kmymoney is lunched from the Firefox download the import complete successfully.
Comment 6 Thomas Baumgart 2019-01-20 12:33:02 UTC
Does this still happen with newer versions of the project? You might want to try a recent AppImage file if your distro does not have a newer version available.
Comment 7 José JORGE 2019-01-20 14:36:42 UTC
(In reply to Thomas Baumgart from comment #6)
> Does this still happen with newer versions of the project? You might want to
> try a recent AppImage file if your distro does not have a newer version
> available.

Fixed with 5.0.2 version in my Mageia distro, thanks.