LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   [SOLVED] wicd wants user added to netdev group, but it's already there (hal issues) (https://www.linuxquestions.org/questions/slackware-14/%5Bsolved%5D-wicd-wants-user-added-to-netdev-group-but-its-already-there-hal-issues-752837/)

quiescere 09-05-2009 03:22 AM

[SOLVED] wicd wants user added to netdev group, but it's already there (hal issues)
 
I just installed Slackware 13. Wicd was working fine under 12.2, but now it gives the following error:
Code:

Unable to contact the Wicd daemon due to an access denied error from DBus. Please check that your user is in the netdev group.
except my user certainly is in the netdev group (as well as the root user, and I put them all in messagebus, haldaemon, and plugdev as well, just in case.) Running the client manually from the command line gives the following not-helpful-to-me error:
Code:

ERROR:dbus.proxies:Introspect error on :1.39:/org/wicd/daemon: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 1 matched rules; type="method_call", sender=":1.64" (uid=100 pid=5514 comm="python -O /usr/lib/wicd/wicd-client.py ") interface="org.freedesktop.DBus.Introspectable" member="Introspect" error name="(unset)" requested_reply=0 destination=":1.39" (uid=0 pid=3538 comm="python -O /usr/lib/wicd/wicd-daemon.py "))
(I'm also having HAL problems with X: I can't get above 800x600. I lost a couple of hours mucking with xorg.conf-vesa before I remembered to check the changes and hints file. That's not important right now, except as further evidence that I've got a systemwide HAL problem, not just a wicd quirk.)

Any suggestions are appreciated.
----q.

Hangdog42 09-05-2009 08:18 AM

I was running into the same problem and annoyingly a reboot solved it. I'm guessing that some part of the system only picks up the assignment to netdev during a boot.

Bruce Hill 09-05-2009 08:32 AM

And your normal user should not be in the messagebus or haldaemon groups; in fact, you need no users in them at all.

quiescere 09-05-2009 01:20 PM

Argh. Now it's working after a reboot. I thought I had done that, but I guess despite changing init states and restarting inet1, I never actually did a complete shutdown and restart. Thanks. It's still flaky (having the hidden ssid problem another user has posted about) but at least this is one problem out of the way.

willysr 09-05-2009 01:26 PM

probably the just-released wicd (1-6.2.2) can fixed this problem. Try rebuilding using Slackware 13.0 SlackBuild

slero 04-25-2010 02:59 AM

Neither wicd (1-6.2.2), nor newest wicd (1.7.0) worked for me without full system restart, even after adding user to netdev group.

What I did:
1. wicd reinstall - got the message
Code:

Unable to contact the Wicd daemon due to an access denied error from DBus. Please check that your user is in the netdev group.
2. add user to netdev group and restart KDE - got the same message
3. su -c wicd-client - wicd loaded and worked
4. tried again with non-root user - got the same message
5. system reboot, startx - voila! wicd loaded and worked.

I think it is an issue regarding dbus initialization. If someone can post a solution without system rebooting, it will be appreciated.


All times are GMT -5. The time now is 06:34 PM.