gnome-keyring-manager can't see gnome-keyring-daemon

[drjimmy42]

Every time I go to my evolution exchange calendar I am prompted for my exchange password. In order to investigate I opened up gnome-keyring-manager which said "GNOME Keyring daemon is not running". And yet:

Code: Select all

~> ps -eF | grep keyring
jorussel 20812     1  0   642   792   0 16:36 pts/0    00:00:00 gnome-keyring-daemon
jorussel 20821 20466  0 23381 12236   0 16:36 pts/0    00:00:00 gnome-keyring-manager

After killing the daemon and starting it again it still doesn't work.

Has anyone else been having problems like this?

[littleman]

same problem here. I can't teach the keyring to use my wep key

[saffsd]

Make that a treble. No idea what's causing it.

[drjimmy42]

I solved this, and MANY other weirdo problems dealing with application communication by giving up on my meticulously crafted xinit and xsession files and startx and finally just went with gdm to start my desktop. It takes care of a lot of dbus session initiation and other magical things that make gnome work better. All weird things like this were fixed after I did that. Good luck.

[Sachankara]

You have to export the variables gnome-keyring-daemon spits out when started. One way is by putting the following in .bash_profile :

Code: Select all

export $(gnome-keyring-daemon)

And this in .bash_logout :

Code: Select all

kill $GNOME_KEYRING_PID

Or you could install pam_keyring (you need the patch from http://bugs.gentoo.org ) and let pam start gnome-keyring-daemon, export the two necessary environment variables while unlocking all keyrings which have the same password as your login password.

Both of the mentioned methods should work with all window and desktop managers. So it's just not limited to Gnome.

[drjimmy42]

This is exactly my point. The number of environment variables/process/virgin sacrifices that are required to get all this stuff to work passed my tolerance for keep up with. I started letting gdm sacrifice whatever it wants and everything has been swell. gdm can be used to start kde and any other desktop you want as well.

[sdunne]

Or you could install pam_keyring (you need the patch from http://bugs.gentoo.org ) and let pam start gnome-keyring-daemon, export the two necessary environment variables while unlocking all keyrings which have the same password as your login password.

Any kind soul mind lending a hand here ?

This patch hasn't made it into portage yet, so I'm attempting to setup a local portage overlay and apply the patch myself. However I've never done this before and I'm out of my depth, despite scouring the wiki and here

I'm working on the premise of keeping the local version at 0.0.8, since portage is supposed to prefer to use a local overlay when available. I'm running 2.6.21-gentoo-r4 on x86

Local Portage dir in /usr/local/portage and configured in /etc/make.conf
mkdir -p /usr/local/portage/sys-auth/pam_keyring

In /usr/local/portage/sys-auth/pam_keyring I have a copy of pam_keyring_0.0.8.ebuild from portage. I've also created a files subdir which contains the contents of /usr/portage/sys-auth/pam_keyring/files as well as the pam_keyring-0.0.8-sigchild_dfl.patch from bugzilla.

At t5his stage, after running ebuild pam_keyring_0.0.8.ebuild digest from /usr/local/portage/sys-auth/pam_keyring I can build the same as if I were building from portage, so I assume this means my overlay setup is OK.

Now I've edited the ebuild file so src_unpack is now

Code: Select all

 src_unpack() {
    unpack ${A}

    epatch ${FILESDIR}/${P}-fixes.patch
    epatch ${FILESDIR}/${P}-sigchild_dfl.patch
}

I then ran ebuild pam_keyring_0.0.8.ebuild digest again, However when I now attempt to emerge pam_keyring it barfs on applying the new patch as follows

Code: Select all

>>> Emerging (1 of 1) sys-auth/pam_keyring-0.0.8 to /
 * pam_keyring-0.0.8.tar.gz MD5 ;-) ...                                                                     [ ok ]
 * pam_keyring-0.0.8.tar.gz RMD160 ;-) ...                                                                  [ ok ]
 * pam_keyring-0.0.8.tar.gz SHA1 ;-) ...                                                                    [ ok ]
 * pam_keyring-0.0.8.tar.gz SHA256 ;-) ...                                                                  [ ok ]
 * pam_keyring-0.0.8.tar.gz size ;-) ...                                                                    [ ok ]
 * checking ebuild checksums ;-) ...                                                                        [ ok ]
 * checking auxfile checksums ;-) ...                                                                       [ ok ]
 * checking miscfile checksums ;-) ...                                                                      [ ok ]
 * checking pam_keyring-0.0.8.tar.gz ;-) ...                                                                [ ok ]
