Summary: | crash after opening and on saving older kmymoney data file containing custom report | ||
---|---|---|---|
Product: | [Applications] kmymoney | Reporter: | Thomas Bettler <thomas.bettler> |
Component: | general | Assignee: | KMyMoney Devel Mailing List <kmymoney-devel> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | j.r.hudson, neo2geon, tbaumgart |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
Konsole output from opening file and then closing
Console output from opening, adding a payee, adding a transaction and closing |
Description
Thomas Bettler
2010-01-06 21:17:31 UTC
Can you send us the output of the following command: zgrep charttype your-kmymoney-file-name-here or in case you use GPG encryption: gpg -d your-kmymoney-file-name-here | grep charttype The problem you reported is somehow linked to a chart type which is out of bounds (frames #12-#14 of your backtrace) output as requested: <REPORTS count="1"> <REPORT includesprice="0" includesactuals="0" columnsaredays="0" includestransfers="0" loans="0" id="R000001" comment="Custom Report" columntype="months" rowtype="expenseincome" name="Income and Expenses Last Month (Customized)" chartgridlines="1" includesaverageprice="0" includesmovingaverage="0" chartbydefault="0" datelock="lastmonth" investments="0" charttype="none" favorite="1" showrowtotals="1" chartdatalabels="1" convertcurrency="1" chartlinewidth="2" detail="all" includeschedules="0" tax="0" group="Income and Expenses" includesforecast="0" includeunused="0" type="pivottable 1.15"> <ACCOUNTGROUP group="expense"/> <ACCOUNTGROUP group="income"/> </REPORT> </REPORTS> The charttype is none, which shouldn't happen in this case. Weird thing is, reports are not loaded on startup, so it shouldn't crash. Can you try starting with kmymoney -n and then disabling all components in the Home Page (Go to Configure KMyMoney -> Home) Can you confirm if this still happens with the latest SVN? Sorry for not being able to respond for this time. My system is currently down while waiting for migration, but the new hardware hasn't arrived yet. I will be able to respond in a few weeks. Sorry for having to wait until then. This is just a reminder. Did you have a chance to see if it still fails with a current SVN version? KDE4.3.5 KMyMoney 3.97.2 OpenSUSE After entering bug 235880 re automatic entry of scheduled transactions, I tried to re-open KMyMoney and it froze twice at 'Loading reports.' I have plenty of custom reports but it did not freeze after I installed it last night, only after the first transactions had been entered this morning. SVN commit 1121414 by tbaumgart: Avoid crash in case of a weird chart type setting. Please start the application from the console and monitor the output while running this version against a file that caused the crash for the first time. I am interested in the console output during read and write operations. BUG: 221572 M +8 -3 mymoneyreport.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1121414 Created attachment 43182 [details]
Konsole output from opening file and then closing
Created attachment 43183 [details]
Console output from opening, adding a payee, adding a transaction and closing
Does it still fail? I don't see any of the debug messages I put into the latest SVN which should trigger in case of problems. Can you comment on the behavior of the application (crash/lockup/etc) while creating those two console traces a bit? TIA. No, KMyMoney did not fail in any way on these two occasions when I used a copy of the accounts file I had backed up on a different computer. The behaviour was completely different from when I ran it on my main computer with the original file. The only thing I did not do this time was try to open a custom report on the backup computer. In theory both computers are running exactly the same versions of openSUSE and KDE though my backup has fewer programs installed; so there may have been a conflict with something else on my main computer which is not present on the backup. *** Bug 303558 has been marked as a duplicate of this bug. *** |