Bug 494638 - Problems with dark theme when choosing custom font
Summary: Problems with dark theme when choosing custom font
Status: RESOLVED DUPLICATE of bug 487387
Alias: None
Product: plasmashell
Classification: Plasma
Component: Digital Clock widget (other bugs)
Version First Reported In: 6.2.3
Platform: Kubuntu Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-10-13 07:19 UTC by Johnny Wezel
Modified: 2024-12-26 15:59 UTC (History)
2 users (show)

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


Attachments
Screenshot (46.36 KB, image/png)
2024-10-13 07:19 UTC, Johnny Wezel
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Johnny Wezel 2024-10-13 07:19:39 UTC
Created attachment 174760 [details]
Screenshot

SUMMARY

Problems with dark mode when selecting a custom font.

STEPS TO REPRODUCE
1. In Appearance click Manual [Choose Style]

OBSERVED RESULT

White on white GUI elements

EXPECTED RESULT

White on black GUI elements

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 6.11.0-8-generic #8-Ubuntu SMP PREEMPT_DYNAMIC x86_64
KDE Plasma Version: 6.1.5
KDE Frameworks Version: 6.6.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION
OS: Kubuntu oracular 24.10 x86_64
Host: Amd Wrx80
Display (LC24RG50): 1920x1080 @ 144 Hz in 24" [External]
WM: KWin (X11)
WM Theme: Breeze
Theme: Breeze (Dark) [Qt], Breeze-Dark [GTK2], Breeze [GTK3/4]
Icons: breeze [Qt], breeze [GTK2/3/4]
Comment 1 Nate Graham 2024-11-21 22:41:50 UTC
In some cases, the data license requires this. In all the other cases, it's just polite to acknowledge those whose shoulders you're standing on.
Comment 2 Sam Birch 2024-12-26 15:59:01 UTC
(In reply to Nate Graham from comment #1)
> In some cases, the data license requires this. In all the other cases, it's
> just polite to acknowledge those whose shoulders you're standing on.

I think this bug is about widget styling, not font attribution.

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