Bug 353071 - User defined color schemes only work for qt5
Summary: User defined color schemes only work for qt5
Status: RESOLVED FIXED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_colors (show other bugs)
Version: 5.4.1
Platform: Debian unstable Linux
: NOR normal
Target Milestone: ---
Assignee: Matthew Woehlke
URL:
Keywords:
: 343146 354618 371866 372520 375678 (view as bug list)
Depends on:
Blocks:
 
Reported: 2015-09-23 06:57 UTC by Salvo "LtWorf" Tomaselli
Modified: 2020-01-15 18:20 UTC (History)
7 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Salvo "LtWorf" Tomaselli 2015-09-23 06:57:24 UTC
I am trying to define a custom color scheme, by selecting an existing one and changing some of its colors, in the tab called "colors".

However, after I change them and hit "apply", only qt5 applications are affected. Everything else (qt4, gtk2) will stick to the previous color scheme selected, among the default ones.

I have tryied saving my custom color scheme and selecting it, but it still only works on qt5 programs.

Reproducible: Always

Steps to Reproduce:
1. Select a dark color scheme (such as dark breeze)
2. Apply
3. Now select a white color scheme
4. Now change the white background for text boxes into a light gray
5. Apply

Actual Results:  
Only qt5 applications will follow the new scheme, everything else will be stuck with the dark scheme.

Expected Results:  
Everything to follow the scheme
Comment 1 Nate Graham 2020-01-15 16:18:41 UTC
This is fixed now for GTK apps, and no longer relevant for Qt 4 apps.
Comment 2 Nate Graham 2020-01-15 16:23:01 UTC
*** Bug 354618 has been marked as a duplicate of this bug. ***
Comment 3 Nate Graham 2020-01-15 16:23:32 UTC
*** Bug 372520 has been marked as a duplicate of this bug. ***
Comment 4 Nate Graham 2020-01-15 16:23:41 UTC
*** Bug 371866 has been marked as a duplicate of this bug. ***
Comment 5 Nate Graham 2020-01-15 18:20:30 UTC
*** Bug 343146 has been marked as a duplicate of this bug. ***
Comment 6 Nate Graham 2020-01-15 18:20:39 UTC
*** Bug 375678 has been marked as a duplicate of this bug. ***