Bug 455607 - Enable a Konsole color scheme to automatically use the system accent color in the terminal background/font itself
Summary: Enable a Konsole color scheme to automatically use the system accent color in...
Status: CONFIRMED
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: 22.04.2
Platform: Arch Linux Linux
: NOR wishlist
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
: 497201 (view as bug list)
Depends on:
Blocks:
 
Reported: 2022-06-19 12:22 UTC by Felix Fischer
Modified: 2024-12-19 07:11 UTC (History)
5 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Felix Fischer 2022-06-19 12:22:11 UTC
SUMMARY
Currently system color schemes and konsole color schemes are completely independent. This worked fine for me until plasma 5.25 and the introduction of tinted color schemes. Since my wallpaper changes periodically, my color scheme also gets updated, but konsole obviously stays the same.
This means my window decorations and window borders are now a different color from the actual terminal background.
It would be nice if there was an option to set the terminal background to the standard BackgroundNormal color that all other apps also use (i.e. Dolphin, System Settings).


STEPS TO REPRODUCE
1. enable System Settings > Appearance > Colours > Use accent colour from current wallpaper
2. edit a colour scheme and toggle Options > Tint all colours with accent colour, apply
3. open Konsole and change the wallpaper 

OBSERVED RESULT
background colour of konsole stays the same while window decorationand borders (if enabled) change colour according to the wallpaper

EXPECTED RESULT
Konsole follows system wide colours

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux stable
(available in About System)
KDE Plasma Version: 5.25.0
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.5
Comment 1 John Kizer 2024-12-19 07:11:52 UTC
*** Bug 497201 has been marked as a duplicate of this bug. ***