Bugzilla – Bug 975874
GTK3 Breeze application almost unsusable
Last modified: 2016-04-17 09:08:28 UTC
Created attachment 673262 [details] Easytag with GKT3 Theme set to Breeze Applications using GTK3 with the GTK3 theme set to Breeze in the KDE system settings show up almost unusable. Top Menu is like 1 single line Input boxes and buttons don't really show Settings screen is really unclear I will include screenshots for Easytag with Breeze. Starting from the console it gives a wall of GtK-WARNING messages: (easytag:17940): Gtk-WARNING **: Theme parsing error: gtk.css:3932:19: The 'icon-shadow' property has been renamed to '-gtk-icon-shadow' (easytag:17940): Gtk-WARNING **: Theme parsing error: gtk.css:3935:42: The :insensitive pseudo-class is deprecated. Use :disabled instead. (easytag:17940): Gtk-WARNING **: Theme parsing error: gtk.css:3936:46: The :insensitive pseudo-class is deprecated. Use :disabled instead. (easytag:17940): Gtk-WARNING **: Theme parsing error: gtk.css:3937:45: The :insensitive pseudo-class is deprecated. Use :disabled instead. (easytag:17940): Gtk-WARNING **: Theme parsing error: gtk.css:3938:43: The :insensitive pseudo-class is deprecated. Use :disabled instead. (easytag:17940): Gtk-WARNING **: Theme parsing error: gtk.css:4061:17: The 'icon-shadow' property has been renamed to '-gtk-icon-shadow' (easytag:17940): Gtk-WARNING **: Theme parsing error: gtk.css:4069:17: The 'icon-shadow' property has been renamed to '-gtk-icon-shadow' (easytag:17940): Gtk-WARNING **: Theme parsing error: gtk.css:4123:15: The 'icon-shadow' property has been renamed to '-gtk-icon-shadow' (easytag:17940): Gtk-WARNING **: Theme parsing error: gtk.css:4199:15: The 'icon-shadow' property has been renamed to '-gtk-icon-shadow' I am not sure when this exactly started, I don't run that many GTK3 program's but it has looked perfect before. -Alex
Created attachment 673263 [details] Easytag Settings with GKT3 Theme set to Breeze
We know. The GTK3 update to 3.20 broke the breeze theme... For now, please use another GTK3 theme. *** This bug has been marked as a duplicate of bug 975219 ***