Can't see essid with "@" in its name.

Bug #421634 reported by Ismael
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
wicd
Fix Released
Critical
Adam Blackburn

Bug Description

After I updated to Wicd 1.6.2.1 and now I can't see an ESSID named "TYPO@HOME" when scanning. Downgraded to Wicd 1.6.2 and it went back to working flawlessly.

Running Slackware Linux 13.0.

I'm not familiar with wicd code, but it probably has something to do with this commit (which changes the ESSID regex from ".*" to "\w+" ): http://bazaar.launchpad.net/~adamblackburn/wicd/1.6.2.1/revision/457

Changed in wicd:
status: New → Confirmed
importance: Undecided → Critical
assignee: nobody → Adam Blackburn (adamblackburn)
status: Confirmed → In Progress
Revision history for this message
Adam Blackburn (adamblackburn) wrote :

I've come up with a new and improved regular expression that should solve the problem. I would appreciate testing from anyone who can test it.

Just replace the essid_pattern = re.compile(...) line in your wnettools.py with this line:

essid_pattern = re.compile(r'.*ESSID:("?)((?!"")[^\n].+?)(\1)\s*\n', _re_mode)

That should take care of all cases, except the case where the person has named their AP "" (literally two quotes) but I suspect this is a very, very uncommon case. (if anyone who is better than me at regex would like to fix this... :)

Revision history for this message
Adam Blackburn (adamblackburn) wrote :

 * The ioctl backend is not affected by this.

Just had an idea:

Instead of the one in my above post, try this:

essid_pattern = re.compile(r'.*ESSID:("?)((?!""\s*\n)[^\n].+?)(\1)\s*\n', _re_mode)

Revision history for this message
Adam Blackburn (adamblackburn) wrote :

Wicd 1.6.2.2 once again handles this case properly.

Revision history for this message
Adam Blackburn (adamblackburn) wrote :

Please let us know if you encounter any more problems.

Changed in wicd:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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