Bug 8580 - WiFi won't disconnect
Summary: WiFi won't disconnect
Status: RESOLVED DUPLICATE of bug 8228
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-02 18:50 CET by William Kenney
Modified: 2013-01-13 16:48 CET (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments
In and out of WiFi range testing (6.42 KB, text/plain)
2013-01-08 01:04 CET, William Kenney
Details

Description William Kenney 2013-01-02 18:50:39 CET
Feel free to modify the description of this bug.

Do not connect a ethernet wired network connection
Ensure there are no active network connections, Wired or Wireless
Initially set up MCC -> Network & Internet -> Network Center
Select Wireless (Wi-Fi)
Select and set up a WiFi connection
Configure (Check the box) the selected WiFi connection such that it starts at boot
Connect to that service.
Ensure that it works.
Turn the laptop off and walk it out of range of the initial WiFi connection
Turn laptop on and attempt to connect to any WiFi service managed or not.
It won't work. You get a blank screen for any other WiFi services.

Repeat the above process but ensure in the WiFi setup that the connection does not start at boot.
You will now have to manually connect to a WiFi service but it will work everywhere.

It appears to me that the WiFi connection is not turned off at power down
and when the laptop is powered up again it assumes the connection is there
and does not offer a listing of available WiFi connections. The "Disconnect"
button function is not offered in the WiFi connection setup.
Comment 1 William Kenney 2013-01-08 01:04:20 CET
Created attachment 3334 [details]
In and out of WiFi range testing
Comment 2 Derek Jennings 2013-01-10 23:12:28 CET
Bill.
Following the qa meeting this evening I did some more testing.

For me it was not 'start at boot' that worked around the issue. It was 'access point roaming'.

As Luc mentioned in his original post on 8228 it is only when wpa_supplicant is running that draknetcenter fails to display the networks.

With roaming disabled wpa_spplicant is not running as you can test because 
wpa_cli -i wlan0 scan_results will return an "unable to connect" message.

With roaming enabled (and after a reboot) wpa_supplicant will be running and draknetcenter is empty.

If so then it is not so serious since the default setting is roaming disabled, but it still needs fixing.

CC: (none) => derekjenn

Comment 3 Derek Jennings 2013-01-13 16:48:05 CET
Marking as duplicate of 8228

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

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE


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