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.
You should not remove the wicd package... that contains the daemon.
All you need to do is prevent the wicd-client to start and then run wicd-kde instead.
Anybody? I've done a bunch of Google searches but nothing I've found has worked. The only thing I could think of was to change the permissions on wicd-client so it isn't executable, but that seems like a kludge.
How do you keep wicd-client from starting? I haven't been able to figure that one out.
You can prevent the wicd client from starting when you logon, if you add this line to its desktop files in /etc/xdg/autostart and /usr/share/autostart :
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.