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 09:48:26 -0700 [thread overview]
Message-ID: <511D155A.4060304@mlbassoc.com> (raw)
In-Reply-To: <CAJTo0LbKsTACcGn2+F4ZeVftaGpTnhB=tNCOCa3qUzkac9XKyQ@mail.gmail.com>
On 2013-02-14 08:53, Burton, Ross wrote:
> On 14 February 2013 15:48, Gary Thomas <gary@mlbassoc.com> wrote:
>> I'm using 1.3+ (master from about a month ago) and there is such a file
>>
>> meta/recipes-sato/matchbox-sato/matchbox-session-sato/matchbox-session-sato.schemas
>>
>> How do I change this file to use the new theme?
>> Can I just change the file that becomes
>> (/etc/gconf/schemas/matchbox-session-sato.schemas)
>> in order to test the changes?
>
> Not without re-registering the schemas and rebooting - it's probably
> quicker to change that file in your overlay and re-build an image.
>
> If you've installed the theme already you can use gconftool on the
> device to make a one-off change:
>
> $ gconftool-2 --set --type string /desktop/poky/interface/theme
> Clearlooks-DarkOrange
OK, I've installed the theme into /usr/share/themes and changed the
one line in /etc/gconf/schemas/matchbox-session-sato.schemas from Sato
to Clearlooks-DarkOrange
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?
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2013-02-14 16:48 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 [this message]
2013-02-14 16:50 ` Burton, Ross
2013-02-14 17:07 ` Gary Thomas
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=511D155A.4060304@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.