*** 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 Please remove this comment after reading and before submitting - thanks! *** SUMMARY Home Screen is BLANK when opening in Fedora 41 KDE. STEPS TO REPRODUCE 1. Install Kmymoney 5.1.3 through Discover, or through DNF, or even Kmymoney 5.1.0 through Flathub (same result) 2. Create new file, or load file 3. Home page loads as BLANK OBSERVED RESULT Home page loads as BLANK no matter I do. Other pages works just fine. EXPECTED RESULT Home page should be loaded with Assets/Liabilities, etc... many items on the Home Page. SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: KDE Plasma Version: 6.2.4 KDE Frameworks Version: 6.8.0 Qt Version: 6.8.0 Graphics Platform: Wayland ADDITIONAL INFORMATION It worked fine on Kubuntu 22.04.
Created attachment 176233 [details] Screenshot Screenshot of home page being BLANK
*** This bug has been marked as a duplicate of bug 491494 ***
Not sure this is relevant but I'll share it just in case. While it took me a while to get KMM to run on Fedora 40 (mostly a pinentry issue), I have not had any problems with Fedora 41. I have not tried the version provided by Fedora. I have compiled both 5.1 and the master branches successfully on 4 different systems. I have scripts that make it easy to compile either branch so I can always run the latest code.
One observation and perhaps a good news is something I tried - I booted up the liveCD, installed KMyMoney from the repository, and it all worked, home page appeared correctly. Not sure then if this would help lead to any clues as to what may be contributing to this bug.
It's ok to add a comment to a bug closed as a duplicate, but please do not reopen it unless you are claiming it is really not a duplicate. Otherwise, all further comments should be made on the other bug (yes, I see you made the same comment there.) Thanks. *** This bug has been marked as a duplicate of bug 491494 ***