From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Koen Kooi <koen@dominion.thruhere.net>
Subject: Re: [PATCH] gnome-keyring 2.32.1: fix PAM support and make it conditional on DISTRO_FEATURES
Date: Fri, 22 Jul 2011 11:56:20 +0100 [thread overview]
Message-ID: <1311332180.2344.132.camel@rex> (raw)
In-Reply-To: <1311329348-25568-1-git-send-email-koen@dominion.thruhere.net>
On Fri, 2011-07-22 at 12:09 +0200, Koen Kooi wrote:
> The plugin got installed into the wrong dir leading to:
>
> gdm-session-worker[515]: PAM unable to dlopen(/lib/security/pam_gnome_keyring.so): /lib/security/pam_gnome_keyring.so: cannot open shared object file: No such file or directory
>
> Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
> ---
> meta/recipes-gnome/gnome/gnome-keyring_2.32.1.bb | 12 ++++++------
> 1 files changed, 6 insertions(+), 6 deletions(-)
Merged to master, thanks.
Richard
prev parent reply other threads:[~2011-07-22 11:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-22 10:09 [PATCH] gnome-keyring 2.32.1: fix PAM support and make it conditional on DISTRO_FEATURES Koen Kooi
2011-07-22 10:56 ` Richard Purdie [this message]
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=1311332180.2344.132.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=koen@dominion.thruhere.net \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox