MOE-lnx, you are correct that wicd must be launched as root, but from the user perspective here's what I will have to teach several people
who are not pc savvy. ( as I am donating these laptops.)
OK, hope this makes sense. Now with only root and one user01 account created .
1. If I start laptop from off and log into normal user01 and let GUI load, USB adapter LED is OFF, and I have wicd in menu and tray but launching from either gives "could not connect" popup. So then close popups and launch a root terminal , start wicd, then close terminal, then USB adpter LED kicks in, and I can launch wicd from normal's GUI tray or menu. (Yes, I could teach them to reopen normal terminal and enter "wicd-client" ).
2. But if I start laptop from off, then log in as root, and let root's GUI load and WITHOUT TERMINAL just launch wicd from either tray or menu., adapter LED kicks on, wicd works and I can connect. AND if I log out ( not shut down) and log back in as normal/unprivileged user01, then adapter remains on (presumably b/c it has been launched in root's previous session) , wicd is in tray and menu and I can launch and use wicd as normal user.
So either way wicd is being launched as root and if so, should probably teach procedure (1) so as not to leave them in root's GUI session.
wicd-daemon may be loading at boot, but without that LED on, I know either wicd or the rtl 8187 module has not accessed it until root launches it either way as you say. The reason I say is b/c pclos lxde lights that led during boot even before login and user can launch network manager from his/her own GUI (if given permissions during network setup).
1. Isn't there some script or conf file way to give allow normal/unprivileged user permissions to launch wicd from his own GUI interface?
Haven't used Windows in 7-8 years but new to VL . Sorry, got spoiled by mandriva/pclos/mageia control center. Blame them!