wicd-curses broken on Fedora 16 after update

Asked by dirt bag on 2012-11-09

[jason@zim ~]$ wicd-curses

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 1047, in <module>
    main()
  File "/usr/share/wicd/curses/wicd-curses.py", line 982, in main
    ui.run_wrapper(run)
  File "/usr/lib/python2.7/site-packages/urwid/raw_display.py", line 241, in run_wrapper
    return fn()
  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 990, in run
    app = appGUI()
  File "/usr/share/wicd/curses/wicd-curses.py", line 535, in __init__
    self.wiredCB = urwid.Filler(WiredComboBox(wiredL))
  File "/usr/share/wicd/curses/wicd-curses.py", line 365, in __init__
    self.__super.__init__(use_enter=False)
  File "/usr/share/wicd/curses/curses_misc.py", line 349, in __init__
    self.focus = focus
AttributeError: can't set attribute
[jason@zim ~]$

[jason@zim ~]$ pgrep -lf wicd
7679 /usr/bin/python -O /usr/share/wicd/daemon/wicd-daemon.py
7684 /usr/bin/python -O /usr/share/wicd/daemon/monitor.py
[jason@zim ~]$

any idears?

Question information

Language:
English Edit question
Status:
Answered
For:
wicd Edit question
Assignee:
David Paleino Edit question
Last query:
2012-11-09
Last reply:
2012-11-15
David Paleino (dpaleino) said : #1

What version of urwid do you have?

dirt bag (tempuser-n) said : #2

[jason@zim ~]$ rpm -qi python-urwid
Name : python-urwid
Version : 1.1.0
Release : 2.fc16
Architecture: i686
Install Date: Fri 09 Nov 2012 10:01:55 AM EST
Group : Development/Libraries
Size : 2785116
License : LGPLv2+
Signature : RSA/SHA256, Tue 23 Oct 2012 03:52:14 PM EDT, Key ID 067f00b6a82ba4b7
Source RPM : python-urwid-1.1.0-2.fc16.src.rpm
Build Date : Tue 23 Oct 2012 02:04:56 PM EDT
Build Host : buildvm-05.phx2.fedoraproject.org

I know that this rpm has (historically) been problematic, so I have frozen it in my /etc/yum.conf
so maybe i need to release it and upgrade it?

dirt bag (tempuser-n) said : #3

anyone?

David Paleino (dpaleino) said : #4

Your version isn't really frozen. You have 1.1.0 installed which -- once again -- changed API.

There is an existing bugreport, I linked that. Please continue there, if you need more info.

I will fix this ASAP.

Can you help with this problem?

Provide an answer of your own, or ask dirt bag for more information if necessary.

To post a message you must log in.