** Changed in: gnome-keyring
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1246232
Title:
[trusty] gnome-keyring-daemon still use the old path
To manage notifications
** Changed in: gnome-keyring
Status: Unknown => New
** Changed in: gnome-keyring
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1246232
Title:
[trusty] gnome
thanks
** Changed in: gnome-keyring (Ubuntu)
Status: New => Triaged
** Also affects: gnome-keyring via
https://bugzilla.gnome.org/show_bug.cgi?id=711489
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
Thanks Sebastien,
reported upstream : https://bugzilla.gnome.org/show_bug.cgi?id=711489
** Bug watch added: GNOME Bug Tracker #711489
https://bugzilla.gnome.org/show_bug.cgi?id=711489
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
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/G
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 di
** Description changed:
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/keyr
