After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 711489 - Gnome-keyring-daemon still use the old path
Gnome-keyring-daemon still use the old path
Status: RESOLVED NOTABUG
Product: gnome-keyring
Classification: Core
Component: general
3.8.x
Other Linux
: Normal normal
: ---
Assigned To: GNOME keyring maintainer(s)
GNOME keyring maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2013-11-05 14:24 UTC by dirk.seynol
Modified: 2014-03-06 20:05 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description dirk.seynol 2013-11-05 14:24:55 UTC 
A few days back i've made a fresh Ubuntu Saucy installation from a netinstall, then upgraded it to Trusty.
Looking at auth.log, i've found this error logged:
Oct 30 09:55:40 dev32 gnome-keyring-daemon[1549]: Gkm: using old keyring directory: /home/oem/.gnome2/keyrings

This installation is sharing a single /home with 2 other partitions distro (ubuntu versions).

As per https://git.gnome.org/browse/gnome-keyring/commit/?id=747b37bbd8fb82830524c8603f6fcf1ceae605dc
so it seems there is no migration done if your userconfig already has the old directory. (which is the case)

firstly reported on launchpad: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1246232
Comment 1 Sebastien Bacher 2013-11-05 15:06:05 UTC 
Not sure that's worth a warning, if that's a situation that should be fixed maybe gnome-keyring should do a migration on update?
Comment 2 Stef Walter 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.