Slackware This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
06-01-2012, 10:43 AM
|
#1
|
Member
Registered: May 2004
Distribution: Slackware
Posts: 69
Rep:
|
Wicd-kde daemon problem
I'm running slack-current on a Dell lattitude.
I removed wicd (which was working fine) and installed wicd-kde. My problem is the wicd-kde client reports the wicd daemon isn't running.
I manually start the wicd daemon, but the client still says the dameon isn't running.
Any suggestions or help is appreciated.
|
|
|
Click here to see the post LQ members have rated as the most helpful post in this thread.
|
06-01-2012, 11:02 AM
|
#2
|
Slackware Contributor
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,559
|
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.
Eric
|
|
|
06-01-2012, 12:05 PM
|
#3
|
Member
Registered: May 2004
Distribution: Slackware
Posts: 69
Original Poster
Rep:
|
Thank you, Eric.
It's working now.
|
|
|
07-07-2012, 06:39 PM
|
#4
|
Member
Registered: Dec 2005
Distribution: Slackware64 15.0 Multilib
Posts: 318
Rep:
|
Quote:
Originally Posted by Alien Bob
All you need to do is prevent the wicd-client to start and then run wicd-kde instead.
|
How do you keep wicd-client from starting? I haven't been able to figure that one out.
|
|
|
07-10-2012, 01:28 PM
|
#5
|
Member
Registered: Dec 2005
Distribution: Slackware64 15.0 Multilib
Posts: 318
Rep:
|
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.
|
|
|
07-10-2012, 01:48 PM
|
#6
|
Slackware Contributor
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,559
|
Quote:
Originally Posted by marnold
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 :
Eric
|
|
2 members found this post helpful.
|
07-10-2012, 01:52 PM
|
#7
|
Member
Registered: Dec 2005
Distribution: Slackware64 15.0 Multilib
Posts: 318
Rep:
|
Woohoo! Thanks, Eric. That did the trick!
|
|
|
12-25-2013, 03:45 PM
|
#8
|
Member
Registered: Apr 2011
Distribution: slackware64-current
Posts: 566
Rep:
|
I had this same problem, but my issue was that I had wicd-kde but not wicd! It works now. 
|
|
|
All times are GMT -5. The time now is 07:33 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|