Bug 471441 - Dark theme for Windows not working properly
Summary: Dark theme for Windows not working properly
Status: RESOLVED DUPLICATE of bug 471347
Alias: None
Product: okular
Classification: Applications
Component: general (show other bugs)
Version: 23.04.2
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-06-25 16:39 UTC by Ena
Modified: 2023-06-25 16:42 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Buggy dark theme in Okular (29.59 KB, image/png)
2023-06-25 16:39 UTC, Ena
Details
Buggy dark theme in Okular (41.74 KB, image/png)
2023-06-25 16:41 UTC, Ena
Details
Buggy dark theme in Okular (15.62 KB, image/png)
2023-06-25 16:41 UTC, Ena
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ena 2023-06-25 16:39:10 UTC
Created attachment 159892 [details]
Buggy dark theme in Okular

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. Settings
2. Color Scheme 
3. Breeze Dark (Or default if Windows system theme is dark)

OBSERVED RESULT
Provided in attachment.

EXPECTED RESULT
A working dark mode with readable text.

SOFTWARE/OS VERSIONS
Windows: Windows 10 Version 2009 (x86_64)
macOS: -
Linux/KDE Plasma: -
(available in About System)
KDE Plasma Version: -
KDE Frameworks Version: Version 5.107.0
Qt Version: Version 5.15.9 (built against 5.15.9)

ADDITIONAL INFORMATION
It worked fine when I installed Okular recently for the first time, but it's been a couple of days (?) since this bug appeared.
Comment 1 Ena 2023-06-25 16:41:46 UTC
Created attachment 159893 [details]
Buggy dark theme in Okular
Comment 2 Ena 2023-06-25 16:41:58 UTC
Created attachment 159894 [details]
Buggy dark theme in Okular
Comment 3 Nicolas Fella 2023-06-25 16:42:44 UTC

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