Closing this bug as per your last comment. Thanks!
** Changed in: gnome-screensaver (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu.
https://bugs.launchpad
I cannot reproduce this in maverick anymore and, in fact, it resolved by
itself quite some time ago. I suppose it was on the upgrade to Lucid,
but I do not remember at all, sorry. I guess the bug may be closed.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Can you still reproduce this issue with Ubuntu 10.10 (Maverick)?
** Changed in: gnome-screensaver (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu.
https://bugs.laun
reassigning to gnome-screensaver
** Package changed: gnome-keyring (Ubuntu) => gnome-screensaver (Ubuntu)
** Changed in: gnome-screensaver (Ubuntu)
Status: Incomplete => New
--
gnome-keyring does not grant permissions automatically on resume
https://bugs.launchpad.net/bugs/454404
You rec
Yes, it is in my user's config; therefore, indeed it is not the default.
The file is dated 2008-03-28, however, so the behaviour did change by
itself on the switch to karmic. And in fact, the problem is not that the
keyring is locked (I would even argue that this should be the default,
but this is
changing to new and not confirming, the gconf key schemas is set to
false and my laptop upgrade didn't show a key change nor did it do for
other users apparently since nobody complained about that now, do you
have a value to true for this key in .gconf in your config?
** Changed in: gnome-keyring
Uh? Please note:
1. I did not change this; it is the default value;
2. This did not happen in Hardy, Intrepid or Jaunty (and probably not
before either); the behaviour changed by itself on the upgrade to
karmic;
3. It is IMHO a good idea to lock the keyring on suspend, since it makes
a lot of se
not a bug then bug an user configuration choice
** Changed in: gnome-keyring (Ubuntu)
Status: Incomplete => Invalid
--
gnome-keyring does not grant permissions automatically on resume
https://bugs.launchpad.net/bugs/454404
You received this bug notification because you are a member of Ub
This key is set to true; the key use_screensaver_settings is also set to
true. FWIW, /apps/gnome-screensaver/lock_enabled is also enabled.
Thanks for the attention!
--
gnome-keyring does not grant permissions automatically on resume
https://bugs.launchpad.net/bugs/454404
You received this bug no
Thank you for your bug report, what value do you have for the gconf key
/apps/gnome-power-manager/lock/gnome_keyring_suspend?
** Changed in: gnome-keyring (Ubuntu)
Importance: Undecided => Low
** Changed in: gnome-keyring (Ubuntu)
Status: New => Incomplete
--
gnome-keyring does not gr
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/33860515/Dependencies.txt
--
gnome-keyring does not grant permissions automatically on resume
https://bugs.launchpad.net/bugs/454404
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
11 matches
Mail list logo
