Bug 361404 - Breeze GTK - issues with GTK 3.20.2
Summary: Breeze GTK - issues with GTK 3.20.2
Status: RESOLVED DUPLICATE of bug 361066
Alias: None
Product: Breeze
Classification: Plasma
Component: gtk theme (show other bugs)
Version: 5.6.1
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: scionicspectre
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-05 08:20 UTC by Marius Orcsik
Modified: 2016-04-05 13:32 UTC (History)
1 user (show)

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

Attachments
GTK_THEME=Breeze gnome-calculator output (113.47 KB, text/plain)
2016-04-05 08:21 UTC, Marius Orcsik 		Details
GTK_THEME=Breeze:dark gnome-calculator (106.21 KB, text/plain)
2016-04-05 08:22 UTC, Marius Orcsik 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Marius Orcsik 2016-04-05 08:20:57 UTC 
When using the GTK3 Breeze theme in conjunction with GTK3.20.2 the widget styles are completely broken. Probably the same happens with GTK3.20.*

Tested with Firefox and Gnome calculator.

Reproducible: Always

Steps to Reproduce:
1. Install gnome-calculator
2. Execute GTK_THEME=Breeze gnome-calculator in terminal


Actual Results:  
Application has generic controls, but with the correct colours.

Expected Results:  
Application should have the Breeze style controls.
Comment 1 Marius Orcsik 2016-04-05 08:21:46 UTC 
Created attachment 98250 [details]
GTK_THEME=Breeze gnome-calculator output
Comment 2 Marius Orcsik 2016-04-05 08:22:44 UTC 
Created attachment 98251 [details]
GTK_THEME=Breeze:dark gnome-calculator
Comment 3 scionicspectre 2016-04-05 13:23:04 UTC 
This may be a duplicate of https://bugs.kde.org/show_bug.cgi?id=361066, but perhaps we could use this bug to track the resolution of the GTK-warnings instead.
Comment 4 Marius Orcsik 2016-04-05 13:31:24 UTC 
Yeah, sorry. Bugzilla didn't find any previous tickets when I searched.
Comment 5 Rex Dieter 2016-04-05 13:32:20 UTC 
yes, it's a dup

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