From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Andreas Müller" <schnitzeltony@googlemail.com>,
"openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>,
"Patches and discussions about the oe-core layer"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] Language settings GTK (glibc?) problem
Date: Wed, 03 Feb 2016 14:50:12 +0000 [thread overview]
Message-ID: <1454511012.27087.183.camel@linuxfoundation.org> (raw)
In-Reply-To: <CALbNGRRmD=4QUi=+_fx48M4GDB9VwTX5m5wH12j4ed1OK6SW6Q@mail.gmail.com>
On Wed, 2016-02-03 at 12:49 +0100, Andreas Müller wrote:
> Hi,
>
> while testing libreoffice language packets I found that language
> settings for GTK based apps are broken. Interestingly QT based
> applications (tested with qtcreator and lxqt) and libreoffice are
> working fine.
>
> I did some research and hope for some expert with helping hints.
> Details are:
>
> * I am testing with jethro environment
I did wonder about http://git.yoctoproject.org/cgit.cgi/poky/commit/?id
=3b5288f0a28205289063424afc474675cbaa05b8
or possibly:
https://github.com/rehsack/poky/commit/46ac36953e2e76ba716c7ba42ddfe41c
9a19a11d
but I haven't looked into this much and don't have experience in this
area.
Cheers,
Richard
WARNING: multiple messages have this Message-ID (diff)
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Andreas Müller" <schnitzeltony@googlemail.com>,
"openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>,
"Patches and discussions about the oe-core layer"
<openembedded-core@lists.openembedded.org>
Subject: Re: Language settings GTK (glibc?) problem
Date: Wed, 03 Feb 2016 14:50:12 +0000 [thread overview]
Message-ID: <1454511012.27087.183.camel@linuxfoundation.org> (raw)
In-Reply-To: <CALbNGRRmD=4QUi=+_fx48M4GDB9VwTX5m5wH12j4ed1OK6SW6Q@mail.gmail.com>
On Wed, 2016-02-03 at 12:49 +0100, Andreas Müller wrote:
> Hi,
>
> while testing libreoffice language packets I found that language
> settings for GTK based apps are broken. Interestingly QT based
> applications (tested with qtcreator and lxqt) and libreoffice are
> working fine.
>
> I did some research and hope for some expert with helping hints.
> Details are:
>
> * I am testing with jethro environment
I did wonder about http://git.yoctoproject.org/cgit.cgi/poky/commit/?id
=3b5288f0a28205289063424afc474675cbaa05b8
or possibly:
https://github.com/rehsack/poky/commit/46ac36953e2e76ba716c7ba42ddfe41c
9a19a11d
but I haven't looked into this much and don't have experience in this
area.
Cheers,
Richard
next prev parent reply other threads:[~2016-02-03 14:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 11:49 Language settings GTK (glibc?) problem Andreas Müller
2016-02-03 14:50 ` Richard Purdie [this message]
2016-02-03 14:50 ` Richard Purdie
2016-02-03 16:01 ` [OE-core] " Andreas Müller
2016-02-03 16:01 ` Andreas Müller
2016-02-04 10:09 ` [OE-core] " Andreas Müller
2016-02-04 10:09 ` Andreas Müller
2016-02-05 12:02 ` [OE-core] " Andreas Müller
2016-02-05 12:02 ` Andreas Müller
2016-02-05 12:04 ` [OE-core] " Andreas Müller
2016-02-05 12:04 ` Andreas Müller
2016-02-05 15:27 ` [OE-core] " Burton, Ross
2016-02-05 15:27 ` Burton, Ross
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=1454511012.27087.183.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=schnitzeltony@googlemail.com \
/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.