Still seeing that 'LOG_NOTICE' priority logged into journalctl on vivid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1246232
Title: gnome-keyring-daemon still use the old path Status in GNOME keyring services: Invalid Status in gnome-keyring package in Ubuntu: Triaged Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-keyring/+bug/1246232/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
