wicd can't detect wireless interface
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
wicd |
Fix Committed
|
Critical
|
David Paleino | ||
wicd (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Hi, I recently migrated to a new laptop, and wicd had trouble detecting the wireless interface on it. I'm using Debian sid on a Toshiba dynabook RX2/T7J.
GetWirelessInte
I chose iwgetid over iwconfig because of this bug:
http://
(Summary of the linked bug report: "iwconfig foo" returns 0 even if foo is not a wireless interface.)
There is a related bug, which is that the default values of the interfaces were never used. My wireless interface was in fact wlan0 (the hard-coded default), but wicd didn't try that interface. In WicdDaemon.
Finally, can wicd show a warning if it couldn't detect any wireless interfaces? I think the user should be alerted when there is a potential problem.
Related branches
Changed in wicd: | |
assignee: | nobody → David Paleino (dpaleino) |
importance: | Undecided → Medium |
status: | Confirmed → Triaged |
affects: | wicd → baltix |
Changed in baltix: | |
milestone: | 1.7.3 → none |
affects: | baltix → wicd |
Changed in wicd (Baltix): | |
status: | New → Incomplete |
status: | Incomplete → New |
Changed in wicd (Ubuntu): | |
status: | New → Confirmed |
What is in /sys/class/ net/wlan0/ on your system? I'm surprised the wireless directory is missing.
The detection code could get moved to the backends. Right now it lives in wnettools.py right now because checking for a directory on the filesystem is pretty quick, and it just gets run twice at start up time (once for wired, once for wireless), so I didn't bother with an ioctl implementation for it.
Re: the default interface name not getting used, now that you mention it, we probably shouldn't be filling in a default interface at all. It will likely cause issues if we try to use a wireless interface we didn't actually detect and that probably doesn't exist.
I don't think removing the str() call from the return value of DetectWirelessI nterface( )/DetectWiredIn terface( ) will work correctly unless you convert None to an empty string first. D-Bus can't return NoneType.
I think a warning should be getting logged when we don't detect a wireless interface. Bubbling it up to the GUI might get annoying for users who really don't have a wireless interface. Actually, that code gets executed so early in the daemon startup sequence that the UI probably won't even be running yet. We don't really have a system for queuing up messages in the daemon to send to the UI right now, so any signal we sent indicating the failure to detect the interface would likely be lost anyway. It's something to consider for wicd 2.0, though.