[Gutsy][NetworkManager] No applet anymore

Bug #261472 reported by Cédric Jeanneret deactivated
4
Affects Status Importance Assigned to Milestone
network-manager-applet (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Hello again,
I have a "little" problem on two gutsy :
NetworkManager appelet doesn't appear in systray, BUT it's up n'running according to /var/log/daemon.log...

Versions :
ii network-manager 0.6.5-0ubuntu16.7.10.0
ii network-manager-gnome 0.6.5-0ubuntu11~7.10.0
ii network-manager-openvpn 0.3.2svn2342-1ubuntu4
ii network-manager-pptp 0.6.5+svnhead2574-0ubuntu1
ii network-manager-vpnc 0.6.4svn2422-0ubuntu3

lsb_release -rd:
Description: Ubuntu 7.10
Release: 7.10

Uname -a:
Linux annapurna 2.6.22-15-generic #1 SMP Wed Aug 20 18:39:13 UTC 2008 i686 GNU/Linux

Computer's hardware :
1st: laptop Dell Latitude D820, network hardware:
09:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5752 Gigabit Ethernet PCI Express (rev 02)
0c:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)

2nd: Dell workstation DM051, network hardware:
03:08.0 Ethernet controller: Intel Corporation 82801G (ICH7 Family) LAN Controller (rev 01)

As you can see, they are quite different.

I tried to purge completely NM packages (all the mentioned above), reboot, reinstall them, reboot; nothing to do, NM is launched, but no icon.

Regards,

C.

Revision history for this message
Cédric Jeanneret deactivated (cjeanneret-c2c-deactivated) wrote :

oh, one more thing :
when launching nm-applet in a shell as user, it complain about rights we don't have on dbus stuff [sorry, I don't have hand on this computer anymore... error message will come tomorrow morning.]

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Thank you for taking the time to report this bug and help make Ubuntu better. Unfortunately we can't fix it, because your description did not include enough information.

Please attach your /var/log/syslog and ~/.xsession-errors file to this bug report (after you experience this problem).

Thank you.

Changed in network-manager-applet:
status: New → Incomplete
Revision history for this message
Cédric Jeanneret deactivated (cjeanneret-c2c-deactivated) wrote :

Hello,
I was about to post more informations, but the users had to use his computer.
So. here is an interesting output from .xsession-errors:

** (nm-applet:6578): WARNING **: <WARN> nma_dbus_init(): could not acquire its service. dbus_bus_acquire_service() says: 'Connection ":1.21" is not allowed to own the service "org.freedesktop.NetworkManagerInfo" due to security policies in the configuration file'

We didn't change anything on those computer, just apply ubuntu updates.... It worked fine until Thursday or Friday, then.... no applet anymore.

I tried to restart dbus daemon then restart nm-applet from the shell, same error. With a "sudo nm-applet" it works, but.... we could launch it as user, before.

In syslog, we can only see that NM daemon is started, that it works (catch dhcp server, sets IP, DNS and so on).
It just appears to be a bit silly, as it deactivates eth0 many times before catching network. Network cable was plugged all the time [computer boots with it], and our network is all right (gentoo has no problem, with dhcpcd or dhclient, it find in 5s an IP for my computer)
There are some warnings:

<WARN> nm_dhcp_manager_begin_transaction(): dhcdbd not running!
[snip]
<WARN> nm_spawn_process(): nm_spawn_process('/usr/sbin/nscd -i hosts'): could not spawn process. (Failed to execute child process "/usr/sbin/nscd" (No such file or directory))

But I don't think it's related to the Applet.

We find the same logs than syslog in daemon.log

So, seems "something" in config file has changed. Maybe a group added in which we have to add our user so that it can access the dbus ressource ?

Hope it will help you.

Regards,

C.

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

This does indeed seem like a DBUS policy issue. Could you please tar the contents of /etc/dbus-1/system.d in to a tar.gz archive and attach it to this bug report.

Thanks

Revision history for this message
Cédric Jeanneret deactivated (cjeanneret-c2c-deactivated) wrote :

hi again, thanks for your quick response.
Here's the tar.gz, and groups in which my user is :
uid=1000(yves)
gid=1000(yves)
groups=1000(yves),
4(adm),
20(dialout),
24(cdrom),
25(floppy),
27(sudo),
29(audio),
30(dip),
44(video),
46(plugdev),
104(scanner),
106(fuse),
108(lpadmin),
110(admin),
115(netdev),
117(powerdev)

