Bug 503242

Summary: Transaction Entry Screen Frame Totally Black
Product: [Applications] kmymoney Reporter: Gary C Bellaire <step12dude>
Component: generalAssignee: KMyMoney Devel Mailing List <kmymoney-devel>
Status: RESOLVED DUPLICATE    
Severity: minor CC: step12dude
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Appimage   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Gary C Bellaire 2025-04-23 16:47:26 UTC 
SUMMARY
Using recent development builds (currently 4275) the transaction entry screen, which used to have a blue border and where the field labels were present, is now entirely black and the field labels are unreadable

STEPS TO REPRODUCE
1.   Download development version (currently 4275) applimage file and run it
2.   Select an account and attempt to add a transaction using the transaction entry screen
3.   Transaction entry screen is entirely black with white fields instead of blue and visible field labels

OBSERVED RESULT
Unless the user is experienced with the application and knows from prior experience which field is what on the transaction entry screen, the screen is not usable.  

EXPECTED RESULT
Transaction entry screen should be readable with labels present

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma:   Development build (applimage) #4275.  Noticed in other recent builds as well.
KDE Plasma Version:   6.3.4
KDE Frameworks Version:  6.13.0
Qt Version:  6.9.0

ADDITIONAL INFORMATION
Not a major issue - but something that would appear to be easily fixable
Comment 1 Gary C Bellaire 2025-04-23 16:49:15 UTC 
Suggestion - on the download screen for development builds, provide access to not just the most current build but other recent builds, so that if an issue is encountered, one can easily roll back to a prior build.
Comment 2 Thomas Baumgart 2025-04-24 05:59:02 UTC 
Regarding your suggestions: sorry, but the KMyMoney project does not have any influence on that as the whole appimage build service and the storage location is provided by KDE. OTOH, each version has a different number and you can keep them on your local system too.

*** This bug has been marked as a duplicate of bug 503095 ***