Hi,
isis agora lovecruft wrote:
> Package: wicd-curses
> Version: 1.7.2.4-4
> Severity: grave
> Tags: upstream patch
> Justification: renders package unusable
>
> When attempting to run wicd-curses, I get the following traceback from an
> unhandled AttributeError:
>
> ∃!isisⒶwintermute:~ ∴ wicd-curses
>
> Traceback (most recent call last):
> File "/usr/share/wicd/curses/wicd-curses.py", line 1063, in <module>
> main()
> File "/usr/share/wicd/curses/wicd-curses.py", line 995, in main
> ui.run_wrapper(run)
> File "/usr/local/lib/python2.7/dist-packages/urwid/raw_display.py",
> line 242, in run_wrapper
> return fn()
> 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 1003, in run
> app = appGUI()
> File "/usr/share/wicd/curses/wicd-curses.py", line 548, in __init__
> self.wiredCB = urwid.Filler(WiredComboBox(wiredL))
> File "/usr/share/wicd/curses/wicd-curses.py", line 378, in __init__
> self.__super.__init__(use_enter=False)
> File "/usr/share/wicd/curses/curses_misc.py", line 352, in __init__
> self.focus = focus
> AttributeError: can't set attribute
While I could reproduce this last week on every wicd-curses invocation
it now no more happens.
Looks to me as if the bug was really in one of wicd-curses'
dependencies and has been fixed in the meanwhile.
"which-pkg-broke wicd-curses" (well, yes, it's used as
"which-pkg-fixed" here ;-) reports for dates after the bug report:
libselinux1:i386 Tue May 21 01:02:38 2013
libsepol1:i386 Tue May 21 01:02:46 2013
libsemanage-common Tue May 21 01:02:53 2013
libsemanage1:i386 Tue May 21 01:03:05 2013
python2.7 Tue May 21 01:03:35 2013
libpython2.7-stdlib Tue May 21 01:03:44 2013
python2.7-minimal Tue May 21 01:03:46 2013
libpython2.7-minimal Tue May 21 01:03:49 2013
libacl1:i386 Tue May 21 15:03:03 2013
libssl1.0.0:i386 Wed May 22 22:22:46 2013
libsqlite3-0:i386 Wed May 22 22:22:50 2013
libnl-3-200:i386 Wed May 22 22:23:07 2013
libnl-genl-3-200:i386 Wed May 22 22:23:07 2013
libgnutls-openssl27:i386 Thu May 23 23:41:04 2013
libgnutls26:i386 Thu May 23 23:41:05 2013
libprocps1:i386 Mon May 27 18:12:41 2013
procps Mon May 27 18:14:06 2013
isc-dhcp-client Tue May 28 14:25:10 2013
isc-dhcp-common Tue May 28 14:25:11 2013
python-urwid Thu May 30 01:24:10 2013
gcc-4.8-base:i386 Fri May 31 02:34:54 2013
libgcc1:i386 Fri May 31 02:35:19 2013
Then again, I downgraded python-urwid recently, too, to be able to
install sat-xmpp-primitivus from unstable which currently depends on
python-urwid's version in testing (likely because sat-xmpp-primitivus
was built against that version and then had to wait in NEW for a
while).
I'll soon check if upgrading python-urwid again to unstable make
wicd-curses bail out again.
But then again, python-urwid 1.1.1-1 was uploaded one day after this
bug report and the original report contained "ii python-urwid
1.0.2-1". And all recent python2.7 changes don't sound as if they
could cause such an issue. A new upstream version of python-urwid
still sounds more realistic somehow.
Regards, Axel
--
,''`. | Axel Beckert <[email protected]>, http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
`- | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
