Bug 491145

Summary: Home Page and Reports not showing data
Product: [Applications] kmymoney Reporter: Richard Harries <r.harries>
Component: ux-uiAssignee: KMyMoney Devel Mailing List <kmymoney-devel>
Status: REPORTED ---    
Severity: normal    
Priority: NOR    
Version: 5.1.3   
Target Milestone: ---   
Platform: macOS (DMG)   
OS: macOS   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Richard Harries 2024-08-01 22:00:40 UTC
***
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
***

SUMMARY
Normally there is a table of Assets/Liabilities on the home page.  These are not showing.  Similarly, in the reports section, I can see charts but not reports.

SOFTWARE/OS VERSIONS
macOS:  5.1.3
Comment 1 Jack 2024-08-02 00:14:08 UTC
I was going to close this as a duplicate of Bug 468936, but that one got closed as WORKSFORME because the OP didn't respond to questions about details of their setup.  Basically, the "missing" sections are rendered using HTML, so the problem is figuring why that is the case.  I thought there had been a solution, but will need to do some further research to find that information.

However, if this problem just started for you, is this a new installation of KMyMoney, or else what has recently changed or been upgraded?

In the meantime, I did find one post suggesting that something had changed either in the rendering or the package building, so it would be good if you could at least try using the development version, built from master branch, rather than either the stable 5.1.3 or even git head of the 5.1 git branch.
Comment 2 Richard Harries 2024-08-02 09:40:09 UTC
Hi Jack.

Thanks for responding so quickly.  I did see the previous bug report had been closed without resolution.  I also suspected it must be some sort of rendering error, since everything else is working perfectly.  I'll try using the development version and report back.
Comment 3 Richard Harries 2024-08-04 09:58:28 UTC
Okay, I tested out the development version and that did correct the display problems HOWEVER it also threw up two new issues.

1. It said the data file failed the consistency tests for some old entries.  This has never occurred with previous versions.
2. It 'forgot' my Favourite, customised reports.

So, I'm going to stick with 5.1.2 stable for the time being.
Comment 4 Jack 2024-08-04 14:52:53 UTC
Over the years, many new checks have been added to the consistency test, so new issues showing up is not a surprise.  Please say what types of messages you get and we can suggest how to resolve them.
When you say it forgot  some reports, did it just no longer mark some reports as favorites, or did it seem to actually forget the report?  In the latter case, if you Save As with the new version (be sure to keep a copy of the original data file) is the report now missing if you open that new file with the old version of the program?  I want to be sure there isn't something in the old report which the new program fails to read correctly.
Comment 5 Thomas Baumgart 2024-08-11 07:59:23 UTC
I would very much appreciate some feedback and details on the "disappearing favorite reports".
Comment 6 Richard Harries 2024-08-11 15:28:58 UTC
(In reply to Thomas Baumgart from comment #5)
> I would very much appreciate some feedback and details on the "disappearing
> favorite reports".

Sorry for the delay replying.  On the consistency checks, it really seemed to mess with my .kmy file, reducing it from ~960KB to 306KB.  On the reports, it just dropped the entire section 11, Favorite Reports, which has around 20 or so custom reports I have built up over the years.
Comment 7 Richard Harries 2024-08-11 15:31:06 UTC
Here is an extract from the tail end of the consistency check, all but the last related to "Sum of splits in transaction":

    Account: Asset:Child Trust Fund ([name deleted]), Amount: £ 396.69
  * Sum of splits in transaction 'T000000000000006459' posted on 25/05/2011 is not zero.
    Account: Asset:Child Trust Fund ([name deleted]), Amount: £ 567.90
  * Sum of splits in transaction 'T000000000000006996' posted on 18/11/2011 is not zero.
    Account: Asset:Child Trust Fund ([name deleted]), Amount: £ -33.50
  * Sum of splits in transaction 'T000000000000007003' posted on 23/11/2011 is not zero.
    Account: Asset:Child Trust Fund ([name deleted]), Amount: £ -384.73
  * Sum of splits in transaction 'T000000000000007568' posted on 25/05/2012 is not zero.
    Account: Asset:Child Trust Fund ([name deleted]), Amount: £ -293.16
  * Sum of splits in transaction 'T000000000000008160' posted on 19/11/2012 is not zero.
    Account: Asset:Child Trust Fund ([name deleted]), Amount: £ 78.84
  * Sum of splits in transaction 'T000000000000008169' posted on 22/11/2012 is not zero.
    Account: Asset:Child Trust Fund ([name deleted]), Amount: £ 962.85
* Potential problem with securities/currencies
  * The account 'FD Current' in currency 'British Pound' has no price set for the date of its first usage on '01/01/2005'.
    Please enter a price for the currency on or before '01/01/2005'.

Finished: 0 problems corrected. 262 problems still present.
Comment 8 Thomas Baumgart 2024-08-11 16:34:42 UTC
> ...  it really seemed to mess with my .kmy file, reducing it from ~960KB to 306KB

That does not sound right. What is the exact version of your failing KMyMoney application (see Help/About KMyMoney). As example, mine currently says "5.1.80-30e479294".
Comment 9 Richard Harries 2024-08-11 17:10:46 UTC
(In reply to Thomas Baumgart from comment #8)
> > ...  it really seemed to mess with my .kmy file, reducing it from ~960KB to 306KB
> 
> That does not sound right. What is the exact version of your failing
> KMyMoney application (see Help/About KMyMoney). As example, mine currently
> says "5.1.80-30e479294".

It's 5.1.80-7f2c37e
Comment 10 Thomas Baumgart 2024-08-11 18:26:57 UTC
Thanks. This commit is dated Mar 12, 2024. On May 17, 2024 we added this commit: https://invent.kde.org/office/kmymoney/-/commit/b2067be54 which solves a problem with invalid XML in the file. I expect this to be the case for the trouble you experience with the shortened file. The current build of the MacOS version on the KDE CI/CD system still seems to be broken. I set the status of this bug entry back to REPORTED so that you can check once we are able to see a newer version.
Comment 11 Richard Harries 2024-08-12 07:43:12 UTC
(In reply to Thomas Baumgart from comment #10)
> Thanks. This commit is dated Mar 12, 2024. On May 17, 2024 we added this
> commit: https://invent.kde.org/office/kmymoney/-/commit/b2067be54 which
> solves a problem with invalid XML in the file. I expect this to be the case
> for the trouble you experience with the shortened file. The current build of
> the MacOS version on the KDE CI/CD system still seems to be broken. I set
> the status of this bug entry back to REPORTED so that you can check once we
> are able to see a newer version.

Thanks. R.