Bug 506629 - Kmymoney crashed when importing .qif file
Summary: Kmymoney crashed when importing .qif file
Status: RESOLVED DUPLICATE of bug 506667
Alias: None
Product: kmymoney
Classification: Applications
Component: reports (other bugs)
Version First Reported In: 5.2.0
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-07-05 12:01 UTC by Anthony
Modified: 2025-07-06 14:10 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
.kmy and .qif file (1.78 KB, application/gzip)
2025-07-06 09:34 UTC, Anthony
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Anthony 2025-07-05 12:01:46 UTC
When i import a .qif file, kmymoney crushed with this message : Core dumped. With the last version of kmymoney (5.1), i never have this problem.


***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Please remove this comment after reading and before submitting - thanks!
***

SUMMARY


STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 6.4.1
KDE Plasma Version: 6.4.1
KDE Frameworks Version: 6.15.0
Qt Version: 6.9.1

ADDITIONAL INFORMATION
Comment 1 Thomas Baumgart 2025-07-06 08:39:55 UTC
The information so far is a bit vague. Can you provide a sample .KMY and .QIF file so that the problem becomes reproducable?
Comment 2 Anthony 2025-07-06 09:34:53 UTC
Created attachment 183000 [details]
.kmy and .qif file

Please find in attachment .kmy and .qif file
Comment 3 Thomas Baumgart 2025-07-06 14:10:12 UTC
Thank you very much for providing the sample files. By looking at the QIF file, it seems that the problem is a duplicate of bug #506667 which was just fixed. I was able to successfully process the files you provided.

*** This bug has been marked as a duplicate of bug 506667 ***