nm-applet asks for keyring password 2 or 3 times during login

[hackel]

After booting and logging in, nm-applet asks for my gnome-keyring password two or sometimes three times right away (there are 3 password dialogs open at the same time). After entering my password x number of times, my wpa connection usually comes up then goes down again. I have to re-select my wireless network from the applet menu to bring it up.

If I only enter my password in the first dialog (and let the other one sit there), then my connection comes up and is usable, but then as soon as I type my password into the second dialog, the connection goes down and I have to bring it up by chosing the connection again from the menu.

I thought perhaps nm-applet was getting launched multiple times. While there is never more than one instance of the applet running, my session file does contain these 3 lines:

./session:3,Program=nm-applet
./session:3,CloneCommand=nm-applet --sm-config-prefix /nm-applet-wJkve5/
./session:3,RestartCommand=nm-applet --sm-config-prefix /nm-applet-wJkve5/ --sm-client-id 1045139245000114031132100000072650008 --screen 0

Indicating (to me, at least) that maybe it's trying to launch it 3 times. I will try with a clean profile and report if I can reproduce this issue.

[hackel (hackel)]

In a clean profile I'm able to log in and am only prompted for my password once. I can't figure out what is wrong. I've tried deleting my keyring, deleting my gconf settings for that network, everything I can think of and nothing works. When I diff what config files I can find between my working and non-working accounts, they are the same. Debugging nm-applet is a bit of a challenge so any advice would be appreciated.

[hackel (hackel)]

After enough playing around with my profile, deleting keyrings and gconf keys, I've finally got nm-applet to only ask for my keyring password once. Unfortunately I have no clue what the actual difference was. The only difference I could find was this gconf key:

/system/networking/wireless/%gconf.xml

<gconf>
        <entry name="scan_method" mtime="1130843086" type="int" value="2">
        </entry>
</gconf>

Which is not present in my new, working configuration. I don't see what this would have to do with gnome-keyring, however, so I'm stumped. I also recreated my keyring (although I'd done that several times and it never made any difference).

Since no one else reported this same problem I'll assume it was some strange, esoteric configuration I had, perhaps from a previous version. If anyone else has this problem, feel free to re-open.

[rael9 (jamesmbaker)]

I have the same problem. I will try taking that entry out of my gconf file and see if it clears up the problem or not.

[rael9 (jamesmbaker)]

No go. I don't even have that entry in the place you specified. It was initially working perfectly when I first upgraded to Dapper and install all the network-manager stuff. It wasn't until a few updates through Synaptic later that it started asking me for the password twice.

[hackel (hackel)]

Confirming based on rael9's report, along with the fact that it happened to me again, after I had fixed the issue by whiping my configuration.

This time it happened to me after my gnome-session was automatically saved prior to an automatic low-power shutdown. I was able to fix it by killing all instances of nm-applet, saving my session, then logging in again. This still doesn't make sense, however, because I never see two instances of nm-applet running when I am prompted for the password twice. Needs to be debugged.

[rael9 (jamesmbaker)]

It somehow seems fixed after doing another upgrade using Synaptic yesterday (4/19/06). I'm not sure what it was that fixed it, but there was a gnome-panel update in there, so that have been it.

[rael9 (jamesmbaker)]

Now it seems intermittent. I got 2 password dialogs on the first startup this morning, 3 the next time, and 1 after that. I'm not sure what happened to mess it up, though I did join another wireless network yesterday. Though I don't see how that would effect it.

[hackel (hackel)]

I don't see how this is a dup of bug #31286. It has nothing to do with suspend/resume, but rather seems to have to do with gnome-session interactions.

[Scott James Remnant (Canonical) (canonical-scott)]

Because the actual interactions are the same, resume just happens to trigger the same behaviour.

Unless you can provide additional information that proves you're not getting the same bug, they should remain duplicates.

[mtkuiken (matt-kuiken)]

The description of this bug matches exactly what I am seeing on my system. It happens every time I log in.

It does not occur when I do a suspend/resume operation, in fact, no password is even asked for after a resume, the network just continues to operate.

What do we need to do to either show that this is a different bug, or help fix this one? I cannot reproduce this bug through the method given in the 'duplicate', so I cannot follow the set of instructions you left for the OP of that problem.

I do not mind needing to enter my password to open the keyring, but needing to get rid of the number of open windows, either by entering the password, or by denying access, and then needing to manually select my network from the list and have the whole connection process repeat is a bug that I'd really rather not live with. I do not trust that the other bug is a duplicate, so while I won't try to remove the duplicate designation on this one, I would appreciate your help in trying to track this one down. If they truly are duplicates, then we'll be finding the other at the same time.

-Matt

[Scott James Remnant (Canonical) (canonical-scott)]

Trace the process through the source code that yields the multiple dialogs and attach the results to the upstream portion of this bug.