Hi shesser,
yes, this gives a chance to make a better guess
First of all, for future incidents, it’d be better viewable if you’d put such segments into [ C O D E ] … [ / C O D E ] blocks (of course without the blanks - or if you’re accessing the forum via browser, use the advanced editor, mark the block via i.e. mouse, and hit the “#” action icon in the editor tool bar).
[CODE]# Gilouche 2.0
Based on Clearlooks
Created by Jakub Steiner, Garrett LeSage, Aaron Bockover
Richard Stellingwerff, Emil Jacobs, and Daniel Borgmann.
#defining icon sizes
#gtk-icon-sizes = “gtk-menu=16,16:panel-menu=16,16:panel=16,16:gtk-button=16,16:gtk-large-toolbar=22,22”
#default color scheme
gtk_color_scheme = “fg_color:#101010
bg_color:#fbf8f1
base_color:#fff
text_color:#000
selected_bg_color:#6798cb
selected_fg_color:#fff”
style “theme-default”
{
GtkButton ::default_border = { 0, 0, 0, 0 }
GtkRange ::trough_border = 0
GtkPaned ::handle_size = 8
GtkRange ::slider_width = 15
GtkRange ::stepper_size = 15
GtkScrollbar ::min_slider_length = 30
GtkCheckButton ::indicator_size = 14
GtkMenuBar ::internal-padding = 0
GtkTreeView ::expander_size = 12
GtkExpander ::expander_size = 14
# The following line hints to gecko (and possibly other appliations)
# that the entry should be drawn transparently on the canvas.
# Without this, gecko will fill in the background of the entry.
GtkEntry ::honors-transparent-bg-hint = 1
xthickness = 1
ythickness = 1[/CODE]
From my counting, line 35 follows:
[CODE]fg[NORMAL] = @fg_color #“#000000” # black
fg[PRELIGHT] = @fg_color #“#000000” # black
fg[SELECTED] = @selected_fg_color #“#ffffff” # white
fg[ACTIVE] = @fg_color #“#000000” # black
fg[INSENSITIVE] = darker (@bg_color) #“#b5b3ac” # dark beige
bg[NORMAL] = @bg_color # "#ede9e3"
bg[PRELIGHT] = shade (1.02, @bg_color) #"#f9f7f3" # very light beige
bg[SELECTED] = @selected_bg_color # "#5598d7" # deepsky
bg[INSENSITIVE] = @bg_color # "#efebe5" # beige
bg[ACTIVE] = shade (0.9, @bg_color) #"#dcd4c9" #"#d7d3ca" # dark beige
base[NORMAL] = @base_color # "#ffffff" # white
base[PRELIGHT] = shade (0.95, @bg_color) # "#5f8ec4" # dark beige
base[ACTIVE] = shade (0.9, @selected_bg_color) # "#a69f91" # darker deepsky
base[SELECTED] = @selected_bg_color # "#5598d7" # deepsky
base[INSENSITIVE] = @bg_color # "#e8e5de" # beige
text[NORMAL] = @text_color # "#000000" # black
text[PRELIGHT] = @text_color # "#000000" # black
text[ACTIVE] = @selected_fg_color # "#ffffff" # white
text[SELECTED] = @selected_fg_color # "#ffffff" # white
text[INSENSITIVE] = darker (@bg_color) # "#b5b3ac" # dark beige[/CODE]
I suggest to either make a backup copy of the file and to remove all that color customization via an editor before retesting, or to comment it out by adding “#” at the start of each line. Syntactically, these stick out like a sore thumb.
I confess to have never worked with Gilouche. Probably this file got “messed up” while running a newer version of Gilouche, and now you’re using an older version that doesn’t know how to handle these statement… if this profile isn’t used across multiple systems (i.e. via NFS), that would have to have happened on the same machine.
Regards,
Jens