gnome-keyring-daemon still use the old path

[dino99]

With Trusty i386 logged on gnome-shell, i get that auth.log error :

Oct 30 09:55:40 dev32 gnome-keyring-daemon[1549]: Gkm: using old keyring directory: /home/oem/.gnome2/keyrings

so it does not know about the actual path that should be : "~/.local/share/keyrings"
In fact , searching "keyrings" or "keyring" via nautilus, only find that old ".gnome2/keyrings" . That's strange as that installation is newly made from scratch via fresh iso.

Meaning: /.local/share/keyrings has not been created.

A few lines later, i get that other (probably related) other error:
gnome-keyring-daemon[1549]: couldn't allocate secure memory to keep passwords and or keys from being written to the disk

package: 3.8.2-0ubuntu3

Note: that issue also exist with Saucy, as it has been known a while back
https://lists.ubuntu.com/archives/ubuntu-users/2013-March/268426.html

[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.

[Sebastien Bacher (seb128)]

https://git.gnome.org/browse/gnome-keyring/commit/?id=747b37bbd8fb82830524c8603f6fcf1ceae605dc states

" * If the new XDG directory doesn't exist, and the old ~/.gnome2/keyrings does exist, then continue to use that"

so it seems there is no migration done if your userconfig already has the old directory

[dino99 (9d9)]

Thanks Sebastien,

reported upstream : https://bugzilla.gnome.org/show_bug.cgi?id=711489

[Sebastien Bacher (seb128)]

thanks

[dino99 (9d9)]

Upstream have declared that 'issue' as invalid:

Stef Walter [gnome-keyring developer] 2014-03-06 20:05:11 UTC
Hmmm, it's not a warning or error, it's a simple LOG_NOTICE priority message:

https://git.gnome.org/browse/gnome-keyring/tree/pkcs11/gkm/gkm-util.c#n160
https://git.gnome.org/browse/gnome-keyring/tree/daemon/gkd-main.c#n293

If someone is interested in working on migration functionality, I wouldn't be
against that.

As vivid still has this logged and seems 'an issue' maybe it should be silenced at least.

[dino99 (9d9)]

Still seeing that 'LOG_NOTICE' priority logged into journalctl on vivid

[dino99 (9d9)]

Some tests have been made at:

https://bugzilla.gnome.org/show_bug.cgi?id=613644