dbus-daemon rejects NetworkManager messages

Bug #368204 reported by Michael Stiller
2
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Expired
Low
Unassigned

Bug Description

Binary package hint: network-manager

Mobile Broadband connections do not work in Ubuntu 9.04, dbus messages from pppd to the NetworkManager
are rejected due to a broken /etc/dbus-1/system.d/NetworkManager.conf. Due to the rejected messages, NetworkManager runs into a timeout and kills the established connection.

/var/log/messages:
Apr 27 19:57:03 blackberry NetworkManager: <WARN> pppd_timed_out(): Looks like pppd didn't initialize our dbus module
/var/log/auth.log:
...
Apr 27 21:59:30 blackberry dbus-daemon: Rejected send message, 8 matched rules; type="method_call", sender=":1.48" (uid=0 pid=5446 comm="/usr/sbin/pppd nodetach lock nodefaultroute user v") interface="org.freedesktop.NetworkManager.PPP" member="SetState" error name="(unset)" requested_reply=0 destination="org.freedesktop.NetworkManager" (uid=0 pid=3241 comm="/usr/sbin/NetworkManager --pid-file /var/run/Netwo"))
Apr 27 21:59:30 blackberry dbus-daemon: Rejected send message, 8 matched rules; type="method_call", sender=":1.48" (uid=0 pid=5446 comm="/usr/sbin/pppd nodetach lock nodefaultroute user v") interface="org.freedesktop.NetworkManager.PPP" member="SetIp4Config" error name="(unset)" requested_reply=0 destination="org.freedesktop.NetworkManager" (uid=0 pid=3241 comm="/usr/sbin/NetworkManager --pid-file /var/run/Netwo"))
...

This is:

Description: Ubuntu 9.04
Release: 9.04
root@blackberry:/etc/dbus-1/system.d# apt-cache policy network-manager
network-manager:
  Installed: 0.7.1~rc4.1.cf199a964-0ubuntu2
  Candidate: 0.7.1~rc4.1.cf199a964-0ubuntu2
  Version table:
 *** 0.7.1~rc4.1.cf199a964-0ubuntu2 0
        500 http://de.archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status

FIX:

I got it to work by commenting the following lines in /etc/dbus-1/system.d/NetworkManager.conf:

                <!--
                <deny send_destination="org.freedesktop.NetworkManager"
                      send_interface="org.freedesktop.NetworkManager.PPP"/>
                -->

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

some reporters claimed that rebooting suddenly fixes this. Did you try that without changing the config?

Changed in network-manager (Ubuntu):
status: New → Incomplete
Revision history for this message
Michael Stiller (ms-2scale) wrote :

Yes, tried that. I think the config must be changed because it looks like a documented feature.
See man dbus-daemon, the section about policies:

       Policies are applied to a connection as follows:
          - all context="default" policies are applied
          - all group="connection’s user’s group" policies are applied
            in undefined order
          - all user="connection’s auth user" policies are applied
            in undefined order
          - all at_console="true" policies are applied
          - all at_console="false" policies are applied
          - all context="mandatory" policies are applied

       Policies applied later will override those applied earlier, when the
       policies overlap. Multiple policies with the same user/group/context
       are applied in the order they appear in the config file.

Looked to me like the at_console policy denies the sending of the messages, because
it is applied after the user = root policy. In the logs one could clearly see, that there were messages
denied due to some config rules.

Revision history for this message
Victor Vargas (kamus) wrote :

Since this report have a long time without activity, please could you check (if is possible) in latest version included in Karmic if this issue is still happening? Thanks in advance.

Changed in network-manager (Ubuntu):
importance: Undecided → Low
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.