[8.10] Selecting "Deny" on the password confirmation does nothing

Bug #290378 reported by b3n87
4
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Binary package hint: network-manager

I have my laptop set up to automaticly log in, when it logs in, a box pops up saying that network manager is requesting premission to access my network key, if I press Deny, it just keeps coming back up.

Revision history for this message
b3n87 (benhellyer) wrote :

In-fact, nothing seems to work until I have entered the correct password for "Unlock Key" window. Thinking about it now, I dont think its network-manager, its Seahorse.

Evolution was asking for a password to unlock a key too.

Revision history for this message
Elias K Gardner (zorkerz) wrote :

I believe what is happening is that network-manager is asking for the password over and over again as it tries to connect but "Deny" makes seahorse refuse the request. I agree it would be nice if seahorse could communicate to network-manager saying you request has been denied don't ask again or if seahorse ignored further requests after being denied for a time.

There are ways around this you can set your default keyring so that it has no password. I think you access this through 'system->accessories->passwords and encryption keys' then 'edit->preferences' and go to the 'Password Keyrings' tab. Here there is a button 'Change Unlock Password'. The default keyring is where network passwords are stored.

I have also heard but not tested that you can right click on the network-manager icon in the notification area and select 'Edit Connections...'. Then find your network and click the 'Edit' button. Here there is a 'system setting' checkbox that if checked you will not be asked for the password. Again I have not tested this method.

Thanks for reporting this. Assuming your problem has been solved I am going to this invalid. If you would still like to report a bug about the 'Deny' button functionality you can change the status back. I that case I think the best thing to do would be to also add seahorse as an affected package. This would then also have to be reported upstream and it likely will fall under the category of wishlist as I think technically both network-manager and seahorse are performing as expected.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

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 is this still an issue for you? Could you try to reproduce the same with Ubuntu 8.10 or 9.04? Thanks in advance.

Changed in network-manager:
status: New → Incomplete
Revision history for this message
b3n87 (benhellyer) wrote :

Hello,

Yes the bug still exists, its if you have gnomes "auto-login" enabled then the bug will exist because it will need you to type the password in to unlock the keys.

If you enable auto login, then reboot, you should be able to produce the same bug.

Revision history for this message
Victor Vargas (kamus) 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.

Revision history for this message
Elias K Gardner (zorkerz) wrote :

I am using Ubuntu 9.10 x86-64. I am also still autologing in. I don't believe I am getting asked for a password to access encrypted networks. Although a different app (gmail-notifier) is asking me for a password to access the keyring it is possible that then negates the need to ask again.

Revision history for this message
Elias K Gardner (zorkerz) wrote :

Ok update. When asked to give permission to access the keyring I have to click deny twice before the dialogue stops returning. At this point everything appears to work fine.

I would still consider this a bug until the user only needs to deny once.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.]

Changed in network-manager (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.