nm-applet tries to unlock the keyring (asks for password) on resume. Just after the unlock screen, whereas network is already up

[Id2ndR]

Release : Gutsy

Steps :
- Connect to a secured wireless network, and use gnome keyring to store the key
- Suspend, and resume
- Unlock the screen (make sure that you type the password in the lock screen ; bug #153544 explain the trouble)
- Don't enter the password required by nm-applet (most of the time, not always), and look at the two green round of the applet. Try to ping google to see that you connectivity is OK.

Expected behavior :
nm-applet should not ask password whereas it has already connect the network.

[Id2ndR (id2ndr)]

This look like bug #81965 but is not the same as nm-applet ask only one time, and only on resume.

[tiwag (tiwag-gmx)]

i can confirm this bug, get exactly the same behaviour (Gutsy on Dell D820 laptop)
brgds, tiwag

[tiwag (tiwag-gmx)]

in most cases i don't get a working wireless network connection,
if i don't reenter the password in the keyring manager,
but after reading your bugreport i waited a few times a few minutes,
and it did really connect once after some minutes.

but why should i have to enter my password again,
when i already entered the password in the LOCK-screen dialog ?

it seems that the password entered to the lock-screen dialog
after resume from hibernation (or suspend S3) isn't used
in the same way as when logging on by GDM login screen dialog.

after GDM login i never have to reenter the keyring-password again,
(using same passwords for user-login and keyring)
NM is always able to connect to the wireless network.

problem is only after screen-unlock after hibernation or suspend.

thanks, brgds, tiwag

[tiwag (tiwag-gmx)]

don't know if this is an important information, but for the records:

Dell D820, Ubuntu 7.10 Gutsy, installed from alternate CD,

wireless Intel Pro Wireless using the ipw3945 restricted driver,

wireless network is using WPA2/TKIP (only one profile saved)

[Tormod Volden (tormodvolden)]

Seeing the same here, with secured wireless. Sometimes I can just hit escape, and things work fine, other times I really have to enter the password.

[KraetziChriZ (christian.b)]

Can confirm this. Fix would be fine :/

[ethanay (ethan-y-us)]

Dell XPS m1330
iwl3945
Hardy 8.04 w/latest

after resume from suspend w/gnome keyring remaining unlocked: network manager asks for access to default keyring after successful connect to secure wireless network is established. i believe the standard behavior (that I have experienced in the past) is to ask for the password to access the network key before the connection is established.

this means that for some reason network manager seems to have access to the network key but still asks for permission to do something it has already done?

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

 Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

[usatrooper (usatrooper)]

I've got the same problem with Ubuntu 8.10 at startup-when I hafta connect to wireless net, and when I go to receive e-mail, evolution asks for the default keyring also. I'm on a Gateway Laptop with the built-in wireless, the wireless is connected to my DSL modem.

[Victor Vargas (kamus)]

Since this report have a long time without activity, could you check (if is possible) in latest version included in Karmic if this issue is still happening? Thanks in advance.

[ethanay (ethan-y-us)]

This has not been an issue for me on a fresh install of 9.10....I am
asked only once per session for the keyring password.

On Fri, Nov 20, 2009 at 11:34 AM, Kamus <email address hidden> wrote:
> Since this report have a long time without activity, could you check (if
> is possible) in latest version included in Karmic if this issue is still
> happening? Thanks in advance.
>
> --
> nm-applet tries to unlock the keyring (asks for password) on resume. Just after the unlock screen, whereas network is already up
> https://bugs.launchpad.net/bugs/155373
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “network-manager” package in Ubuntu: Incomplete
>
> Bug description:
> Release : Gutsy
>
> Steps :
> - Connect to a secured wireless network, and use gnome keyring to store the key
> - Suspend, and resume
> - Unlock the screen (make sure that you type the password in the lock screen ; bug #153544 explain the trouble)
> - Don't enter the password required by nm-applet (most of the time, not always), and look at the two green round of the applet. Try to ping google to see that you connectivity is OK.
>
> Expected behavior :
> nm-applet should not ask password whereas it has already connect the network.
>

[Victor Vargas (kamus)]

@ld2ndR, please could you check if this issue is still affecting you in latest ubuntu Karmic version?. Thanks in advance

[tiwag (tiwag-gmx)]

Sorry i can't

i'm no longer using Ubuntu because there were too much troubles with
standby / resume

Windows 7 does the better job for me now.

brgds,
tiwag

2010/1/6 Kamus <email address hidden>:
> @ld2ndR,  please could you check if this issue is still affecting you in
> latest ubuntu Karmic version?. Thanks in advance
>
> --
> nm-applet tries to unlock the keyring (asks for password) on resume. Just after the unlock screen, whereas network is already up
> https://bugs.launchpad.net/bugs/155373
> You received this bug notification because you are a direct subscriber
> of the bug.
>
>

[Id2ndR (id2ndr)]

This has been fixed a long time ago now.