wicd-curses: Crash and raise IndexError, "No widget at position %s"

Bug #1132053 reported by François Boulogne on 2013-02-23
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Tom Van Braeckel

Bug Description


I'm running wicd on archlinux.
There is my version:
wicd-curses --version -I-
wicd-curses-uimod (using wicd

The traceback:
ERROR:dbus.connection:Exception in handler for D-Bus signal:
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/dbus/connection.py", line 230, in maybe_handle_message
    self._handler(*args, **kwargs)
  File "/usr/share/wicd/curses/wicd-curses.py", line 788, in dbus_scan_finished
  File "/usr/share/wicd/curses/wicd-curses.py", line 621, in unlock_screen
  File "/usr/share/wicd/curses/wicd-curses.py", line 88, in wrapper
    return func(*args, **kargs)
  File "/usr/share/wicd/curses/wicd-curses.py", line 703, in update_netlist
  File "/usr/lib/python2.7/site-packages/urwid/listbox.py", line 567, in set_focus
  File "/usr/lib/python2.7/site-packages/urwid/listbox.py", line 178, in set_focus
    raise IndexError, "No widget at position %s" % (position,)
IndexError: No widget at position 2

I don't exactly known when it crashes. It seems it happens when a new connexion is set up.
Not reproducible each time, it occurs about Three times a week (my computer is running half a day).

radaiming (radaiming) wrote :

I also met this problem, the version is:
 $ wicd-curses --version -I-
wicd-curses-uimod (using wicd

It's easy to reproduce in a environment with many access points, continue refresh and move the focus to the access point at the bottom each time, when the numbers of access points scanned this time is less than last time, it can't focus on a non-exist access point, crash comes out.

I've view some code and get a solution, change

    self.wlessLB.set_focus(min(self.focusloc[1], len(self.wlessLB.body) -1))

in line 703 of wicd-curses.py, it will focus on last access point when get less access points then last scan.

radaiming (radaiming) wrote :

I found my fix is bad, will cause other problems, I wrote another dirty fix for myself, but hope to get better fixes:

  File "/usr/share/wicd/curses/wicd-curses.py", line 703, in update_netlist
    self.wlessLB.set_focus(min(self.focusloc[1], len(self.wlessLB.body) -1))
TypeError: object of type 'PollingListWalker' has no len()

FlashYoshi (tivervac) wrote :

You can indeed reproduce this as @radaiming said.
This fix I wrote seems to work:

if self.focusloc[1] < len(wlessL):
    self.wlessLB.set_focus(len(wlessL) - 1)

or as @radaiming would do it

self.wlessLB.set_focus(min(self.focusloc[1], len(wlessL) - 1))

FlashYoshi (tivervac) wrote :
Changed in wicd:
status: New → Confirmed

Improved and applied your patch. Thanks for making wicd more stable!

=== modified file 'curses/wicd-curses.py'
--- curses/wicd-curses.py 2014-12-19 14:40:39 +0000
+++ curses/wicd-curses.py 2014-12-20 09:30:43 +0000
@@ -872,7 +872,8 @@
                     if self.wlessLB != self.no_wlan:
- self.thePile.get_focus().set_focus(self.focusloc[1])
+ # Set the focus to the last selected item, but never past the length of the list
+ self.thePile.get_focus().set_focus(min(self.focusloc[1], len(wlessL) - 1))
@@ -885,7 +886,8 @@
                 if self.focusloc[1] is None:
                     self.focusloc[1] = 0
                 if self.wlessLB != self.no_wlan:
- self.wlessLB.set_focus(self.focusloc[1])
+ # Set the focus to the last selected item, but never past the length of the list
+ self.wlessLB.set_focus(min(self.focusloc[1], len(wlessL) - 1))

         self.prev_state = state
         if not firstrun:

Changed in wicd:
importance: Undecided → High
assignee: nobody → Tom Van Braeckel (tomvanbraeckel)
milestone: none → 1.7.3
status: Confirmed → Fix Committed
qbit (porcedda) wrote :

Hi all,

i use wicd-curses and I notice the exact bug claimed here. I saw above the patch by tivervac and its improvement by tomvanbraeckel, and I have two questions: do I have to only apply the last patch, or both two (first the tivervac one, then tomvanbraeckel one)? And does it work with wicd 1.7.3-1?

Thanks very much, and sorry for the behave!

Only the improved patch (the last one) will do. Try it on wicd 1.7.3-1!

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers