LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 09-05-2009, 03:22 AM   #1
quiescere
Member
 
Registered: Sep 2003
Distribution: Slackware64 13.1
Posts: 52

Rep: Reputation: 15
[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.

Last edited by quiescere; 09-05-2009 at 01:21 PM.
 
Old 09-05-2009, 08:18 AM   #2
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,791
Blog Entries: 1

Rep: Reputation: 414Reputation: 414Reputation: 414Reputation: 414Reputation: 414
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.
 
Old 09-05-2009, 08:32 AM   #3
Bruce Hill
HCL Maintainer
 
Registered: Jun 2003
Location: Tupelo, MS
Distribution: Gentoo
Posts: 6,926

Rep: Reputation: 124Reputation: 124
And your normal user should not be in the messagebus or haldaemon groups; in fact, you need no users in them at all.
 
Old 09-05-2009, 01:20 PM   #4
quiescere
Member
 
Registered: Sep 2003
Distribution: Slackware64 13.1
Posts: 52

Original Poster
Rep: Reputation: 15
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.
 
Old 09-05-2009, 01:26 PM   #5
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 2,605

Rep: Reputation: 438Reputation: 438Reputation: 438Reputation: 438Reputation: 438
probably the just-released wicd (1-6.2.2) can fixed this problem. Try rebuilding using Slackware 13.0 SlackBuild
 
Old 04-25-2010, 02:59 AM   #6
slero
LQ Newbie
 
Registered: Aug 2004
Location: Sofia, Bulgaria
Distribution: Slackware
Posts: 3

Rep: Reputation: 0
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.
 
  


Reply

Tags
hal, wicd


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
root not in netdev group by default jazzor Slackware 4 08-12-2009 10:29 AM
How can I make bash recognise that some user has been added to a group? Bernard Swiss Linux - General 20 09-23-2007 09:25 AM
LXer: Include diff attachment -- Re: Fedora-netdev FC4: kernel-2.6.14-1.1656_FC4.netdev.7 is now available! LXer Syndicated Linux News 0 01-09-2006 09:01 PM
LXer: Fedora-netdev FC4: kernel-2.6.14-1.1653_FC4.netdev.6 is now available! LXer Syndicated Linux News 0 12-15-2005 02:32 PM
reboot so user can access fs space limited by group recently added to? bdp Linux - General 4 09-27-2003 02:21 AM


All times are GMT -5. The time now is 03:43 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration