I get this warning since ~ 2 weeks doing a “zypper dup” about every 5 days.
(gvim:3524): Gtk-WARNING **: 07:40:48.503: Theme parsing error: gtk.css:1649:16: '-gtk-icon-size' is not a valid property name
I see this when I start things from the command line and apart from this warning nothing is wrong as far as I can see. Multiple applications trigger this warning, when I start gvim it prints out this message 4 times, when I start Firefox only two times.
$ find / -name gtk.css 2> /dev/null
/home/user/.config/gtk-3.0/gtk.css
/home/user/.config/gtk-4.0/gtk.css
/usr/share/themes/Breeze/gtk-3.0/gtk.css
/usr/share/themes/Breeze/gtk-4.0/gtk.css
/usr/share/themes/Breeze-Dark/gtk-3.0/gtk.css
/usr/share/themes/Breeze-Dark/gtk-4.0/gtk.css
/usr/share/themes/Adwaita/gtk-3.0/gtk.css
/usr/share/themes/Adwaita-dark/gtk-3.0/gtk.css
So multiple gtk.css files but based on the line number I can say the problem is originating in /usr/share/themes/Breeze-Dark/gtk-3.0/gtk.css as that has “-gtk-icon-size: 16px” on line 1659 but I see in in 4 files:
/usr/share/themes/Breeze/gtk-3.0/gtk.css
1649: -gtk-icon-size: 16px; }
1652: -gtk-icon-size: 32px; }
/usr/share/themes/Breeze/gtk-4.0/gtk.css
1595: -gtk-icon-size: 16px; }
1598: -gtk-icon-size: 32px; }
1601: -gtk-icon-size: 128px; }
3834: -gtk-icon-size: 24px;
/usr/share/themes/Breeze-Dark/gtk-3.0/gtk.css
1649: -gtk-icon-size: 16px; }
1652: -gtk-icon-size: 32px; }
/usr/share/themes/Breeze-Dark/gtk-4.0/gtk.css
1595: -gtk-icon-size: 16px; }
1598: -gtk-icon-size: 32px; }
1601: -gtk-icon-size: 128px; }
3834: -gtk-icon-size: 24px;
I am running KDE and never played with GTK themes but looks like these application somehow use GTK themes. I found GTK on the ArchLinux wiki and based on that I tried:
$ GTK_THEME=Adwaita:dark gvim
That works and gvim get a dark header.
$ sudo rpm -q --whatprovides /usr/share/themes/Breeze-Dark/gtk-3.0/gtk.css
gtk3-metatheme-breeze-5.27.4-2.1.noarch
Clear, I tried “zypper remove” for this (and the gtk4 variant) and saw there were no dependencies so went ahead. After that the problem is gone.
So problem gone, but some questions:
- Good idea to post this although the problem is gone?
- Would you have done something different?