Bug 453926

Summary: Right-clicking nm-applet when keyring opens locks desktop.
Product: [Fedora] Fedora Reporter: simon
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: rawhideCC: dcbw, wtogami
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-10-17 16:07:20 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description simon 2008-07-03 09:38:07 UTC
Description of problem:
On several occasions I have had a problem that when I left click on the
nm-applet icon to see a list of networks, nm can cause the keyring password
prompt to appear.
The combination of both a left click menu and a keyring dialog box causes all
input to be ignored. The keyring dialog normally takes all the input focus,
however I believe the left click menu must somehow conflict with that.

Version-Release number of selected component (if applicable):
NetworkManager 0.7.0-0.9.4.svn3675.fc9.i386

How reproducible:
It's happened quite a few times.

Steps to Reproduce:
1. Have NM in an unassociated state, with keyring locked.
2. Have the wireless scanning/associate start (e.g. by turning on adapter)
3. Leftclick nm-applet to see list of wireless nets.
4. Leave menu open and wait for keyring unlock dialog to open.
5. Keyring dialog opens, prompting for pawssword.
6. Attempt to enter password
  
Actual results:
Move moves, but not keyboard input or mouse clicks are registered. Need to
switch out into console and manually kill the unlock + nm processes.

Expected results:
Expected to be able to enter password and continue.

Additional info:

Comment 1 Dan Williams 2008-10-17 16:07:20 UTC

*** This bug has been marked as a duplicate of bug 353451 ***