From: Gary Thomas <gary@mlbassoc.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: Control over Sato theme
Date: Thu, 14 Feb 2013 10:07:35 -0700 [thread overview]
Message-ID: <511D19D7.8020706@mlbassoc.com> (raw)
In-Reply-To: <CAJTo0Lacok_G7hbBXptLM5easV_9t+pwjX+4S8js2XtmLmfX=Q@mail.gmail.com>
On 2013-02-14 09:50, Burton, Ross wrote:
> On 14 February 2013 16:48, Gary Thomas <gary@mlbassoc.com> wrote:
>> Much closer. Now the theme is being used (and it does suit me!)
>> but I'm also getting a lot of warnings:
>>
>> matchbox-wm: unable to open theme:
>> /usr/share/themes/Clearlooks-DarkOrange/matchbox/theme.xml
>> (matchbox-panel:29173): Gtk-WARNING **: Unable to locate theme engine in
>> module_path: "clearlooks",
>> (matchbox-desktop:29172): Gtk-WARNING **: Unable to locate theme engine in
>> module_path: "clearlooks",
>> ./client_gui.py:219: GtkWarning: Unable to locate theme engine in
>> module_path: "clearlooks",
>>
>> Can I get rid of these? Should I bother?
>
> Yes and yes, it can look a *lot* better. Add a runtime dependency on
> your theme package to gtk-engine-clearlooks (part of the gtk-engines
> recipe).
Thanks, that does look [mostly] better, but I'm still getting some warnings/errors:
matchbox-wm: unable to open theme: /usr/share/themes/Clearlooks-DarkOrange/matchbox/theme.xml
/usr/share/themes/Clearlooks-DarkOrange/gtk-2.0/gtkrc:58: Clearlooks configuration option "sunkenmenu" is not supported and will be ignored.
/usr/share/themes/Clearlooks-DarkOrange/gtk-2.0/gtkrc:59: Clearlooks configuration option "menuitemstyle" is not supported and will be ignored.
/usr/share/themes/Clearlooks-DarkOrange/gtk-2.0/gtkrc:60: Clearlooks configuration option "listviewitemstyle" is not supported and will be ignored.
/usr/share/themes/Clearlooks-DarkOrange/gtk-2.0/gtkrc:61: Clearlooks configuration option "progressbarstyle" is not supported and will be ignored.
Maybe these are GTK-3 elements?
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2013-02-14 17:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 23:19 Control over Sato theme Gary Thomas
2013-02-13 16:00 ` Burton, Ross
2013-02-14 13:24 ` Gary Thomas
2013-02-14 15:00 ` Burton, Ross
2013-02-14 15:08 ` Gary Thomas
2013-02-14 15:13 ` Burton, Ross
2013-02-14 15:30 ` Gary Thomas
2013-02-14 15:38 ` Burton, Ross
2013-02-14 15:48 ` Gary Thomas
2013-02-14 15:53 ` Burton, Ross
2013-02-14 16:48 ` Gary Thomas
2013-02-14 16:50 ` Burton, Ross
2013-02-14 17:07 ` Gary Thomas [this message]
2013-02-14 17:16 ` Burton, Ross
2013-02-14 17:28 ` Gary Thomas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=511D19D7.8020706@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=ross.burton@intel.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.