couldn't prepare to write out keyring

[Alessio]

gnome-keyring-daemon can't store password in keyring files
into ~/.gnome2/keyrings/ .keyring files are created, but passwords aren't stored

in /var/log/auth.log when any application try to store a password (nautilus, empathy, evolution, ubuntuone) I can see these log messages:
Oct 14 17:18:56 ktulu gnome-keyring-daemon[15555]: egg_symkey_generate_simple: assertion `iterations >= 1' failed
Oct 14 17:18:56 ktulu gnome-keyring-daemon[15555]: couldn't prepare to write out keyring: /home/alessio/.gnome2/keyrings/login.keyring
Oct 14 17:18:56 ktulu gnome-keyring-daemon[15555]: couldn't unwrap item secret: Internal error

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: gnome-keyring 3.2.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu3
Architecture: i386
Date: Fri Oct 14 20:13:19 2011
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
SourcePackage: gnome-keyring
UpgradeStatus: No upgrade log present (probably fresh install)

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Pedro Villavicencio (pedro)]

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

[kapetr (kapetr)]

Hello.

I have reported in bug :
https://bugs.launchpad.net/ubuntu-sso-client/+bug/745540
(comment #62 and further), but maybe is it duplicate of this one. See there for detailed description please.

If I try to sign-in in my Ubuntu One account in ubuntu one client, I get in /var/log/auth.log:

------
Nov 1 12:40:36 hugo-A7V400-MX gnome-keyring-daemon[2849]: egg_symkey_generate_simple: assertion `iterations >= 1' failed
Nov 1 12:40:36 hugo-A7V400-MX gnome-keyring-daemon[2849]: couldn't prepare to write out keyring: /home/hugo/.gnome2/keyrings/login.keyring
-------

So here is missing third log entry.

This bug is in "fix released" state - please - what does it mean for me ?
When will I be able to use Ubuntu one in Ubuntu 11.10 ?

[Alessio (alessio)]

no, this is not a duplicate of bug #745540 as this one is not related only to ubuntuone but breaks every applications that use gnome-keyring

the Roman Yepishev ppa (ppa:rye/ubuntuone-support) reported on bug #745540 on comment #69 have fixed gnome-keyring packages that seems correclty work

[Sebastien Bacher (seb128)]

The fix is on http://git.gnome.org/browse/gnome-keyring/commit/?h=gnome-3-2&id=71bdb5dc967ec99b3b2fe9d5994de7996b4142c5 if somebody wants to backport it

[Launchpad Janitor (janitor)]

This bug was fixed in the package gnome-keyring - 3.2.2-0ubuntu1

---------------
gnome-keyring (3.2.2-0ubuntu1) precise; urgency=low

  * New upstream release
    - Use g_random_int_range() for pseudo-random hash iteration
      count. (LP: #874501)
    - Fix problem with 'unsafe storage' prompt deadlocking
    - Remove XFCE & LXDE from OnlyShowIn for autostart files
    - Return password results with the most recent result first
    - Make clear source of warnings from the rpc module
 -- Ken VanDine <email address hidden> Mon, 14 Nov 2011 09:57:13 -0500

[Chris Halse Rogers (raof)]

I've rejected the gnome-keyring package from oneiric-proposed as it's got a higher version number than the version in Precise. Please upload it again with a version lower than the one in the development release ;). (3.2.2-0ubuntu0.1 should do).

[Clint Byrum (clint-fewbar)]

I'm a bit concerned about this change:

+commit bc01094411d724470ebda56d4515f45760f8d008
+Author: Stef Walter <email address hidden>
+Date: 2011-10-20
+
+ secret-store: Return results with the most recent result first
+
+ * This is to help programs that have erroneusly stored more than
+ one password with given attributes, and keep finding the old one.
+ * The most recent one is usually correct.
+
+ pkcs11/secret-store/gkm-secret-search.c | 79 +++++++++++++----------
+ pkcs11/secret-store/tests/test-secret-search.c | 73 ++++++++++++++++++++++
+ 2 files changed, 118 insertions(+), 34 deletions(-)
+

And the lack of a "regression potential" attached to this bug. I'd like to see some comments on what the danger is here, as to me, this seems like a clear change in the way it works, and might cause regressions for applications which don't expect them to be in this order.

Leaving it in the queue for now, but can somebody please add a full SRU justification to the bug description?

https://wiki.ubuntu.com/StableReleaseUpdates

[Ken VanDine (ken-vandine)]

Unfortunately It is pretty hard to measure the regression potential for this. Applications that could be broken by this change are probably experiencing hard to reproduce bugs themselves. The fact that multiple entries are getting stored would be a bug itself, they wouldn't be depending on that behavior. However, it could break users that are already affected by that kind of bug, we just don't really have a way to measure that.

[dobey (dobey)]

Clint, as Ken suggested, those changes seem acceptible. It seems unlikely that any apps would depend on multiple entries working. And if they are, the app is already broken, I think.

[Martin Pitt (pitti)]

Hello Alessio, or anyone else affected,

Accepted gnome-keyring into oneiric-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!

[Alessio (alessio)]

I tested it with nautilus, empathy, evolution and ubuntuone and seems correctly work, password are correctly stored and I can see them on seahorse

[Launchpad Janitor (janitor)]

This bug was fixed in the package gnome-keyring - 3.2.2-0ubuntu0.1

---------------
gnome-keyring (3.2.2-0ubuntu0.1) oneiric-proposed; urgency=low

  * New upstream release.
    - Use g_random_int_range() for pseudo-random hash iteration
      count. (LP: #874501)
    - Fix problem with 'unsafe storage' prompt deadlocking
    - Remove XFCE & LXDE from OnlyShowIn for autostart files
    - Make clear source of warnings from the rpc module
  * debian/patches/05_revert_order_fix.patch
    - revert upstream fix which always returns most recent keyring result,
      it is hard to verify for an SRU and hard to predict the possibility
      for regression
 -- Ken VanDine <email address hidden> Mon, 28 Nov 2011 14:20:08 -0500