Bug 437756

Summary:	long pause after wlan card inserted; enable does not work first time.
Product:	[Fedora] Fedora	Reporter:	Greg <greg.b.redhat>
Component:	NetworkManager	Assignee:	Dan Williams <dcbw>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	low
Version:	8	CC:	dcbw, wtogami
Target Milestone:	---	Flags:	dcbw: needinfo?
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-01-09 06:12:15 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 Greg 2008-03-17 09:19:03 UTC

Description of problem:
NetworkManager seems to wait unduly long before allowing the user to enable
Wireless, and when the option is made available, it does not work the first time.

Version-Release number of selected component (if applicable):
NetworkManager-0.7.0-0.6.7.svn3235.fc8

How reproducible:
always

Steps to Reproduce:
1. These steps begin with a working and active wlan connection.
2. Right click on KDE network manager applet to disable wireless
3. Remove wireless card from laptop
4. Re-insert wireless card into laptop
  
Actual results:
It takes about a minute for the "Enable Wireless" option to appear on the popup
menu on the KDE nm applet icon on the taskbar.
Once it does appear, user must enable wireless, then disable, then enable again
before NetworkManager begins reconnecting to the network.

Expected results:
Option should appear immediately (via dbus notification?)
Option should work the first time

Additional info:
Atheros AR5212 based card.  Problem occurs whether ath5k or madwifi is used.

Comment 1 Dan Williams 2008-03-17 20:28:57 UTC

Can you get some logs from /var/log/messages?  I've seen this at various times,
sometimes it takes a long time for HAL (possibly due to driver/udev delays) to
actually emit the event.

Comment 2 Bug Zapper 2008-11-26 10:11:36 UTC

This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '8'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 8's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 8 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Bug Zapper 2009-01-09 06:12:15 UTC

Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.