Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#43850 - [wicd] fail to setup up wifi-connection through wicd-curses

Attached to Project: Arch Linux
Opened by Tim Josefski (timski) - Monday, 16 February 2015, 22:37 GMT
Last edited by Doug Newgard (Scimmia) - Tuesday, 17 February 2015, 05:29 GMT
Task Type Bug Report
Category Packages: Extra
Status Assigned
Assigned To Angel Velasquez (angvp)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 10
Private No

Details

Description:

when I try to setup a new wifi link through wicd-curses it crashes and gives following output:

Traceback (most recent call last):
File "/usr/share/wicd/curses/wicd-curses.py", line 1146, in call_update_ui
self.update_ui(True)
File "/usr/share/wicd/curses/wicd-curses.py", line 97, in wrapper
return func(*args, **kargs)
File "/usr/share/wicd/curses/wicd-curses.py", line 1159, in update_ui
self.handle_keys(input_data)
File "/usr/share/wicd/curses/wicd-curses.py", line 1037, 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

Additional info:
wicd 1.7.3-1
python2-urwid 1.3.0-1

Steps to reproduce:
open wicd-curses
use right-arrow key to select a ssid
This task depends upon

Comment by Corentin Le Molgat (mizux) - Thursday, 19 February 2015, 01:04 GMT
Could reproduce it on two laptop (with one which is a fresh net install of today)

seems to be resolved here https://github.com/voidlinux/void-packages/issues/954
https://github.com/voidlinux/void-packages/commit/220de599ad3ecba14423289209a3e4e031037edf

Hope to have it soon on archlinux, having a new laptop with fresh install (no packages except base base-devel) no wifi -> no connection -> no update possible ^^;

Thanks
Comment by Tran Ha Vu (falcon) - Wednesday, 18 March 2015, 23:53 GMT
Got exact the same issue with latest update of wicd, hope to have it fixed soon on archlinux.
Comment by Ray Smith (muon_) - Friday, 10 April 2015, 18:54 GMT
As a note, following the commit Corentin referenced fixes the issue for me. It's a simple change of the /usr/share/wicd/curses/netentry_curses.py file. Not the ideal solution, but it got wicd-curses working again for me.
Comment by rimaille (ekyo) - Wednesday, 15 April 2015, 12:23 GMT
same problem here, when i need to setup a new wifi connection, i use the gtk client (wicd-client).
Comment by vonpupp (vonpupp) - Wednesday, 24 June 2015, 02:07 GMT
I have the same problem here =(
Comment by Mikael Muszynski (linduxed) - Sunday, 28 June 2015, 07:35 GMT
Confirming that this is still an issue.

According to the discussion on Github, a newer revision of the package already has a fix, it just has to be packaged for Archlinux.
Comment by Angel Velasquez (angvp) - Sunday, 28 June 2015, 13:06 GMT
This is an unofficial patch, and since this bug it's an upstream issue, I wrote to the maintainer of wicd several months ago in order to ask if this patch seems correct to him, I didn't got a reply yet. I'll try this and apply it if I see its working until a new release is made.
Comment by Samantha McVey (samcv) - Friday, 10 June 2016, 22:29 GMT
This bug was reported for 1.7.3, since the current version is 1.7.4-1, can I get a report back on whether this is still an issue in the latest version? Thank you.
Comment by Ray Smith (muon_) - Sunday, 12 June 2016, 22:30 GMT
I still see the same behavior as originally reported with wicd 1.7.4-1 and python2-urwid 1.3.1-2.
Comment by Michael (lusid_fait) - Tuesday, 16 August 2016, 15:14 GMT
Comment by Napalm Snake (palmerito0) - Sunday, 06 August 2017, 19:10 GMT
I can confirm this bug still occurs in version 1.7.4-1
Comment by Radek R. (radek_r) - Sunday, 09 September 2018, 09:30 GMT
the error still in wicd 1.7.4-2

Loading...