Comment 51 for bug 218434

Sebastien - that could well be it.

I don't have a log of precisely what I did, but it boils down to roughly:

- install gnome-devel
- download gnome-keyring from svn
- configure with prefix = /usr
- install

I doubt gnome-devel installs any PAM headers, so gnome-keyring probably
didn't attempt to build any pam integration code.

An ldd of my /usr/bin/gnome-keyring-daemon gives:

 linux-gate.so.1 => (0xb7f93000)
 libgthread-2.0.so.0 => /usr/lib/libgthread-2.0.so.0 (0xb7f7d000)
 librt.so.1 => /lib/tls/i686/cmov/librt.so.1 (0xb7f74000)
 libgconf-2.so.4 => /usr/lib/libgconf-2.so.4 (0xb7f43000)
 libdbus-1.so.3 => /usr/lib/libdbus-1.so.3 (0xb7f0d000)
 libgcrypt.so.11 => /lib/libgcrypt.so.11 (0xb7ec0000)
 libtasn1.so.3 => /usr/lib/libtasn1.so.3 (0xb7eb0000)
 libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0xb7e74000)
 libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0xb7dc3000)
 libpthread.so.0 => /lib/tls/i686/cmov/libpthread.so.0 (0xb7daa000)
 libc.so.6 => /lib/tls/i686/cmov/libc.so.6 (0xb7c5b000)
 libselinux.so.1 => /lib/libselinux.so.1 (0xb7c42000)
 /lib/ld-linux.so.2 (0xb7f94000)
 libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0xb7c3e000)
 libdl.so.2 => /lib/tls/i686/cmov/libdl.so.2 (0xb7c3a000)
 libORBit-2.so.0 => /usr/lib/libORBit-2.so.0 (0xb7be7000)
 libgpg-error.so.0 => /lib/libgpg-error.so.0 (0xb7be3000)
 libpcre.so.3 => /usr/lib/libpcre.so.3 (0xb7bbc000)

I don't see anything mentioning PAM. But I'm a perl hacker, not a C
coder, and I have no dev experience of gnome, so this may not prove a thing!

Please shout if there are any tests on my setup that anybody needs me to
perform.

Ta,

Karl

Sebastien Bacher wrote:
> There is no code change upstream which seem likely to do a change there,
> maybe the people building from svn didn't build the pam integration code
> though?
>
> ** Changed in: gnome-keyring (Ubuntu)
> Importance: Medium => High
>