moko-gtk-engine throws errors

[koen@…]

/usr/share/themes/Moko/gtk-2.0/gtkrc:162: Invalid symbolic color 'fg_color'
/usr/share/themes/Moko/gtk-2.0/gtkrc:162: error: invalid identifier `fg_color',
expected valid identifier

[thomas@…]

Strange, the same symbollic colour name is used just a few lines up. What SVN
revision produces those errors?

[koen@…]

root@a780:~# ipkg list_installed | grep moko-g
moko-gtk-engine - 0.1.0+svnr3207-r0 - Moko GTK+ theme engine
moko-gtk-theme - 0.1.0+svnr3207-r0 - Moko GTK+ theme engine

[thomas@…]

I've just tested the same revisions on the device and cannot reproduce. Is there
any specific application that creates these errors?

[koen@…]

it appears in the console after starting xserver-nodm-init by hand

[koen@…]

The startup log (minus the config-parser messages):

ot@a780:~# /etc/init.d/xserver-nodm start
root@a780:~# Starting Xserver

Extended Input Devices not yet supported. Impelement it at line 637 in kinput.c
D-BUS per-session daemon address is:
unix:abstract=/tmp/dbus-Vc2kSYtrZM,guid=ddbeda083c37dc1cf83d3c0047163756
[settings daemon] Forking. run with -n to prevent fork
matchbox-keyboard-ui.c:150,update_display_size() mark
matchbox-keyboard-ui.c:168,update_display_size() #### Orientation know '1'

matchbox-keyboard-key.c:127,mb_kbd_key_set_fill() mark
matchbox-keyboard-key.c:127,mb_kbd_key_set_fill() mark
matchbox-keyboard-key.c:127,mb_kbd_key_set_fill() mark
matchbox-keyboard-key.c:127,mb_kbd_key_set_fill() mark
matchbox-keyboard-key.c:127,mb_kbd_key_set_fill() mark
matchbox-keyboard-key.c:127,mb_kbd_key_set_fill() mark
matchbox-keyboard-key.c:127,mb_kbd_key_set_fill() mark
matchbox-keyboard-key.c:127,mb_kbd_key_set_fill() mark
matchbox-keyboard-key.c:127,mb_kbd_key_set_fill() mark
sh: /usr/local/arm/2.95.3/bin/cpp: No such file or directory
root@a780:~# matchbox-keyboard-ui.c:722,mb_kbd_ui_resources_create() setting no
focus hint
(neod:3380): DEBUG: '/dev/input/event0' open OK, fd = '5'
(neod:3380): DEBUG: '/dev/input/event1' open OK, fd = '6'
(neod:3380): DEBUG: '/dev/input/event2' open OK, fd = '7'
(neod:3380): DEBUG: '/dev/input/event3' open OK, fd = '8'
(neod:3380): DEBUG: opened 4 input nodes.
(neod:3380): DEBUG: added fd 5 to list of watchers
(neod:3380): DEBUG: added fd 6 to list of watchers
(neod:3380): DEBUG: added fd 7 to list of watchers
(neod:3380): DEBUG: added fd 8 to list of watchers
(neod:3380): DEBUG: mainmenu powersave reset
(neod:3380): DEBUG: mainmenu powersave reset
(neod:3380): DEBUG: requested to set display brightness 100
matchbox-keyboard-remote.c:34,mb_kbd_remote_process_xevents() got a message

(neod:3380): DEBUG: backlight_node_dir = ezx-bl
(neod:3380): DEBUG: detected backlight in sysfs as
'/sys/class/backlight/ezx-bl/brightness'
(neod:3380): DEBUG: scanned maximum brightness for
'/sys/class/backlight/ezx-bl/brightness' = '50'
(neod:3380): DEBUG: writing '50' to '/sys/class/backlight/ezx-bl/brightness'
(neod:3380): DEBUG: panel mainmenu sound init
(neod:3380): DEBUG: mainmenu sound state callback. state = 1
(neod:3380): DEBUG: sound init ok. threaded mainloop started
(neod:3380): DEBUG: mainmenu sound state callback. state = 2
(neod:3380): DEBUG: mainmenu sound state callback. state = 3
(neod:3380): DEBUG: mainmenu sound state callback. state = 4
/usr/share/themes/Moko/gtk-2.0/gtkrc:162: Invalid symbolic color 'fg_color'
/usr/share/themes/Moko/gtk-2.0/gtkrc:162: error: invalid identifier `fg_color',
expected valid identifier
matchbox-keyboard-remote.c:34,mb_kbd_remote_process_xevents() got a message

matchbox-keyboard-remote.c:34,mb_kbd_remote_process_xevents() got a message

matchbox-keyboard-remote.c:34,mb_kbd_remote_process_xevents() got a message

matchbox-keyboard-remote.c:39,mb_kbd_remote_process_xevents() is a Client Message

(matchbox-panel-2:3385): DEBUG: moko_panel_applet_init
(matchbox-panel-2:3385): DEBUG: moko_panel_applet_init
libmokogsmd: Unable to connect to gsmd, trying to start it
/usr/share/themes/Moko/gtk-2.0/gtkrc:162: Invalid symbolic color 'fg_color'
/usr/share/themes/Moko/gtk-2.0/gtkrc:162: error: invalid identifier `fg_color',
expected valid identifier
/usr/share/themes/Moko/gtk-2.0/gtkrc:162: Invalid symbolic color 'fg_color'
/usr/share/themes/Moko/gtk-2.0/gtkrc:162: error: invalid identifier `fg_color',
expected valid identifier
Stopping GSM daemon: no /usr/sbin/gsmd found; none killed.
gsmd.
Starting GSM daemon: gsmd.

(matchbox-panel-2:3385): WARNING : libgsmd: can't connect to gsmd. You
won't receive any events.
(matchbox-panel-2:3385): DEBUG: moko_panel_applet_init
Got path /org/gnome/evolution/dataserver/calendar/filehome_rootmoko_journal_
for new calendar

(openmoko-today:3382): WARNING : Cannot read
/usr/share/today/vfolders/PIM.directory: No such file or directory
(neod:3380): DEBUG: mainmenu powersave timeout 1
(neod:3380): DEBUG: requested to set display brightness 25
(neod:3380): DEBUG: writing '12' to '/sys/class/backlight/ezx-bl/brightness'
matchbox-keyboard-remote.c:34,mb_kbd_remote_process_xevents() got a message

matchbox-keyboard-remote.c:34,mb_kbd_remote_process_xevents() got a message

matchbox-keyboard-remote.c:34,mb_kbd_remote_process_xevents() got a message

matchbox-keyboard-remote.c:34,mb_kbd_remote_process_xevents() got a message

matchbox-keyboard-remote.c:34,mb_kbd_remote_process_xevents() got a message

matchbox-keyboard-remote.c:34,mb_kbd_remote_process_xevents() got a message

matchbox-keyboard-remote.c:34,mb_kbd_remote_process_xevents() got a message

matchbox-keyboard-remote.c:34,mb_kbd_remote_process_xevents() got a message

Got path /org/gnome/evolution/dataserver/calendar/filehome_rootmoko_journal_
for new calendar
(openmoko-dialer:3383): DEBUG: Journal Loaded
Got path
/org/gnome/evolution/dataserver/calendar/filehome_rootevolution_calendar_local_system_
for new calendar
Got path
/org/gnome/evolution/dataserver/calendar/filehome_rootevolution_tasks_local_system_
for new calendar
(openmoko-dialer:3383): DEBUG: The Journal is empty
(neod:3380): DEBUG: mainmenu powersave timeout 2
(neod:3380): DEBUG: requested to set display brightness 0
(neod:3380): DEBUG: writing '0' to '/sys/class/backlight/ezx-bl/brightness'
(openmoko-dialer:3383): DEBUG: Requesting registration

[koen@…]

root@a780:/usr/share/themes/Moko/gtk-2.0# grep fg_color *
gtkrc:gtk_color_scheme =
"fg_color:#333;bg_color:#ccc;base_color:#ccc;text_color:#000;selected_bg_color:#ff7d00;selected_fg_color:#000"
gtkrc: fg [NORMAL] = @fg_color
gtkrc: fg [PRELIGHT] = @fg_color
gtkrc: fg [ACTIVE] = @selected_fg_color
gtkrc: fg [INSENSITIVE] = @fg_color
gtkrc: fg [SELECTED] = @selected_fg_color
gtkrc: bg[NORMAL] = @fg_color
gtkrc: bg[PRELIGHT] = @fg_color
gtkrc: text[NORMAL] = @selected_fg_color
gtkrc: text[PRELIGHT] = @selected_fg_color
gtkrc: fg[NORMAL] = @selected_fg_color
gtkrc: bg[PRELIGHT] = @fg_color
gtkrc: bg[ACTIVE] = @fg_color
gtkrc: fg[NORMAL] = @selected_fg_color
gtkrc: fg[PRELIGHT] = @selected_fg_color
openmoko-calculator: bg[NORMAL] = @selected_fg_color
openmoko-dialer: bg[NORMAL] = @selected_fg_color
openmoko-dialer: base[NORMAL] = @selected_fg_color
openmoko-dialer: fg[NORMAL] = @fg_color
openmoko-dialer: bg[PRELIGHT] = @selected_fg_color
root@a780:/usr/share/themes/Moko/gtk-2.0#

[hrw@…]

root@fic-gta01Bv4:~/$ ipkg list_installed | grep moko-g
moko-gtk-engine - 0.1.0+svnr3240-r0 - Moko GTK+ theme engine
moko-gtk-theme - 0.1.0+svnr3240-r0 - Moko GTK+ theme engine

I have same problem:
/usr/share/themes/Moko/gtk-2.0/gtkrc:65: Invalid symbolic color 'fg_color'
/usr/share/themes/Moko/gtk-2.0/gtkrc:65: error: invalid identifier `fg_color',
expected valid identifier
/usr/share/themes/Moko/gtk-2.0/gtkrc:65: Invalid symbolic color 'fg_color'
/usr/share/themes/Moko/gtk-2.0/gtkrc:65: error: invalid identifier `fg_color',
expected valid identifier

[thomas@…]

Can you check to make sure the gtkrc file was installed properly? I still
haven't been able to reproduce this reliably.

[thomas@…]

Resolving as WORKSFORME since I can't reproduce and no further information has
been given.