NM-APPLET "Error getting devices"

Bug #356925 reported by Mattia Guidi
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Binary package hint: network-manager

By left-clicking on the nm-applet icon, it always gives back the message "No network devices available", although all the connections (cable and wireless) work properly.
If I close nm-applet and re-run it from a terminal window, I get this:

sudo nm-applet
[sudo] password for xxxx:

** (nm-applet:13113): WARNING **: No connections defined

** (nm-applet:13113): WARNING **: nm_client_get_devices: error getting devices: A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration file (rejected message had interface "org.freedesktop.NetworkManager" member "GetDevices" error name "(unset)" destination "org.freedesktop.NetworkManager")

Network Manager is at 0.7 version.

Mattia Guidi (matguidi)
description: updated
Revision history for this message
Alexander Sack (asac) wrote :

1. dont start applet as root ;).
2. what happens if you start it as your user?
3. please post what you get on ls /etc/dbus-1/system.d/

Changed in network-manager (Ubuntu):
status: New → Incomplete
Revision history for this message
Mattia Guidi (matguidi) wrote :

1) ok :)
2) the response is the same as if the application is started as root:

me@me-laptop:~$ nm-applet

** (nm-applet:13360): WARNING **: nm_client_get_devices: error getting devices: A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration file (rejected message had interface "org.freedesktop.NetworkManager" member "GetDevices" error name "(unset)" destination "org.freedesktop.NetworkManager")

3) here you are:

me@me-laptop:~$ ls /etc/dbus-1/system.d/
avahi-dbus.conf
bluetooth.conf
com.ubuntu.DeviceDriver.conf
com.ubuntu.ScreenResolution.Mechanism.conf
com.ubuntu.SystemService.conf
com.ubuntu-tweak.Mechanism.conf
ConsoleKit.conf
cups.conf
dhcdbd.conf
hal.conf
NetworkManager.conf
NetworkManager.conf~
newprinternotification.conf
nm-applet.conf
nm-avahi-autoipd.conf
nm-dhcp-client.conf
nm-dispatcher.conf
nm-openvpn-service.conf
nm-system-settings.conf
nm-vpnc-service.conf
obex-data-server.conf
org.freedesktop.PolicyKit.conf
org.gnome.ClockApplet.Mechanism.conf
org.gnome.CPUFreqSelector.conf
org.gnome.GConf.Defaults.conf
skype.conf
system-tools-backends.conf
wicd.conf
wpa_supplicant.conf

What should the last command exactly show?

Thank you for your help, and don't hesitate to ask me more infos if you need!

Mattia Guidi (matguidi)
Changed in network-manager (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Mattia Guidi (matguidi) wrote :

It was sufficient to change some "deny" into "allow" in /etc/dbus-1/system.d/NetworkManager.conf

Changed in network-manager (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
Alexander Sack (asac) wrote :

you might have opened a security whole by doing that. i would suggest that you post your NetworkManager.conf so i can take a look.

Revision history for this message
Alexander Sack (asac) wrote :

that said: if you ever manually edited that file, you probably got stuck with the old version. dbus was changed to permissive default policy in jaunty, meaning that if you have the old file, you dont have enough permissions. I attach the right file here now. maybe compare it with what you have.

Changed in network-manager (Ubuntu):
status: Invalid → Incomplete
Revision history for this message
Mattia Guidi (matguidi) wrote :

Sorry Alexander, but the NetworkManager.conf that you've posted displays only "512" as text. Could you please check it? Thanks...

Revision history for this message
Alexander Sack (asac) wrote :

thats just a display thing. should work better now that i tweaked the mime type of the attachment. just download that file and compare in editor.

Revision history for this message
Mattia Guidi (matguidi) wrote :

I've replaced my *.conf file with the one you've posted (saving a backup copy)... it seems to work! Thanks again!

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.]

Changed in network-manager (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.