Bug 469558 - Wireless is enabled but NetworkManager thinks it is disabled on resume since it was disabled before suspending
Wireless is enabled but NetworkManager thinks it is disabled on resume since ...
Status: CLOSED DUPLICATE of bug 471435
Product: Fedora
Classification: Fedora
Component: NetworkManager (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Dan Williams
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-11-02 07:59 EST by Hedayat Vatankhah
Modified: 2008-11-17 14:04 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-11-17 14:04:34 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Hedayat Vatankhah 2008-11-02 07:59:19 EST
Description of problem:
If I disable Wireless using NetworkManager, and then suspend my system, On resume NetworkManager still thinks that wireless is disabled, but my wireless light is on and it is working. But it should be still disabled.

How reproducible:

Steps to Reproduce:
1. Right click on NetworkManager applet's icon and uncheck Enable Wireless. It should turn off wireless (it turns off my wireless's light)
2. Suspend the system
3. Resume the system. You'll see that network manager applet still thinks that wireless is disabled. But my wireless light turns on after resume.
Actual results:
After resume, my wireless card is active.

Expected results:
It should be still inactive after resume

Additional info:
Maybe it is a kernel bug :(
Comment 1 Dan Williams 2008-11-17 14:04:34 EST
NetworkManager sets the device "down", which means that wifi traffic will not be sent or received, and the card is not associated with an access point.  Acutally turning the device off requires HAL rfkill support (which is what NM would use to disable the wireless if it was there).

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

Note You need to log in before you can comment on or make changes to this bug.