[SOLVED] Trying wicd, but daemon error because not logging in as root

Konphine · 09-21-2011, 07:58 PM

Okay, so I have wicd downloaded and ready to go. It's working great, I like it.

However, whenever I restart my computer, I get this error message:

Code:

Could not connect to wicd's D-Bus interface. Check the wicd log for details.

Code:

The wicd daemon has shut down. The UI will not function properly until it is restarted.

Then another one comes up but that one just says "Disconnected". Anyways, I do know for a fact that wicd requires it to be run as root, so I quickly switched user to root to start wicd by:

Code:

/etc/rc.d/rc.wicd start

Afterwards it works fine, but I don't want to be doing this every time I log on just to get an internet connection. Is there by any chance a possibility to run wicd as soon as I log in?

A second somewhat related question: I downloaded wicd from the /extras section on the Slackware DVD, but I'm wondering if I use slackpkg to update my packages, and there's a new version of wicd out or something, will it also be updated?

I got very far in my Google searches but to no avail, and in LinuxQuestions.org these were the only 2 threads I found with the same (or similar) problem:

http://www.linuxquestions.org/questi...-error-771762/
http://www.linuxquestions.org/questi...stions-892213/

dive · 09-21-2011, 08:06 PM

So long as it's executable it will start on boot via rc.M in 13.37

ReaperX7 · 09-21-2011, 08:30 PM

Is your user account part of the "netdev" group?

allend · 09-21-2011, 08:55 PM

Is the 'dbus-daemon' process running? Check that /etc/rc.d/rc.messagebus is executable.

Konphine · 09-21-2011, 09:56 PM

Quote:

dive:
So long as it's executable it will start on boot via rc.M in 13.37

It does start on boot because by default it is part of rc.M, but it needs root privileges in order to start, which means I have to temporarily log in to root in order to start it.

Quote:

ReaperX7:
Is your user account part of the "netdev" group?

I'm not quite sure how to check. It's been awhile but was it part of the default settings? The only group I added to my user was 'sys'.

Quote:

allend:
Is the 'dbus-daemon' process running? Check that /etc/rc.d/rc.messagebus is executable.

/etc/rc.d/rc.messagebus is executable.

allend · 09-21-2011, 10:18 PM

To check the groups that your user belongs to, either login as that user and type 'groups', or inspect the output of 'less /etc/group'.

The typical groups for a user to belong to are:

Quote:

users floppy audio video cdrom plugdev power netdev

Konphine · 09-21-2011, 10:27 PM

Yes, my user does seem to be a part of the "netdev" group ReaperX7, and thank you allend for the command.

allend · 09-21-2011, 11:25 PM

Another thought is to check /var/run/wicd/ for any stale lock files.
As root, do '/etc/rc.d/rc.wicd stop', then delete in files in the above directory, before restarting with '/etc/rc.d/rc.wicd start'.

Konphine · 09-21-2011, 11:35 PM

There's nothing in there except the pid file.

dive · 09-22-2011, 12:46 AM

Quote:

Originally Posted by Konphine

It does start on boot because by default it is part of rc.M, but it needs root privileges in order to start, which means I have to temporarily log in to root in order to start it.

rc.M is run as root. You don't need to log in to start it, let rc.M start it. Check that there is actually a section in rc.M to start it. Should look like:

Code:

# Start wicd:        
if [ -x /etc/rc.d/rc.wicd ]; then
  sh /etc/rc.d/rc.wicd start
fi

dive · 09-22-2011, 12:51 AM

Quote:

Originally Posted by Konphine

There's nothing in there except the pid file.

If wicd is definitely not running you can delete that.

willysr · 09-22-2011, 01:06 AM

execute

Code:

wicd-client &

as root once you loggged in to your desktop

Konphine · 09-22-2011, 01:56 AM

Problem solved. It was my idiocy at work again. :/ I had commented out wicd since I had both it and networkmanager (although networkmanager was in rc.local). Sorry for bothering you guys. I knew it was in rc.M which is why I didn't bother to really check, but then looking at it again...it was commented out.

Well, other than that, thanks guys. ^.^