Bug 414108 - Combobox texts not readable in GIMP with Breeze (Bright)
Summary: Combobox texts not readable in GIMP with Breeze (Bright)
Status: RESOLVED DUPLICATE of bug 412331
Alias: None
Product: Breeze
Classification: Plasma
Component: gtk theme (show other bugs)
Version: 5.17.3
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Janet Blackquill
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-11-13 20:25 UTC by postix
Modified: 2019-11-28 04:24 UTC (History)
2 users (show)

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


Attachments
Screenshot of the issue. One combobox is extended (clicked), the others are not. (110.88 KB, image/png)
2019-11-13 20:25 UTC, postix
Details
Breeze Dark for GTK2/3 looks fine. (105.41 KB, image/png)
2019-11-13 20:29 UTC, postix
Details

Note You need to log in before you can comment on or make changes to this bug.
Description postix 2019-11-13 20:25:03 UTC
Created attachment 123907 [details]
Screenshot of the issue. One combobox is extended (clicked), the others are not.

SUMMARY

I chose Breeze for both GTK2.0 and 3.0 theme and unchecked "preferred dark (gtk) theme". However GIMP stays being dark and that's already an issue.
However, this issue is about unclicked comboboxes, which are are bright with a white text on it and therefore not readable at all.

See screenshot.

STEPS TO REPRODUCE
1. Breeze theme for GTK 2.0/3.0
3. Unchecked "Prefer dark theme"
2. Open GIMP

SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux 
KDE Plasma Version: 5.17.3
KDE Frameworks Version: 5.65.0
Qt Version: 5.13.2


ADDITIONAL INFORMATION

I already tried to reinstalled GIMP and to delete the local configuration at .config/GIMP.
Comment 1 postix 2019-11-13 20:29:12 UTC
Created attachment 123908 [details]
Breeze Dark for GTK2/3 looks fine.

With Breeze dark for GTK2/3 it looks fine. However, I don't want to use Breeze dark for all GTK apps just because of GIMP.
Comment 2 Nate Graham 2019-11-28 04:24:09 UTC
Looks like the same underlying issue as Bug 412331.

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