This bug no longer exists for me under Feisty final. Can anyone else who
was experiencing this bug confirm?
--
after resume, networkmanager reprompts for WPA key
https://bugs.launchpad.net/bugs/92032
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
I can confirm. I have re-enabled libpam-keyring, and it's working fine
again. This was caused by the decision upstream to lock the keyring on
resume, which has been reverted (or so I understand).
You can close this bug.
--
after resume, networkmanager reprompts for WPA key
closing as requested by reporter.
** Changed in: gnome-keyring (Ubuntu)
Status: Unconfirmed = Rejected
--
after resume, networkmanager reprompts for WPA key
https://bugs.launchpad.net/bugs/92032
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
closing as requested by reporter.
** Changed in: network-manager (Ubuntu)
Status: Unconfirmed = Rejected
--
after resume, networkmanager reprompts for WPA key
https://bugs.launchpad.net/bugs/92032
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
Yes, I did it according to the Debian readme. I only added the @include
to the gdm module.
This used to work until 2 days ago. I tried to revert to gnome-keyring
0.7.92, but that didn't solve the problem. Any other things I can try?
--
after resume, networkmanager reprompts for WPA key
It seems the default keyring can not be accessed after resume. If I
start gnome-keyring-manager after resume, the default' keyring is
locked. If I click on that keyring, I get an error dialog saying that
the keyring can not be accessed. If I log out and back in again, the
keyring is accessible
maybe related to https://launchpad.net/gnome-keyring/+bug/83326
** Also affects: gnome-keyring (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
after resume, networkmanager reprompts for WPA key
https://launchpad.net/bugs/92032
--
ubuntu-bugs mailing list
I retested with pam-keyring enabled. I get the same error (screenshot
attached shows the prompt for the WPA key, the gnome-keyring-manager
with locked 'default' keyring and the error dialog when trying to access
that keyring).
To verify the link to #83326, I looked with ps ax for gnome-keyring-
If I manually kill and restart the gnome-keyring-daemon, the keyring
becomes available again.
--
after resume, networkmanager reprompts for WPA key
https://launchpad.net/bugs/92032
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
libpam-keyring specifically is not compatible in combination with the
gnome-screensaver PAM module.
libpam-keyring spawns a new instance of gnome-keyring-daemon on each
instance.
--
after resume, networkmanager reprompts for WPA key
https://launchpad.net/bugs/92032
--
ubuntu-bugs mailing list
aha, interesting. What are my options? Can I disable the screensaver pam
module (in which I'm not interested at all), and get a working pam-
keyring?
--
after resume, networkmanager reprompts for WPA key
https://launchpad.net/bugs/92032
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
You installed libpam-keyring. Did you follow the README.Debian? If so,
which modules did you modify?
--
after resume, networkmanager reprompts for WPA key
https://launchpad.net/bugs/92032
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
12 matches
Mail list logo
