Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 14 May 2010 13:59:50 -0400
From:      Joe Marcus Clarke <marcus@freebsd.org>
To:        Jonathan Chen <jonc@chen.org.nz>
Cc:        freebsd-gnome@freebsd.org
Subject:   Re: gnome-keyring 2.30.1 woes.
Message-ID:  <4BED8F96.7070801@freebsd.org>
In-Reply-To: <20100513222654.GA1680@osiris.chen.org.nz>
References:  <20100513204933.GA248@osiris.chen.org.nz> <20100513210117.GA571@osiris.chen.org.nz> <4BEC7679.1080106@freebsd.org> <20100513222654.GA1680@osiris.chen.org.nz>

next in thread | previous in thread | raw e-mail | index | archive | help
On 5/13/10 6:26 PM, Jonathan Chen wrote:
> On Thu, May 13, 2010 at 06:00:25PM -0400, Joe Marcus Clarke wrote:
>> On 5/13/10 5:01 PM, Jonathan Chen wrote:
>>> On Fri, May 14, 2010 at 08:49:34AM +1200, Jonathan Chen wrote:
>>>> Hi,
>>>>
>>>> I recently upgraded to GNOME 2.30, and I'm experiencing problems with
>>>> gnome-keyring. The mail-notification daemon continually asks me for a
>>>> password, and if I provide one, it then informs me that it is unable
>>>> to save it.
>>>>
>>>> If I invoke:
>>>>     "Applications > Accessories > Passwords and Encryption Keys"
>>>>
>>>> The app informs me that "Couldn't communicate with key ring daemon". 
>>>>
>>>> ~/.xsession-errors has the following:
>>>>     ** Message: init gpgme version 1.2.0
>>>>     ** Message: secret service operation failed: The name org.freedesktop.secrets was not provided by any .service files
>>>>     ** Message: secret service operation failed: The name org.freedesktop.secrets was not provided by any .service files
>>>>
>>>>     ** (seahorse:14613): WARNING **: couldn't get default keyring name: Error communicating with gnome-keyring-daemon
>>>
>>> Looks like this is the problem:
>>>     http://bugs.gentoo.org/show_bug.cgi?id=314641
>>>
>>> Anyone here have workarounds?
>>
>> Did you follow the steps in /usr/ports/UPDATING on properly updating
>> gnome-keyring?  If not, then what you're seeing would be expected.
> 
> Yes, I did notice and followed the steps in UPDATING. In fact, when I
> noticed the problem, I even forced a rebuild of gnome-keyring and
> libgnome-keyring just in case there was something I missed.
> 
> If I kill all gnome-keyring-daemon processes and start it up by hand
> as suggested by the link, the problem goes away; BUT this then
> introduces a problem with ssh-authentication ... :(

This should be fixed now.

Joe

-- 
Joe Marcus Clarke
FreeBSD GNOME Team	::	gnome@FreeBSD.org
FreeNode / #freebsd-gnome
http://www.FreeBSD.org/gnome



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4BED8F96.7070801>