You are not logged in.
Hi all,
Yesterday I changed--just for the sake of trying new things--the driver that wicd uses (in Preferences > Advanced > Driver). I tried to select another different driver and it worked. However, when I try to go back to wext wicd-curses collapses and the terminal prompts a message saying that "AttributeError: 'Text' object has no attribute 'keypress' (ergo the selected driver in wicd remains as nl80211).
Out of curiosity, how could I change the driver back to wext? Thanks a lot.
Best,
ps: wicd seems to work just fine under nl80211
Last edited by Humble_Panda (2013-10-07 03:29:47)
Offline
Hi again,
I know I said previously that wicd seemed to be working fine. Thing is, these days I have been experimenting more disconnections than before (so I am guessing it might have to do with the driver I am using now, nl80211).
I tried to change it manually in
/etc/wicd/manager-settings.conf
However, changes are applied only to the other two drivers available, meaning that in wicd-curses > Preferences > Advanced the changes are reflected as long as they are not "wext."
Any idea as to why this is happening?
Cheers
Offline
This isn't an answer but you could try
# pacman -Rn wicd <insert names of other wicd packages you use here e.g. wicd-gtk>
# pacman -S wicd <insert names of other wicd packages you use here e.g. wicd-gtk>and then reconfigure it from scratch. While this obviously shouldn't be necessary, if you are stuck, it might be worth doing. It also might be worth filing a bug report (upstream?).
EDIT: You should probably stop the wicd service with systemctl before you do this and then restart it afterwards just so systemd doesn't freak out.
Last edited by cfr (2013-10-06 19:03:41)
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline
@cfr
Thanks for your reply. In my mind what you proposed was the last resort, but now I think I will have to do it in the "dirty" way.
Cheers
ps: to fully remove wicd's configuration you also need to remove manually several directories in /etc and /var if I remember well.
Offline