Regards,

C.

Revision history for this message
Cédric Jeanneret deactivated (cjeanneret-c2c-deactivated) wrote :
Download full text (3.9 KiB)

I paste here some informations. Those files are located in /etc/dbus-1/system.d/ :
NetworkManager.conf :
<!DOCTYPE busconfig PUBLIC
 "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"
 "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
<busconfig>
        <policy user="root">
                <allow own="org.freedesktop.NetworkManager"/>

                <allow send_destination="org.freedesktop.NetworkManager"/>
                <allow send_interface="org.freedesktop.NetworkManager"/>
        </policy>
        <policy user="haldaemon">
                <allow send_destination="org.freedesktop.NetworkManager"/>
                <allow send_interface="org.freedesktop.NetworkManager"/>
        </policy>
        <policy at_console="true">
                <allow send_destination="org.freedesktop.NetworkManager"/>
                <allow send_interface="org.freedesktop.NetworkManager"/>
        </policy>
        <policy context="default">
                <deny own="org.freedesktop.NetworkManager"/>
                <deny send_destination="org.freedesktop.NetworkManager"/>
                <deny send_interface="org.freedesktop.NetworkManager"/>
        </policy>

        <limit name="max_replies_per_connection">512</limit>
</busconfig>

nm-applet.conf
<!DOCTYPE busconfig PUBLIC
 "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"
 "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
<busconfig>
 <policy user="root">
  <allow own="org.freedesktop.NetworkManagerInfo"/>

  <allow send_destination="org.freedesktop.NetworkManagerInfo"/>
                <allow send_interface="org.freedesktop.NetworkManagerInfo"/>
 </policy>
 <policy at_console="true">
  <allow own="org.freedesktop.NetworkManagerInfo"/>

  <allow send_destination="org.freedesktop.NetworkManagerInfo"/>
                <allow send_interface="org.freedesktop.NetworkManagerInfo"/>
 </policy>
 <policy context="default">
  <deny own="org.freedesktop.NetworkManagerInfo"/>

  <deny send_destination="org.freedesktop.NetworkManagerInfo"/>
  <deny send_interface="org.freedesktop.NetworkManagerInfo"/>
 </policy>

        <limit name="max_replies_per_connection">512</limit>
</busconfig>

nm-openvpn-service.conf
<!DOCTYPE busconfig PUBLIC
 "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"
 "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
<busconfig>
 <policy user="root">
  <allow own="org.freedesktop.NetworkManager.openvpn"/>
  <allow send_destination="org.freedesktop.NetworkManager.openvpn"/>
  <allow send_interface="org.freedesktop.NetworkManager.openvpn"/>
 </policy>
 <policy context="default">
  <deny own="org.freedesktop.NetworkManager.openvpn"/>
  <deny send_destination="org.freedesktop.NetworkManager.openvpn"/>
  <deny send_interface="org.freedesktop.NetworkManager.openvpn"/>
 </policy>
</busconfig>

The other nm-[vpnc-service|ppp-starter] are like the latest one.

According to the error reported by nm-applet when launching it through
nm-applet
in a shell :
** (nm-applet:13017): WARNING **: <WARN> nma_dbus_init(): could not acquire its service. dbus_bus_acquire_service() says: 'Connection ":1.44" is not allowed to own the service "org.freedesktop.Network...

Read more...

Revision history for this message
Cédric Jeanneret deactivated (cjeanneret-c2c-deactivated) wrote :

oh, by the way : seems there's exactly the same issue on intrepid. just wondering how it's possible :
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/249404

Revision history for this message
Cédric Jeanneret deactivated (cjeanneret-c2c-deactivated) wrote :

so, workaround :

# cd /etc/dbus/system.d
# for i in nm-*; do sed -i 's/deny/allow/' $i; done
# sed -i 's/deny/allow/' NetworkManager.conf
# /etc/init.d/dbus restart

works fine here, but that's really ugly. I didn't found any difference between dbus on a "working machine" and the crashed one; config files in /etc/dbus are exactly the same, but.... one works, the other not.

Hope someone will find a clue, and that this workaround will be useful to others.

Regards

C.

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

Revision history for this message
Michele Mangili (mangilimic) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in network-manager-applet:
status: Incomplete → Invalid
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.