gtkrc:35: error:

While starting Novell’s gwcheck application in a terminal window, get the following error at the link below? I ran this passed the Novell GroupWise support team and they say it’s an issue with the gui and not the gwcheck app. I was wondering if anyone has seen this before and if so, is there a fix? I don’t think it is hurting anything, but wanted to make sure.

Thanks!

https://forums.novell.com/attachment.php?attachmentid=4991&d=1389298455

shesser Wrote in message:
[color=blue]

While starting Novell’s gwcheck application in a terminal window, get
the following error at the link below? I ran this passed the Novell
GroupWise support team and they say it’s an issue with the gui and not
the gwcheck app. I was wondering if anyone has seen this before and if
so, is there a fix? I don’t think it is hurting anything, but wanted to
make sure.[/color]

Which version of SUSE Linux Enterprise Server are you doing this
from? Please post the output from “cat /etc/*release”.
[color=blue]

https://forums.novell.com/attachment.php?attachmentid=4991&d=1389298455[/color]

For the benefit of others, the error message in the attached PDF is

/usr/share/themes/Gilouche/gtk-2.0/gtkrc:rc35: error: lexical
error or unexpected token, expected valid token

HTH.

Simon
SUSE Knowledge Partner

----Android NewsGroup Reader----
http://www.piaohong.tk/newsgroup

Hi shesser,

would you mind sharing what’s at line 35 of /usr/share/themes/Gilouche/gtk-2.0/gtkrc, with a few lines of context?

Regards,
Jens

Here is the release info you requested

SUSE Linux Enterprise Server 11 (x86_64)
VERSION = 11
PATCHLEVEL = 2
LSB_VERSION=“core-2.0-noarch:core-3.2-noarch:core-4.0-noarch:core-2.0-x86_64:core-3.2-x86_64:core-4.0-x86_64”
Novell Open Enterprise Server 11 (x86_64)
VERSION = 11.1
PATCHLEVEL = 1

Would this be enough to help? Starting at the top of the file down to line 72 I believe.

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

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

engine "clearlooks"  {
  #style               = CLASSIC # classic tabs
  style               = GUMMY   # classic tabs
  toolbarstyle        = 0       # flat toolbars
  animation           = TRUE    # animated progressbars
  menubarstyle        = 2       # flat menus
  colorize_scrollbar  = TRUE   
}

#engines 2.22 -- supposedly gets rid of menu/toolbar separator
GtkMenuBar::shadow_type = GTK_SHADOW_NONE
GtkToolbar::shadow_type = GTK_SHADOW_NONE

}

Hi shesser,

yes, this gives a chance to make a better guess :smiley:

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

So posting it like this is better for you? Does the line count include rem’ed out lines? I’m not a programmer but understand the basics. So the error is stating the something in line 35 is generating the error? I could post the complete file if needed. I will try an rem out the lines your talking about and see what happens. The server was installed with sles11sp2 from the cd. I want to say, other then updates that have been applied through the channel, I have never messed with it! :cool:

[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

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

engine "clearlooks"  {
  #style               = CLASSIC # classic tabs
  style               = GUMMY   # classic tabs
  toolbarstyle        = 0       # flat toolbars
  animation           = TRUE    # animated progressbars
  menubarstyle        = 2       # flat menus
  colorize_scrollbar  = TRUE   
}

#engines 2.22 -- supposedly gets rid of menu/toolbar separator
GtkMenuBar::shadow_type = GTK_SHADOW_NONE
GtkToolbar::shadow_type = GTK_SHADOW_NONE

}[/CODE]

So I tried the modified file and this is the result that comes up in the terminal window, looks like it goes a little deeper than just those lines. This error does not seem to hinder the application from running. The check utility loads and works.

With Rem’ed out lines
server:/opt/novell/groupwise/gwcheck/bin # ./gwcheck
libxcb: WARNING! Program tries to unlock a connection without having acquired
a lock first, which indicates a programming error.
There will be no further warnings about this issue.
libxcb: WARNING! Program tries to lock an already locked connection,
which indicates a programming error.
There will be no further warnings about this issue.
/usr/share/themes/Gilouche/gtk-2.0/gtkrc:66: Engine “clearlooks” is unsupported, ignoring
/usr/share/themes/Gilouche/gtk-2.0/gtkrc:69: Failed to parse property value " GTK_SHADOW_NONE " for GtkMenuBar::shadow-type' /usr/share/themes/Gilouche/gtk-2.0/gtkrc:70: Failed to parse property value " GTK_SHADOW_NONE " for GtkToolbar::shadow-type’
/usr/share/themes/Gilouche/gtk-2.0/gtkrc:88: error: lexical error or unexpected token, expected valid token

Removed the rem’ed lines
server:/opt/novell/groupwise/gwcheck/bin # ./gwcheck
libxcb: WARNING! Program tries to unlock a connection without having acquired
a lock first, which indicates a programming error.
There will be no further warnings about this issue.
libxcb: WARNING! Program tries to lock an already locked connection,
which indicates a programming error.
There will be no further warnings about this issue.
/usr/share/themes/Gilouche/gtk-2.0/gtkrc:35: error: lexical error or unexpected token, expected valid token

Hi shesser,

As all this was more or less a shot into the dark from my side, let me ask you if you’ll call this issue “closed” or would like to dig into it deeper (like finding out what caused that inconsistency between the file content and the run-time environment, which obviously was/is unable to handle the file’s contents).

[QUOTE=shesser;18638][…]
Removed the rem’ed lines
server:/opt/novell/groupwise/gwcheck/bin # ./gwcheck
libxcb: WARNING! Program tries to unlock a connection without having acquired
a lock first, which indicates a programming error.
There will be no further warnings about this issue.
libxcb: WARNING! Program tries to lock an already locked connection,
which indicates a programming error.
There will be no further warnings about this issue.
/usr/share/themes/Gilouche/gtk-2.0/gtkrc:35: error: lexical error or unexpected token, expected valid token[/QUOTE]

Boy, does this last line make me look stupid - Gilouche is a GTK theme, not an application :[ Since it came with SLES (“rpm -qf /usr/share/themes/Gilouche/gtk-2.0/gtkrc” ought to tell you which RPM brought the file onto your system, “rpm -qi rpmname” should reveal some details) I might ask SUSE support to have an explicit look at the dependencies.

Regards,
Jens

Just and FYI for you Jens, the rpm info is below. Thanks for your help on this and I will probably get Novell to look at this by opening up a ticket with them.:slight_smile:

Name : gtk2-theme-SLED Relocations: (not relocatable)
Version : 11.1 Vendor: SUSE LINUX Products GmbH, Nuernberg, Germany
Release : 1.29.82 Build Date: Tue May 11 16:19:23 2010
Install Date: Wed Jul 10 11:12:06 2013 Build Host: anonymi
Group : System/GUI/GNOME Source RPM: gtk2-theme-SLED-11.1-1.29.82.src.rpm
Size : 637067 License: GPL v2 or later
Signature : RSA/8, Tue May 11 16:19:26 2010, Key ID e3a5c360307e3d54
Packager : http://bugs.opensuse.org
Summary : SLED themes and metathemes for gtk2 and metacity
Description :
SLED themes and metathemes for gtk2 and metacity contains several
themes in SLED look: Gilouche, GreyGilouche, Synchonicity and SuSE.

Authors:

Jakub Steiner <jimmac@novell.com>
Garrett LeSage <glesage@novell.com>
Richard Stellingwerff <remenic@gmail.com>
Daniel Borgmann <daniel.borgmann@gmail.com>
Kenneth Wimer <wimer@suse.de>
Everaldo Coelho <everaldo@everaldo.com>

Distribution: SUSE Linux Enterprise 11

[QUOTE=jmozdzen;18656]Hi shesser,

As all this was more or less a shot into the dark from my side, let me ask you if you’ll call this issue “closed” or would like to dig into it deeper (like finding out what caused that inconsistency between the file content and the run-time environment, which obviously was/is unable to handle the file’s contents).

Boy, does this last line make me look stupid - Gilouche is a GTK theme, not an application :[ Since it came with SLES (“rpm -qf /usr/share/themes/Gilouche/gtk-2.0/gtkrc” ought to tell you which RPM brought the file onto your system, “rpm -qi rpmname” should reveal some details) I might ask SUSE support to have an explicit look at the dependencies.

Regards,
Jens[/QUOTE]

Another fyi, I decided to play around with using some different themes. Each one I used produced a different error in the terminal window. It just may be that the utility gwcheck doesn’t play well with the various themes you can use under gnome. I’m not going to worry to much about this!:slight_smile:

Thanks again!

Hi shesser,

[QUOTE=shesser;18662]Just and FYI for you Jens, the rpm info is below. Thanks for your help on this and I will probably get Novell to look at this by opening up a ticket with them.:slight_smile:

Name : gtk2-theme-SLED Relocations: (not relocatable)[/QUOTE]

opening a ticket is probably a good idea. OTOH, what catches the eye is that you have a SLED RPM there - isn’t this a SLES machine? :wink:

If you need any more assistance, just let us know :slight_smile:

Regards,
Jens

Confusingly the name and description contains SLED but it’s included in SLES:

noi:~ # cat /etc/SuSE-release SUSE Linux Enterprise Server 11 (x86_64) VERSION = 11 PATCHLEVEL = 3 noi:~ # zypper packages | grep gtk2-theme-SLED i | SLES11-SP3-Pool | gtk2-theme-SLED | 11.1-1.29.82 | noarch noi:~ #
Also

foo:~ # mount | grep mnt /local/SLES-11-SP3-DVD-x86_64-GM-DVD1.iso on /mnt/tmp type iso9660 (ro) foo:~ # find /mnt/tmp/ -name gtk2-theme-SLED\\* /mnt/tmp/suse/noarch/gtk2-theme-SLED-11.1-1.29.82.noarch.rpm foo:~ #

You think maybe there should be a theme package like this for sles also? How can we find this out?

Very easily, look and see if there’s such a package with SLES in the name in the SLES repos or on the SLES DVD.

foo:~ # cat /etc/SuSE-release SUSE Linux Enterprise Server 11 (x86_64) VERSION = 11 PATCHLEVEL = 3 foo:~ # zypper packages | grep gtk2-theme-SLE i | SLES11-SP3-Pool | gtk2-theme-SLED | 11.1-1.29.82 | noarch foo:~ # foo:~ # mount | grep mnt/tmp /local/SLES-11-SP3-DVD-x86_64-GM-DVD1.iso on /mnt/tmp type iso9660 (ro) foo:~ # find /mnt/tmp/ -name gtk2-theme-SLE\\* /mnt/tmp/suse/noarch/gtk2-theme-SLED-11.1-1.29.82.noarch.rpm foo:~ #
So there’s no gtk2-theme-SLES package. There’s another 11 packages in SLES the names of which contain SLED:

MozillaFirefox-branding-SLED
desktop-data-SLED
gnome-menus-branding-SLED
gtk2-branding-SLED
kdebase4-SLED
kdebase4-SLED-lang
kdebase4-runtime-branding-SLED
kdebase4-workspace-branding-SLED
kdelibs4-branding-SLED
kdm-branding-SLED
kio_sysinfo-branding-SLED

SLED and SLES are built on a common base and I guess SUSE initially made the branding packages for SLED then re-used them in SLES. (There are no packages in SLED which have SLES in their name.) A logical thing to do, though evidently there is scope for confusion as a result. Perhaps using SLE instead of SLED would be better for such packages.

Thanks again, and I agree, sles and sled are very similar so that’s probably why the use the above.