SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Are you running current? Wicd 1.7.3 and urwid 1.3.0 are not good friend. Patches exist but are hit and miss.
I chose to stay on wicd 1.7.2.x and urwid 1.0.x.
After applying the patch in my OP, everything is working. I first encountered the issue in Gentoo earlier today and the same patch fixed the issue there.
Figured the Slackware community would like to know about it.
Thank you for providing this, I am experiencing the same issue when altering SSID properties:
Code:
ry@~:$ wicd-curses
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
I will try a rebuild with your patch. This issue only happens on networks that have not yet been configured.
On another note, NetworkManager has to connect twice to my home network in KDE (always fails on first attempt, then succeeds), I have never seen this behavior before ... perhaps v1.0.6 fixes this?
Are you running current? Wicd 1.7.3 and urwid 1.3.0 are not good friend. Patches exist but are hit and miss.
I chose to stay on wicd 1.7.2.x and urwid 1.0.x.
Thanks for this posting.
It was suggested in the requests-for-current thread to apply the patch
I get this when connecting with wicd-ncurses although it connects.
Quote:
bash-4.3$ wicd-curses
ERROR:dbus.connection:Exception in handler for D-Bus signal:
Traceback (most recent call last):
File "/usr/lib64/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 97, in wrapper
return func(*args, **kargs)
File "/usr/share/wicd/curses/wicd-curses.py", line 850, in update_netlist
self.wiredCB.get_body().set_list(wiredL)
File "/usr/share/wicd/curses/wicd-curses.py", line 469, in set_list
wired.ReadWiredNetworkProfile(self.get_selected_profile())
File "/usr/share/wicd/curses/wicd-curses.py", line 535, in get_selected_profile
return self.theList[loc]
IndexError: list index out of range
And also get this when quiting on wicd-ncurses
Quote:
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 1157, in update_ui
input_data = ui.get_input()
File "/usr/lib64/python2.7/site-packages/urwid/raw_display.py", line 324, in get_input
keys, raw = self.parse_input(None, None, self.get_available_raw_input())
File "/usr/lib64/python2.7/site-packages/urwid/raw_display.py", line 465, in parse_input
codes, wait_for_more)
File "/usr/lib64/python2.7/site-packages/urwid/escape.py", line 383, in process_keyqueue
if run[0] == "esc" or run[0].find("meta ") >= 0:
AttributeError: 'tuple' object has no attribute 'find'
I would like to see wicd dropped from default Slackware.
I used to use and like wicd, especially the ncurses interface, but I now find NetworkManager more capable (I like my USB modem ), even though I still find nmcli difficult to use and deficient when handling secrets as well as NetworkManager's handling of different firewall scripts based on the interface in use to be more difficult to set up.
Also, there is a continuing stream of threads where NetworkManager has been tried and failed, then wicd being installed, leading to conflicts. Choice is good, but sometimes choice needs to be informed. Installing from /extra provides an imprimatur that success is guaranteed. Installing from SBo does not provide the same imprimatur.
/me now ducks into bunker and prepares to wait out the incoming storm.
I believe Pat said it's time to send wicd to SBo but ...
On my Killer 1535 wireless ( ath10k_core module ), when I try to connect to a Wireless AP, NetworkManager goes off into an infinite loop of Connect, Disconnect and never gives me a solid connection.
On the other hand, wicd 'just works' -- both GUI and TUI.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.