Summary: | CSV File Import | ||
---|---|---|---|
Product: | [Applications] kmymoney | Reporter: | JKHU <XI_publici_II> |
Component: | general | Assignee: | KMyMoney Devel Mailing List <kmymoney-devel> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | crash | CC: | agander93, onet.cristian |
Priority: | NOR | ||
Version: | 4.6.1 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
JKHU
2013-01-11 21:05:30 UTC
Unfortunately, the backtrace does not look very helpful, at least not to me, except the indication from the other possible duplicates that the problem may be external to KMyMoney. So, we need more information. Firstly, can you indicate the steps you take leading up to the crash. Next, is there a possibility you can supply the input CSV file, if you wish directly to me, and with sensitive data disguised (AAAAA for alpha characters in bank details, NNNN for numeric), provided the structure stays intact and the file still results in a crash. Then, much has happened since 4.6.1. Could you possibly install the latest stable release, 4.6.3, from Claydoh's PPA. Since you can reproduce the crash every time, please follow the guide[1] and provide a better backtrace. [1] http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_when_an_uncaught_exception_is_causing_a_crash We need a stack trace with debug information installed. |