Bug 874670 - Default keyring does not get created
Summary: Default keyring does not get created
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: libsecret
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kalev Lember
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 874640
TreeView+ depends on / blocked
 
Reported: 2012-11-08 15:47 UTC by Allan Day
Modified: 2012-12-28 23:14 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-12-07 04:24:05 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
screenshot (942.99 KB, image/png)
2012-11-08 15:58 UTC, Allan Day
no flags Details


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 688165 0 Normal RESOLVED Default keyring does not get created 2020-03-27 14:44:01 UTC

Description Allan Day 2012-11-08 15:47:31 UTC
Testing Fedora 18 Beta TC7 as a live system user:

1. Added my Facebook account to online accounts
2. It indicated that I had successfully added the account, and that Chat was ON
3. I opened Empathy, which showed progress for a while
4. Then I got an "Authentication failed" info box in Empathy
5. I went back to GNOME Online Accounts and there was a yellow bar reading "Expired credentials. Please log in again.    [Log In]
6. I pressed Log In, entered my password in the dialog and pressed OK.
7. The result - a dialog reading "Error logging into the account. Failed to store credentials in the keyring".

Comment 1 Allan Day 2012-11-08 15:58:54 UTC
Created attachment 640900 [details]
screenshot

Comment 2 Debarshi Ray 2012-11-12 12:29:32 UTC
The liveCD does not have a default keyring (ie. SECRET_COLLECTION_DEFAULT). libsecret / gnome-keyring should create a default keyring if none exists when an application tries to store something in it.

Currently that is not happening.

$ echo "foo" | secret-tool store --label=Blah attribute value
** Message: Remote error from secret service: org.freedesktop.Secret.Error.NoSuchObject: The '/org/freedesktop/secrets/aliases/default' object does not exist secret-tool: The '/org/freedesktop/secrets/aliases/default' object does not existrpm -q libsecret

Relevant versions:
libsecret-0.11-1
gnome-keyring-3.6.1-1

Comment 3 Debarshi Ray 2012-11-12 12:34:24 UTC
Reassigning to libsecret after talking to stefw on #gnome-os:
<stefw> ok, could you file a bug? and i'll try and reproduce
<stefw> probably against libsecret

Comment 4 Debarshi Ray 2012-11-21 18:10:27 UTC
Now that this has been fixed upstream we should backport the patches for the F18 package. I have a package with the fixes that I have been using for some time. Should I push and build it for F18?

Kalev?

Comment 5 Kalev Lember 2012-11-21 19:20:28 UTC
Sure, but submit a separate bodhi update, please. Too late to include this in the GNOME 3.6.2 megaupdate.

Would be nice to have a fix for this on the live media.

Comment 6 Fedora Update System 2012-11-23 12:40:35 UTC
libsecret-0.12-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/libsecret-0.12-1.fc18

Comment 7 Fedora Update System 2012-11-23 19:53:20 UTC
Package libsecret-0.12-1.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing libsecret-0.12-1.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-18903/libsecret-0.12-1.fc18
then log in and leave karma (feedback).

Comment 8 Fedora Update System 2012-12-07 04:24:08 UTC
libsecret-0.12-1.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Thorsten Scherf 2012-12-17 08:07:35 UTC
I still see this problem with latest f18 package, when I try to add my google account to the default keyring (didn't test with any other account).

Comment 10 Douglas Furlong 2012-12-28 23:14:14 UTC
I've noticed this problem as well.

Upgraded from Fedora 17 -> Fedora 18 using fedup.

On fedora 17 was using fingerprint scanner to log in.

After upgrading, looked in seahorse and could see all of my passwords (had to reset the goa passwords for chat to work again, credentials apparently had expired).

I also noticed that the fingerprint scanner was not working.

Reconfigured the finger print scanner, on re-logging in, got an error stating it could not unlock the keyring (not requested to have it unlocked with a password), and looking in seahorse for a list of passwords, it was empty.


Note You need to log in before you can comment on or make changes to this bug.