Menu
▾
▴
#694 lxappearance-0.5.6 Wrong settings for .config/gtk-3.0?
I'm running Slackware 14.1 x86_64 with gtk+3-3.8.2.
I'm not sure if this is a bug, or there have been changes that have created this?
In lxappearance-0.5.5 for .config/gtk-3.0/settings.ini many of the settings use to be 1, which have now been replaced in 0.5.6 as true...
Having the true settings in 0.5.6 for some applications I now get these messages;
(transmission-gtk:18268): Gtk-WARNING **: Error setting gtk-xft-antialias in /home/foo/.config/gtk-3.0/settings.ini: Key file contains key 'gtk-xft-antialias' in group 'Settings' which has a value that cannot be interpreted.
(transmission-gtk:18268): Gtk-WARNING **: Error setting gtk-xft-hinting in /home/foo/.config/gtk-3.0/settings.ini: Key file contains key 'gtk-xft-hinting' in group 'Settings' which has a value that cannot be interpreted.
Below are how the settings.ini look for each version.
lxappearance-0.5.5 settings
[Settings]
gtk-theme-name=Numix
gtk-icon-theme-name=livarp_icons
gtk-font-name=Aller 9
gtk-cursor-theme-name=Pulse-Glass
gtk-cursor-theme-size=0
gtk-toolbar-style=GTK_TOOLBAR_ICONS
gtk-toolbar-icon-size=GTK_ICON_SIZE_LARGE_TOOLBAR
gtk-button-images=0
gtk-menu-images=0
gtk-enable-event-sounds=1
gtk-enable-input-feedback-sounds=1
gtk-xft-antialias=1
gtk-xft-hinting=1
gtk-xft-hintstyle=hintfull
gtk-xft-rgba=rgb
lxappearance-0.5.6 settings
[Settings]
gtk-theme-name=MediterraneanTributeDark
gtk-icon-theme-name=livarp_icons
gtk-font-name=Aller 9
gtk-cursor-theme-name=Pulse-Glass
gtk-cursor-theme-size=0
gtk-toolbar-style=GTK_TOOLBAR_ICONS
gtk-toolbar-icon-size=GTK_ICON_SIZE_LARGE_TOOLBAR
gtk-button-images=false
gtk-menu-images=false
gtk-enable-event-sounds=true
gtk-enable-input-feedback-sounds=true
gtk-xft-antialias=true
gtk-xft-hinting=true
gtk-xft-hintstyle=hintfull
gtk-xft-rgba=rgb
Well it is back to the old settings like 0.5.6 for 0.6.0, so I'm assuming this is how it was suppose to be? Personally I wasn't sure if the GTK settings had changed for newer versions...
Looks good now thanks
Yes, this was fixed in 0.6.0, I didn't happen to find time to write that here. Thank you for confirmation that it was fixed for you. Thank you very much.