>>> Unpacking source...
>>> Unpacking pam_keyring-0.0.8.tar.gz to /var/tmp/portage/sys-auth/pam_keyring-0.0.8/work
 * Applying pam_keyring-0.0.8-fixes.patch ...                                                               [ ok ]
 * Applying pam_keyring-0.0.8-sigchild_dfl.patch ...

 * Failed Patch: pam_keyring-0.0.8-sigchild_dfl.patch !
 *  ( /usr/local/portage/sys-auth/pam_keyring/files/pam_keyring-0.0.8-sigchild_dfl.patch )
 * 
 * Include in your bugreport the contents of:
 * 
 *   /var/tmp/portage/sys-auth/pam_keyring-0.0.8/temp/pam_keyring-0.0.8-sigchild_dfl.patch-25755.out


!!! ERROR: sys-auth/pam_keyring-0.0.8 failed.
Call stack:
  ebuild.sh, line 1621:   Called dyn_unpack
  ebuild.sh, line 753:   Called qa_call 'src_unpack'
  ebuild.sh, line 44:   Called src_unpack
  pam_keyring-0.0.8.ebuild, line 24:   Called epatch '/usr/local/portage/sys-auth/pam_keyring/files/pam_keyring-0.0.8-sigchild_dfl.patch'
  eutils.eclass, line 304:   Called die

!!! Failed Patch: pam_keyring-0.0.8-sigchild_dfl.patch!
!!! If you need support, post the topmost build error, and the call stack if relevant.
!!! A complete build log is located at '/var/tmp/portage/sys-auth/pam_keyring-0.0.8/temp/build.log'.

!!! This ebuild is from an overlay: '/usr/local/portage'

here's the contents of /var/tmp/portage/sys-auth/pam_keyring-0.0.8/temp/pam_keyring-0.0.8-sigchild_dfl.patch-25755.out

Code: Select all

***** pam_keyring-0.0.8-sigchild_dfl.patch *****

================================================

PATCH COMMAND:	 patch -p0 -g0 -E --no-backup-if-mismatch < /usr/local/portage/sys-auth/pam_keyring/files/pam_keyring-0.0.8-sigchild_dfl.patch

================================================
patching file pam_keyring-0.0.8/src/pam_keyring.c
Hunk #6 FAILED at 331.
1 out of 8 hunks FAILED -- saving rejects to file pam_keyring-0.0.8/src/pam_keyring.c.rej
================================================

PATCH COMMAND:	 patch -p1 -g0 -E --no-backup-if-mismatch < /usr/local/portage/sys-auth/pam_keyring/files/pam_keyring-0.0.8-sigchild_dfl.patch

================================================
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- pam_keyring-0.0.8/src/pam_keyring.c.orig	2007-02-10 21:11:38.000000000 +0100
|+++ pam_keyring-0.0.8/src/pam_keyring.c	2007-02-10 21:32:09.000000000 +0100
--------------------------
No file to patch.  Skipping patch.
8 out of 8 hunks ignored
================================================

PATCH COMMAND:	 patch -p2 -g0 -E --no-backup-if-mismatch < /usr/local/portage/sys-auth/pam_keyring/files/pam_keyring-0.0.8-sigchild_dfl.patch

================================================
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- pam_keyring-0.0.8/src/pam_keyring.c.orig	2007-02-10 21:11:38.000000000 +0100
|+++ pam_keyring-0.0.8/src/pam_keyring.c	2007-02-10 21:32:09.000000000 +0100
--------------------------
No file to patch.  Skipping patch.
8 out of 8 hunks ignored
================================================

PATCH COMMAND:	 patch -p3 -g0 -E --no-backup-if-mismatch < /usr/local/portage/sys-auth/pam_keyring/files/pam_keyring-0.0.8-sigchild_dfl.patch

================================================
missing header for unified diff at line 3 of patch
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- pam_keyring-0.0.8/src/pam_keyring.c.orig	2007-02-10 21:11:38.000000000 +0100
|+++ pam_keyring-0.0.8/src/pam_keyring.c	2007-02-10 21:32:09.000000000 +0100
--------------------------
No file to patch.  Skipping patch.
8 out of 8 hunks ignored
================================================

PATCH COMMAND:	 patch -p4 -g0 -E --no-backup-if-mismatch < /usr/local/portage/sys-auth/pam_keyring/files/pam_keyring-0.0.8-sigchild_dfl.patch

================================================
missing header for unified diff at line 3 of patch
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- pam_keyring-0.0.8/src/pam_keyring.c.orig	2007-02-10 21:11:38.000000000 +0100
|+++ pam_keyring-0.0.8/src/pam_keyring.c	2007-02-10 21:32:09.000000000 +0100
--------------------------
No file to patch.  Skipping patch.
8 out of 8 hunks ignored

I tried adding an initial diff line to pam_keyring-0.0.8-sigchild_dfl.patch in the same style as in the -fixes patch but it still failed. The errors above are with the sigchild patch as per bugzilla without any changes.

So, what have I messed up this time ??

[sdunne]

Weird...I did the same process again, and this time it worked