gnome-keyring does not start org.freedesktop.secrets

Bug #525642 reported by Michael Albinus
48
This bug affects 8 people
Affects Status Importance Assigned to Milestone
GNOME Keyring
Fix Released
Medium
gnome-keyring (Ubuntu)
Fix Released
Low
Ubuntu Desktop Bugs
Lucid
Fix Released
Low
Sebastien Bacher

Bug Description

Binary package hint: gnome-keyring

I've started a D-Bus session in a shell. I've tried to connect the org.freedesktop.secrets service, gnome-keyring is offering. I've got the D-Bus error

"The name org.freedesktop.secrets was not provided by any .service files".

TESTCASE:
* start a non GNOME session (ie KDE) and try to run a software using the keyring (ie seahorse)

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report. The issue is an upstream one and it would be nice if somebody having it could send the bug the to the people writting the software (https://wiki.ubuntu.com/Bugs/Upstream/GNOME)

Changed in gnome-keyring (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
importance: Undecided → Low
Revision history for this message
Sebastien Bacher (seb128) wrote :

Not sure that this interface is supposed to be working yet

Revision history for this message
Michael Albinus (michael-albinus) wrote : Re: [Bug 525642] Re: gnome-keyring does not start org.freedesktop.secrets

Sebastien Bacher <email address hidden> writes:

> Not sure that this interface is supposed to be working yet

It does. I'm testing my client towards.

Best regards, Michael.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gnome-keyring - 2.29.90git20100218-0ubuntu2

---------------
gnome-keyring (2.29.90git20100218-0ubuntu2) lucid; urgency=low

  * debian/gnome-keyring.install:
    - install the dbus instrospection files there (lp: #525645)
  * debian/gnome-keyring.preinst:
    - clean the autostarts on upgrade the components changed
  * debian/patches/03_use_in_xfce.patch:
    - run the autostart under xfce too (lp: #525642)
 -- Sebastien Bacher <email address hidden> Mon, 22 Feb 2010 16:32:31 +0100

Changed in gnome-keyring (Ubuntu):
status: New → Fix Released
Revision history for this message
Sebastien Bacher (seb128) wrote :

ups, listed the wrong bug number

Changed in gnome-keyring (Ubuntu):
status: Fix Released → New
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: https://bugzilla.gnome.org/show_bug.cgi?id=611002

Changed in gnome-keyring (Ubuntu):
status: New → Triaged
Changed in gnome-keyring:
importance: Undecided → Unknown
status: New → Unknown
Changed in gnome-keyring:
status: Unknown → New
Changed in gnome-keyring:
status: New → Fix Released
Revision history for this message
Sebastien Bacher (seb128) wrote :

the bug has been fixed upstream now in GNOME

Changed in gnome-keyring (Ubuntu):
status: Triaged → Fix Committed
Revision history for this message
Haggai Eran (haggai-eran) wrote :

Hi,

I tried adding the missing .service file mentioned in the upstream bug report myself, but I'm still having trouble using the keyring. If I run seahorse for example with the new service file in place, I get this error:
> ** Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
>
> ** (seahorse:11951): WARNING **: couldn't get default keyring name: Error communicating with gnome-keyring-daemon

This only happens when I use a password-less login.
If by the way I kill the gnome-keyring-daemon process started on login, then everything works fine.

Changed in gnome-keyring (Ubuntu Lucid):
assignee: nobody → Sebastien Bacher (seb128)
importance: Undecided → Low
status: New → Fix Committed
description: updated
Revision history for this message
Sebastien Bacher (seb128) wrote :
Revision history for this message
Ryan Daly (daly-ctcnet) wrote :

I get the same error when starting seahorse, and I'm not using password-less login. Is this the same issue reported here?

Revision history for this message
Ryan Daly (daly-ctcnet) wrote :

My fault!! My PAM configuration was incorrect. Once I corrected PAM, all began to work properly. Sorry for any confusion.

Revision history for this message
Colin Watson (cjwatson) wrote : Please test proposed package

Accepted into lucid-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

tags: added: verification-needed
Revision history for this message
Ricardo Correia (wizeman) wrote :

I was having the same problem and the proposed package worked for me.

Martin Pitt (pitti)
tags: added: verification-done
removed: verification-needed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gnome-keyring - 2.92.92.is.2.30.1-0ubuntu2

---------------
gnome-keyring (2.92.92.is.2.30.1-0ubuntu2) lucid-proposed; urgency=low

  * debian/patches/90_git_dbus_activation_service.patch,
    debian/patches/91_git_correct_service.patch:
    - git changes to install the dbus activation service correctly (lp: #525642)
  * debian/patches/92_git_correct_variable_checking.patch:
    - git change to fix a variable checking issue
  * debian/patches/99_autoreconf.patch:
    - update makefile for the previous changes
 -- Sebastien Bacher <email address hidden> Fri, 21 May 2010 10:46:02 +0200

Changed in gnome-keyring (Ubuntu Lucid):
status: Fix Committed → Fix Released
Revision history for this message
Martin Pitt (pitti) wrote :

copied to maverick, too

Changed in gnome-keyring (Ubuntu):
status: Fix Committed → Fix Released
Changed in gnome-keyring:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.