curses python error after escape from preferences

Bug #890442 reported by Dan Ibanez
4
This bug affects 1 person
Affects Status Importance Assigned to Milestone
wicd
Fix Released
Low
David Paleino

Bug Description

Using the wicd-curses, entered preferrences, navigated through all preferences without changing any, then hit escape key. client crashed with the following:

EXCEPTION! Please report this to the maintainer and file a bug report with the backtrace below:
Traceback (most recent call last):
  File "/usr/share/wicd/curses/wicd-curses.py", line 904, in call_update_ui
    self.update_ui(True)
  File "/usr/share/wicd/curses/wicd-curses.py", line 89, in wrapper
    return func(*args, **kargs)
  File "/usr/share/wicd/curses/wicd-curses.py", line 913, in update_ui
    input_data = ui.get_input_nonblocking()
  File "/usr/lib/python2.7/site-packages/urwid/raw_display.py", line 339, in get_input_nonblocking
    return self._input_iter.next()
  File "/usr/lib/python2.7/site-packages/urwid/raw_display.py", line 373, in _run_input_iter
    codes, False)
  File "/usr/lib/python2.7/site-packages/urwid/escape.py", line 354, in process_keyqueue
    if run[0] == "esc" or run[0].find("meta ") >= 0:
AttributeError: 'tuple' object has no attribute 'find'

[dibanez@chomsky ~]$ wicd-curses --version
wicd-curses-uimod (using wicd 1.7.0)
[dibanez@chomsky ~]$ uname -a
Linux chomsky 3.1.0-4-ARCH #1 SMP PREEMPT Mon Nov 7 22:47:18 CET 2011 x86_64 Intel(R) Core(TM) i3-2350M CPU @ 2.30GHz GenuineIntel GNU/Linux

Revision history for this message
David Paleino (dpaleino) wrote :

It seems like I can't reproduce it, sorry.

What's your version of urwid?

Changed in wicd:
status: New → Invalid
status: Invalid → Triaged
Revision history for this message
David Paleino (dpaleino) wrote :

OH, instead I can. But it doesn't really crash, it just shows the traceback once you exited it.

Is it right?

Changed in wicd:
assignee: nobody → David Paleino (dpaleino)
importance: Undecided → Low
Revision history for this message
Dan Ibanez (dan-a-ibanez) wrote :

Yes, it just showed a traceback. Also, since upgrading wicd, I cannot reproduce it anymore.

Revision history for this message
Pieter Leclerc (pieterleclerc-deactivatedaccount) wrote :

Same here; cannot reproduce with the latest version of wicd, so I assume this has been fixed somewhere between 1.7.0 and 1.7.4...

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

Other bug subscribers

Remote bug watches

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