Bug 399422 - kmymoney Crash when importing OFX file
Summary: kmymoney Crash when importing OFX file
Status: RESOLVED FIXED
Alias: None
Product: kmymoney
Classification: Applications
Component: general (show other bugs)
Version: 5.0.0
Platform: RedHat Enterprise Linux Linux
: NOR major
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-10-05 21:55 UTC by Thierry
Modified: 2019-01-19 12:03 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thierry 2018-10-05 21:55:23 UTC
Kmymoney is normaly open..
kmymoney
WebConnect: Starting server failed. Try to remove stale socket.
WebConnect: Running in server mode
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile

some color defects but it does not matter
if i'm importing a ofx file :

LibOFX INFO: libofx_proc_file(): File format not specified, autodetecting...
(Above message occured on Line 18446744073709551615, Column 18446744073709551615)
LibOFX INFO: libofx_proc_file(): Detected file format: OFX (Open Financial eXchange (OFX or QFX))
(Above message occured on Line 18446744073709551615, Column 18446744073709551615)
/usr/include/c++/8/bits/basic_string.h:1048: std::__cxx11::basic_string<_CharT, _Traits, _Alloc>::reference std::__cxx11::basic_string<_CharT, _Traits, _Alloc>::operator[](std::__cxx11::basic_string<_CharT, _Traits, _Alloc>::size_type) [with _CharT = char; _Traits = std::char_traits<char>; _Alloc = std::allocator<char>; std::__cxx11::basic_string<_CharT, _Traits, _Alloc>::reference = char&; std::__cxx11::basic_string<_CharT, _Traits, _Alloc>::size_type = long unsigned int]: Assertion '__pos <= size()' failed.
Aborted (core dumped)

it's systematic


SOFTWARE VERSIONS 5.00
(available in About System)
Kernel: 4.18.10-200.fc28.x86_64 x86_64 bits: 64 Desktop: KDE Plasma 5.13.4
Comment 1 Thomas Baumgart 2019-01-19 11:03:13 UTC
Does the problem still persist with version 5.0.2?
Comment 2 Thierry 2019-01-19 12:03:28 UTC
Hi; No it's perfect now. It resolved.