After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 341297 - displays repeated keyring dialogs on resume from suspend
displays repeated keyring dialogs on resume from suspend
Status: RESOLVED FIXED
Product: NetworkManager
Classification: Platform
Component: general
0.6.6
Other All
: Normal normal
: ---
Assigned To: Dan Williams
Dan Williams
: 343404 359532 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-05-10 18:36 UTC by Scott James Remnant
Modified: 2007-12-05 22:28 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Scott James Remnant 2006-05-10 18:36:32 UTC
Please describe the problem:
From: https://launchpad.net/distros/ubuntu/+source/network-manager/+bug/31286

Booted with wired network connected. Wireless network not activated during this
session. Pressed the Shutdown toolbar icon and selected Suspend. Saw that the
"Gnome keyring" dialog popped up just before the system went to sleep. On
resume, there were at least 5 pending "Gnome keyring" dialogs. After having
typed my password in each of these, the system went momentarily to sleep and
woke up within a couple of seconds by itself (5 sec?). After the last
password-suspend-resume cycle, the system is working perfectly.

Steps to reproduce:


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Scott James Remnant 2006-05-10 18:44:24 UTC
Note that this could be a general problem with NM asking for the passphrase multiple times; in Ubuntu suspend generally means that the driver has been unloaded and then loaded again.
Comment 2 Dan Williams 2006-05-28 20:22:43 UTC
Should be fixed in CVS HEAD and also on the STABLE branch.
Comment 3 Rémi Cardona 2006-07-21 13:07:10 UTC
*** Bug 343404 has been marked as a duplicate of this bug. ***
Comment 4 Dan Williams 2007-12-05 22:28:23 UTC
*** Bug 359532 has been marked as a duplicate of this bug. ***