[wicd-curses] configure new network

Bug #1184629 reported by Lukas Elsner
60
This bug affects 13 people
Affects Status Importance Assigned to Milestone
wicd
In Progress
Undecided
Timur

Bug Description

The first time I try to configure a network, I get this traceback:

Traceback (most recent call last):
  File "/usr/share/wicd/curses/wicd-curses.py", line 1134, in call_update_ui
    self.update_ui(True)
  File "/usr/share/wicd/curses/wicd-curses.py", line 94, in wrapper
    return func(*args, **kargs)
  File "/usr/share/wicd/curses/wicd-curses.py", line 1146, in update_ui
    self.handle_keys(input_data[1])
  File "/usr/share/wicd/curses/wicd-curses.py", line 1028, in handle_keys
    self.diag = WirelessSettingsDialog(pos, self.frame)
  File "/usr/share/wicd/curses/netentry_curses.py", line 503, in __init__
    self.set_values()
  File "/usr/share/wicd/curses/netentry_curses.py", line 543, in set_values
    wireless.GetWirelessProperty(networkID, 'bitrate')
ValueError: None is not in list

But, I'm able to connect to a network via wicd-gtk, and once this connection is saved, it can be modified later using wicd-curses.

Related branches

Revision history for this message
John Boiles (johnaboiles) wrote :

I get the same thing on the latest build from source.

Revision history for this message
John Boiles (johnaboiles) wrote :

Likely introduced by this change:

"Implement iwconfig bitrate setting"
http://bazaar.launchpad.net/~wicd-devel/wicd/experimental/revision/813

The line that causes the crash is trying to set a checkbox for the current bitrate, but there is not current bitrate for networks we're not currently connected to. It's a nice idea, but that change needs some work. I'd stick to 1.7.2.4 for now. Seems to be in a much better place.

Revision history for this message
Valentin J. Leon-Bonnet (vleonbonnet) wrote :

Commenting the lines 541 to 545 on netentry_curses.py for wicd 1.7.4 fixed this issue for me.

Timur (timur-adamow)
Changed in wicd:
status: New → Confirmed
assignee: nobody → Timur (timur-adamow)
Timur (timur-adamow)
Changed in wicd:
status: Confirmed → In Progress
Revision history for this message
Sebastian Rasmussen (sebras) wrote :

I'm on Debian/testing and got hit by this bug today.
The fix proposed in lp#1432423 fixed the issue for me.
Since this seems not have been fixed for a long time,
would it be possible to apply that fix until something
even more well though out can be implemented? Thank you! :)

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.