| 2013-10-30 09:29:36 |
dino99 |
bug |
|
|
added bug |
| 2013-10-30 09:31:01 |
dino99 |
tags |
|
bot-stop-nagging i386 trusty |
|
| 2013-10-30 09:32:53 |
dino99 |
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. |
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.
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 |
|
| 2013-10-30 09:33:05 |
dino99 |
tags |
bot-stop-nagging i386 trusty |
bot-stop-nagging i386 saucy trusty |
|
| 2013-10-30 09:39:28 |
dino99 |
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.
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 |
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
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 |
|
| 2013-10-30 09:44:01 |
dino99 |
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
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 |
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 |
|
| 2013-11-05 13:57:09 |
Sebastien Bacher |
gnome-keyring (Ubuntu): importance |
Undecided |
Low |
|
| 2013-11-05 14:26:48 |
dino99 |
bug watch added |
|
https://bugzilla.gnome.org/show_bug.cgi?id=711489 |
|
| 2013-11-05 15:05:08 |
Sebastien Bacher |
gnome-keyring (Ubuntu): status |
New |
Triaged |
|
| 2013-11-05 15:05:29 |
Sebastien Bacher |
bug task added |
|
gnome-keyring |
|
| 2013-11-06 16:13:02 |
Bug Watch Updater |
gnome-keyring: status |
Unknown |
New |
|
| 2013-11-06 16:13:02 |
Bug Watch Updater |
gnome-keyring: importance |
Unknown |
Medium |
|
| 2014-03-06 23:02:56 |
Bug Watch Updater |
gnome-keyring: status |
New |
Invalid |
|
| 2014-03-17 07:34:20 |
Karma Dorje |
bug |
|
|
added subscriber Karma Dorje |
| 2014-12-19 09:37:25 |
dino99 |
summary |
[trusty] gnome-keyring-daemon still use the old path |
gnome-keyring-daemon still use the old path |
|
| 2014-12-19 09:37:53 |
dino99 |
tags |
bot-stop-nagging i386 saucy trusty |
bot-stop-nagging i386 trusty utopic vivid |
|
| 2015-03-10 07:44:00 |
dino99 |
bug watch added |
|
https://bugzilla.gnome.org/show_bug.cgi?id=613644 |
|
