State of Switch On Wi-Fi button is not consistent (with patch)
Bug #1232521 reported by
John C. Peterson
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
wicd |
New
|
Undecided
|
Unassigned | ||
wicd (Debian) |
Fix Released
|
Unknown
|
|||
wicd (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Version: 1.7.2.4 (wicd-gtk package from Debian Jessie)
The "state" of the "Switch Off/On Wi-Fi" button in the gtk gui is not consistent with the actual power OFF/ON state of the wireless card.
For example, I turned the power state of the wireless card to ON with the Fn+F2 hotkey and verified the state with rfkill. After starting the wicd-gtk gui, the button displayed is "Switch On Wi-Fi" when it should be "Switch Off Wi-Fi" since it's ALREADY powered on!!!
It appeared to me that gui.py should query the power state first and then decide which button to display at start-up.
The attached patch to gui.py worked well for me...
tags: | added: patch |
Changed in wicd (Debian): | |
status: | Unknown → Confirmed |
Changed in wicd (Debian): | |
status: | Confirmed → Fix Released |
To post a comment you must log in.
This problem still exsits in 1.7.3 but the patch helps.
There are still two problems I see that need fixing.
1. If you press F2 to enable/disable wifi it would be nice to have wicd immediately show the change with the Switch ON/OFF button changing while wicd is open and you are looking at it, but you only see the new change when you restart wicd.
2. For laptops that the hardware switch is not supported as an example and the end-user maps the F2 key to rfkill to block and unblock the wifi, If you press the wicd Switch On/Off button it will then disable the F2 key mapped to rfkill. So the end-user should be able to press either the button in wicd or F2 and not have them conflict, but at present they conflict with each other...