Wicd does not detect when broadcasted ESSIDs are changed

Bug #459574 reported by Adam Blackburn on 2009-10-24
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Adam Blackburn
Fix Released

Bug Description

When the ESSID broadcasted by an AP is changed, Wicd does not detect the changed ESSID, instead resorting to the one store in the configuration file wireless-settings.conf. This is a problem because in some cases it prevents people from connecting to their wireless networks.

Changed in debian:
status: Unknown → New
Changed in debian:
status: New → Confirmed
albertone1982 (albertone1982) wrote :

I remember I could solve the problem by removing some files... Unfortunately, I can't remember which files I deleted... :(
Anyone could please give me an advice?

Adam Blackburn (adamblackburn) wrote :

You can solve it by editing /etc/wicd/wireless-settings.conf

I'll take a look and see if I can fix it so it doesn't do this anymore.

Adam Blackburn (adamblackburn) wrote :

Can someone using a *broadcasting* ESSID that is having this trouble please give me a copy of their iwlist scan? Thanks.

deadrabbit (deadrabbit) wrote :

By broadcasting, you mean not a hidden ESSID right? The log is attached (MAC has been obscured).

I would argue that this should be raised to high priority, due the scenario I found myself in: I just got a new router, connected with wicd, went to change the ESSID manually, and then couldn't connect again. Took me a very long time to stumble upon the wireless-settings.conf file - I thought it was a router problem. Seems like a very common scenario.

Thanks for all your work.

Adam Blackburn (adamblackburn) wrote :

deadrabbit: Could you also post the relevant section of your /etc/wicd/wireless-settings.conf file? Make sure you obscure names/MAC addresses/passwords/etc.

Don't worry about the priority. This will be fixed before the next release.

deadrabbit (deadrabbit) wrote :

wireless-settings.conf is attached.

Adam Blackburn (adamblackburn) wrote :

Can someone having this problem confirm that it still exists in 1.7.0a3 or the latest lp:wicd? I can't seem to reproduce it here. Thanks.

Adam Blackburn (adamblackburn) wrote :

I think this is fixed in the latest lp:wicd so I'm going to mark it fix committed. Please reopen if it is not fixed.

Changed in wicd:
status: Confirmed → Fix Committed
Changed in wicd:
assignee: nobody → Adam Blackburn (adamblackburn)
Changed in wicd:
status: Fix Committed → Fix Released
Changed in debian:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.