Displays repeated keyring dialogs on resume from suspend and login

Does the problem arise on updated flight 5 with nm 0.6?

Yes, all updates applied (March 29), still same problem.

Anders

N-M 0.6.2?

Yes, latest nm. Just tried the same sequence. I had to type the keyring password twice this time.

Anders

Please do the following to debug this:
$ sudo -s
# /etc/dbus-1/event.d/25NetworkManager stop
# NetworkManager --no-daemon > nm.log

Wait for it to connect again, then suspend your computer and resume it. After it's connected again, attach the nm.log file to this bug.

You can restore "normal" operation afterwards by stopping NM with ^C then running /etc/dbus-1/event.d/25NetworkManager start

I have also experienced this, but after a resume from hibernate on a Dell Latitude D610.

This patch fixes the problem for me (I get it when starting gnome), it is stolen from upstream CVS, and altered to apply to the ubuntu package.

Using nm 0.6.2-0ubuntu7 I'm able to suspend and resume my laptop and nm re-connects just fine to my WEP wlan without prompting for a password.

It might be fixed for you, but this bug still exists for me.

On 6/9/06, hackel <email address hidden> wrote:
>
> Using nm 0.6.2-0ubuntu7 I'm able to suspend and resume my laptop and nm
> re-connects just fine to my WEP wlan without prompting for a password.
>
>

I'm experiencing this bug with network-manager 0.6.2, but it occurs immediately after login after booting the computer fresh (i.e., not from suspend or hibernate). Unless I can quickly fill in the first keyring login request, network-manager will pop up up to two more keyring login requests.

If I fill in the password on one of the windows, but click "Deny" or simply the close button on the other windows, network-manager then displays the manual dialog for encryption, and if I click cancel on it, network-manager stops connecting to my network. If network-manager was already connected to my network (if I wait for it to connect before closing the other dialogs), it drops the connection.

This is on a custom Compal HEL-80 whitebook. See http://www.powernotebooks.com/specs/PowerPro/l8-15.php for specifications.

I experience exactly what Chris experiences.

I am affected by this when first logging into GNOME after a fresh boot. As soon as the desktop appears I get two (sometimes three) overlapping 'Unlock keyring' dialog boxes. I have to cancel them both and manually select my network, after which the unlock dialog reappears (once this time) and then everything works fine.

I only get this on resume when the machine has been suspended or hibernated long enough for the gnome-keyring session to have expired.

I'm on a Dell Latitude D620 with the ipw3945 chipset, and an up-to-date Dapper.

Hi,

I will be away from the office until 10/2/2006. I will reply to your message at that time.

Thanks,
David

Hi,

I will be away from the office until 10/2/2006. I will reply to your message at that time.

Thanks,
David

I've got the same problem: multiple keyring prompts when I login to Gnome within the range of any AP for which I have a stored password.

I captured the output of NetworkManager and have attached the log. This isn't a transient bug for me--it happens every single time I turn on my computer. It's happened with 0.6.2 (Dapper) and now 0.6.3 (Edgy). If there's anything else I can do to help resolve this issue, please contact me.

Hi,

I will be away from the office until 10/2/2006. I will reply to your message at that time.

Thanks,
David

This reliably occurs in 0.6.3 at login for me, at the guy above. I have re-opened a bug upstream.

Does this still occur for anyone coming back from suspend/resume?

Glad I found this bug. I get three prompts every time I log in. It happened in dapper and I just did a fresh install for edgy and can confirm the same behavior. I will be happy to provide any additional info.

Actually, on Edgy, it prompts me twice instead of three times. So it has improved...

I can also confirm this bug. I always get simultaneously prompted twice for my keyring password at log-in. My wireless chipset is an ipw2200.

I have restarted my computer twice after todays (or yesterdays) updates and it appears to only pops once. I don't know if this is just a circumstance or if it was fixed. Is this consistent with anyone else's experience?

Glad to hear it's fixed for you, Clark, but it's still broken for me. I'm current on Edgy, rebooted, and got the usual two prompts.

Still getting between one to three prompts, here. Haven't seen any updates to this package in Dapper.

Ok, I lied. False alarm. I just got my two prompts back. Sure was nice those two logins...

Guys, this is NOT a message board. If you have any NEW, relevent information to provide, such as a backtrace or other debugging out put, then by all means post it, but please do not use this bug report to have a conversation about it, or simply repeate all the problems you're having over and over. Each email you send goes out to everyone watching this bug, and it really gets annoying.

From what I understood several months ago, the NetworkManager team is aware of this issue and is working on a fix upstream. They are working on an authentication scheme that doesn't use gnome-keyring. At this point, there is nothing we can do, so please just be patient. We all know that the problem exists. I resorted to configuring my wireless manually for now, using /etc/network/interfaces and it works beautifully.

Thanks, I'm sure we would all appreciate it. And thanks to the NetworkManager developers and packagers for getting things straightened out!

I've found a fix for my version of this bug. I have an ipw2200, and I used to get two simultaneous keyring prompts after logging in when nm-applet tries to automatically connect to a preferred, secure network. I installed the network-manager and network-manager-gnome 0.6.4 packages from debian unstable, and they seem to have fixed the problem.

As far as I can remember, I think this bug was fixed upstream (I have a feeling I saw it in the changelog, though I can't find it now).

Please re-open if this is still happening on latest Feisty.

I just checked that it is not fixed in Edgy. I am not currently running Feisty.

Sorry, I thought that I was responding to another bug. I haven't checked this in Edgy (or Feisty). Again, sorry for the confusion.

Just to make things clear. After installing the beta this bug no longer presents itself.

Still asking for a password, many many times. Gutsy.

Sorry for confusion - it asks for WEP key, not keyring password (it is separate bug, already filed). Please ignore my last "me too" comment here.

I found to reproduce this bug by 2 ways:

1. When not connected to a secured (without password saved) wifi, try to connect to the secured wifi (do not type password or do anything), go take a rest, unlock computer and se a lot of nm-applet dialog.

2. When not connected to a secured (without password saved) wifi, try to connect to the secured wifi (do not type password or do anything); repeat from the begining.

To fix this bug I give the following suggestions:

Simple fix: On connect event: If keyring-dialog is visible, do nothing, else if connection needs password and password is not saved, display keyring-dialog.

This bug needs to be reopened because there are new reports of the problem.

Update. The bug has been fixed, but not in Precise.