SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Reinstall macOS from scratch 2. Retrieve KMymoney file from backup 3. Begin using (all previous transactions are present) 4. Download Kmymoney.dmg and install. OBSERVED RESULT Text based reports are gray with no information. Charts seem to work normally. Ledger is accurate. EXPECTED RESULT Text based reports should show columns/data/totals like they did before the system and application reinstall. SOFTWARE/OS VERSIONS macOS: Ventura 13.6 ADDITIONAL INFORMATION
I don't have a mac to test, but my guess is that the reports are being calculated correctly, but there is a problem with the display. If you export a report, does the data look OK? Have you made any changes to default text, colors, and/or themes? One question about your steps to reproduce: You say begin using as step 3, but what version of KMM are you using there, if step 4 is to download and install KMyMoney? Not likely, but I want to be sure there isn't some conflict between two different installs of the program.
Exporting the gray report yields accurate information in a .csv file. What settings do I need to change to actually see the report. Colors settings seem to have no effect.
Exporting the gray report does yield what looks to be accurate information in the .csv file. What settings could I have changed that influences the Report display? KMM colors settings do not appear to influence the Report display.
Reports are presented using HTML, but the Home page is also rendered with HTML and you don't report any problems there. If you display a report, and try selecting some text (mouse click and hold, then move mouse across the report) does anything show up? If you can see the text, it is a problem of the same color text and background. If not, I have no answer. I don't think there are any settings to directly control report presentation. You could manually edit the css, but I doubt that is actually recommended. (There are two css files installed along with KMyMoney, but I have no idea where they would be put on macOS.) Which version of the dmg file are you using? It seems 1840 is the last successful build, so we do need to figure out why the builds have been failing for a month and a half. You might try the nightly builds (which are built from master branch instead of the 5.1 branch) but if you do, be sure to have a good backup of your data file.
from Jack - Reports are presented using HTML, but the Home page is also rendered with HTML and you don't report any problems there. theUser - The Home page is also gray. theUser - if I click the Copy button on the generated report page I do get text so it is easy to agree that this is a text/background same color issue. I also get data on exporting the report. theUser - KMM version is 5.1.3-33a66be8a
Exporting to csv is totally unrelated to HTML, so that just confirms the report is extracting the data correctly. They same gray on the Home Page and Reports confirms it is an HTML display issue. Unfortunately, I haven't seen any actual solution in any of the related posts and bugs about what looks like the same issue. I don't really know what to suggest, but if you can find a dmg for the KDE System Settings application, you can try changing the theme or font colors to see if it has any effect.
The nightly build, kmymoney-master-2045-macos-clang-x86_64.dmg. does not have the issue that the kmymoney-5.1-1840-macos-clang-x86_64.dmg build had.
theUser - I tested for the influence of macOS Dark Mode vs Light Mode on both versions and it has no influence. One last thing, when bringing up the actual report in the 1840 version it does flash a white background first then covers it with a gray background so perhaps there are 2 paints going on in succession?
*** Bug 474877 has been marked as a duplicate of this bug. ***
This is still an issue. Is there a fix in sight?
If build 2045 works, what else is actually needed? The main problem with creating a real fix is that we don't know exactly what the cause of the problem is. In addition, I don't think any of the developers use macOS, so any attempted fix needs to be made, and then can only be tested after the commit is included in the next successful macOS build. Unfortunately, as far as I know, the KDE builds for x86_64 are not currently functional, so unless someone steps up to help restore that process, there is not much that can be done. (see https://kmymoney.org/macos.html for that info.)
This also occurs on the Mac mini M1 ARM version.
The development arm version fixes the issue: https://cdn.kde.org/ci-builds/office/kmymoney/master/macos-arm64/kmymoney-master-3139-macos-clang-arm64.dmg
I'm not sure if anything was explicitly done about this, but I wonder if we should close it as fixed in 5.2?
As reported in comment 13 this is fixed in the 5.2 development code base