View previous topic :: View next topic |
Author |
Message |
dfisco n00b
Joined: 04 Jul 2007 Posts: 39
|
Posted: Sat Apr 25, 2009 6:22 pm Post subject: NetworkManager 7.1 and DBus method calls |
|
|
I recently upgraded NetworkManager to 0.7.1-r1 on my Gentoo laptop.
I began seeing this about every four seconds in my system log:
Code: | Apr 25 13:47:10 pavilion-fisco dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.76" (uid=0 pid=14243 comm="/usr/sbin/NetworkManager --pid-file /\
var/run/Netwo") interface="org.freedesktop.Hal.Device.KillSwitch" member="GetPower" error name="(unset)" requested_reply=0 destination="org.freedesktop.Hal" (uid=0 pid=14128 comm=\
"/usr/sbin/hald --use-syslog --verbose=yes ")) |
I'm assuming this means that NetworkManager is trying to get the power state of one of the laptop's networking devices (probably WiFi) via a DBus method call, but DBus is rejecting the method call. Note that NetworkManager works fine, even with this rejected send message.
I looked in /etc/dbus-1/system.conf and found this line:
Code: | <deny send_type="method_call"/> |
So, I'm assuming that for security reasons, DBus defaults to not allowing method calls on its bus. My understanding is that you shouldn't alter /etc/dbus-1/system.conf, but you can override that configuration file with a patch file called system-local.conf. I added a file (/etc/dbus-1/system-local.conf) to my laptop with the contents:
Code: | <!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-Bus Bus Configuration 1.0//EN"
"http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
<busconfig>
<policy context="default">
<allow send_type="method_call"/>
</policy>
</busconfig> |
It seems to be allowing method calls on the DBus as none of the rejected send messages are appearing in my system log. I'm assuming that this opens up a bunch of security concerns (although I'm not sure they would apply to a single-user laptop).
I've made a bunch of guesses and assumptions in getting rid of this message. Any ideas or comments? |
|
Back to top |
|
|
lorenb Apprentice
Joined: 24 Aug 2002 Posts: 207 Location: Toronto, ON
|
Posted: Sat Apr 25, 2009 8:14 pm Post subject: |
|
|
To fix it on my system, I copied what the Ubuntu guys did to fix. In /etc/dbus-1/system.d/hal.conf, you'll see a block like this:
Code: | <!-- Default policy for the exported interfaces; if PolicyKit is not used
for access control you will need to modify this -->
<policy context="default">
<allow send_interface="org.freedesktop.Hal.Device.SystemPowerManagement"/>
<allow send_interface="org.freedesktop.Hal.Device.VideoAdapterPM"/>
<allow send_interface="org.freedesktop.Hal.Device.LaptopPanel"/>
<allow send_interface="org.freedesktop.Hal.Device.Volume"/>
<allow send_interface="org.freedesktop.Hal.Device.Volume.Crypto"/>
</policy> |
I added 2 new lines for KillSwitch and CPUFreq at the bottom:
Code: | <!-- Default policy for the exported interfaces; if PolicyKit is not used
for access control you will need to modify this -->
<policy context="default">
<allow send_interface="org.freedesktop.Hal.Device.SystemPowerManagement"/>
<allow send_interface="org.freedesktop.Hal.Device.VideoAdapterPM"/>
<allow send_interface="org.freedesktop.Hal.Device.LaptopPanel"/>
<allow send_interface="org.freedesktop.Hal.Device.Volume"/>
<allow send_interface="org.freedesktop.Hal.Device.Volume.Crypto"/>
<allow send_destination="org.freedesktop.Hal" send_interface="org.freedesktop.Hal.Device.KillSwitch"/>
<allow send_destination="org.freedesktop.Hal" send_interface="org.freedesktop.Hal.Device.CPUFreq"/>
</policy> |
|
|
Back to top |
|
|
kernelOfTruth Watchman
Joined: 20 Dec 2005 Posts: 6111 Location: Vienna, Austria; Germany; hello world :)
|
|
Back to top |
|
|
Mamizou Tux's lil' helper
Joined: 09 May 2003 Posts: 101
|
Posted: Mon Apr 27, 2009 8:11 pm Post subject: |
|
|
I added those lines in, restarted hald, and it immediately fixed the problem. Thanks! =) |
|
Back to top |
|
|
regomodo Guru
Joined: 25 Mar 2008 Posts: 445
|
Posted: Sun May 03, 2009 12:53 am Post subject: |
|
|
I can't get Networkmanager to work. 0.6 was buggy as hell and >=0.7 have just refused to see/do anything.
I've added the 2 lines to hal.conf but nm-applet still sees nothing.
This is what I see when I start nm-applet from the terminal
Code: | ** (nm-applet:3924): WARNING **: Could not retrieve dbus connections: Failed to execute program /usr/libexec/dbus-daemon-launch-helper: Success. |
What USE flags should I have built NetworkManager with? |
|
Back to top |
|
|
|