NM Cannot connect "wireless broadband": pppd_timed_out(): Looks like pppd didn't initialize our dbus module

Bug #358048 reported by ichudov
10
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Triaged
Undecided
Unassigned

Bug Description

Binary package hint: network-manager

This does not always happen, but it happens MOST of the time, and when it starts happening it never stops happening:

If I use NM to connect to my wireless broadband, it starts pppd and pppd actually connects and gets IP.

However, I see this in /var/log/syslog. After that the connection is terminated.

Any idea?

Apr 8 16:55:25 potato pppd[23083]: local IP address 173.104.47.254
Apr 8 16:55:25 potato pppd[23083]: remote IP address 68.28.153.69
Apr 8 16:55:25 potato pppd[23083]: primary DNS address 68.28.154.92
Apr 8 16:55:25 potato pppd[23083]: secondary DNS address 68.28.146.92
Apr 8 16:55:40 potato NetworkManager: <WARN> pppd_timed_out(): Looks like pppd
 didn't initialize our dbus module
Apr 8 16:55:40 potato NetworkManager: <info> (ttyUSB0): device state change: 5
 -> 9
Apr 8 16:55:40 potato NetworkManager: <debug> [1239227740.002006] nm_serial_dev
ice_close(): Closing device 'ttyUSB0'
Apr 8 16:55:40 potato pppd[23083]: Terminating on signal 15
Apr 8 16:55:40 potato pppd[23083]: Connect time 0.3 minutes.
Apr 8 16:55:40 potato pppd[23083]: Sent 0 bytes, received 0 bytes.
Apr 8 16:55:40 potato NetworkManager: <info> Marking connection 'Sprint Sierra
' invalid.
Apr 8 16:55:40 potato NetworkManager: <info> Activation (ttyUSB0) failed.

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

What is in /etc/dbus-1/system.d/nm-dhcp-client.conf ?

Did you install NM 0.7 from some PPA at some point?

Changed in network-manager (Ubuntu):
status: New → Incomplete
Revision history for this message
ichudov (igor-chudov) wrote :

> What is in /etc/dbus-1/system.d/nm-dhcp-client.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.nm_dhcp_client"/>
        </policy>
        <policy context="default">
                <deny own="org.freedesktop.nm_dhcp_client"/>
                <deny send_destination="org.freedesktop.nm_dhcp_client"/>
        </policy>
</busconfig>

> Did you install NM 0.7 from some PPA at some point?

I do not think so, though I cannot be completely certain, as I had Intrepid on this laptop.

potato:root:~ ###apt-cache policy network-manager
network-manager:
  Installed: 0.7.1~rc4.1.cf199a964-0ubuntu1
  Candidate: 0.7.1~rc4.1.cf199a964-0ubuntu1
  Version table:
 *** 0.7.1~rc4.1.cf199a964-0ubuntu1 0
        500 http://us.archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status

Revision history for this message
ichudov (igor-chudov) wrote :

> please include the network-manager and network-manager-applet package version and the ubuntu version you are running in your bug description

potato:root:~ ###apt-cache policy network-manager network-manager-gnome
network-manager:
  Installed: 0.7.1~rc4.1.cf199a964-0ubuntu1
  Candidate: 0.7.1~rc4.1.cf199a964-0ubuntu1
  Version table:
 *** 0.7.1~rc4.1.cf199a964-0ubuntu1 0
        500 http://us.archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status
network-manager-gnome:
  Installed: 0.7.1~rc4.1-0ubuntu1
  Candidate: 0.7.1~rc4.1-0ubuntu1
  Version table:
 *** 0.7.1~rc4.1-0ubuntu1 0
        500 http://us.archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status

potato:root:~ ###lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu jaunty (development branch)
Release: 9.04
Codename: jaunty

> stop networkmanager (sudo /etc/init.d/NetworkManager stop) and run it from the root shell

Does not seem to work well:

potato:root:~ ###/etc/init.d/NetworkManager stop
 * Stopping network connection manager NetworkManager
   ...done.
potato:root:~ ###NM_SERIAL_DEBUG=1 NetworkManager --no-daemon 2>&1 | tee /tmp/out.log.txt
NetworkManager: <info> starting...
NetworkManager: <WARN> nm_dbus_manager_start_service(): Could not acquire the NetworkManager service as it is already taken.
NetworkManager: <WARN> main(): Failed to start the dbus service.
NetworkManager: <info> exiting (error)

Revision history for this message
Juha Karonen (juha-karonen) wrote :

I had the same error with Ubuntu Jaunty (rc1) NBR and Nokia N95.

But if I connect the phone before I boot, the connection works. The error appears only if the phone is connected afterwards (with usb cable).

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

sorry. i misread the initial bug. please post your /etc/dbus-1/system.d/NetworkManager.conf .... dbus policy was flipped upside down at some point, so in case you still have the intrepid file, nobody would probably be allowed to call NM ppp.

Revision history for this message
ichudov (igor-chudov) wrote :

Here's my /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_destination="org.freedesktop.NetworkManager"
                       send_interface="org.freedesktop.NetworkManager.PPP"/>
        </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"/>

                <deny send_destination="org.freedesktop.NetworkManager"
                      send_interface="org.freedesktop.NetworkManager.PPP"/>
        </policy>
        <policy context="default">
                <deny own="org.freedesktop.NetworkManager"/>
                <deny send_destination="org.freedesktop.NetworkManager"/>

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

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

<!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_destination="org.freedesktop.NetworkManager"
                       send_interface="org.freedesktop.NetworkManager.PPP"/>
        </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"/>

                <deny send_destination="org.freedesktop.NetworkManager"
                      send_interface="org.freedesktop.NetworkManager.PPP"/>
        </policy>
        <policy context="default">
                <deny own="org.freedesktop.NetworkManager"/>
                <deny send_destination="org.freedesktop.NetworkManager"/>

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

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

Revision history for this message
ichudov (igor-chudov) wrote :

Sorry, I pasted it twice. Here's one copy of it to avoid confusion:

<!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_destination="org.freedesktop.NetworkManager"
                       send_interface="org.freedesktop.NetworkManager.PPP"/>
        </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"/>

                <deny send_destination="org.freedesktop.NetworkManager"
                      send_interface="org.freedesktop.NetworkManager.PPP"/>
        </policy>
        <policy context="default">
                <deny own="org.freedesktop.NetworkManager"/>
                <deny send_destination="org.freedesktop.NetworkManager"/>

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

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

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

kind of odd. did you modify your /etc/ppp/options or any other ppp related config file at some point?

Revision history for this message
ichudov (igor-chudov) wrote :

I do not believe that I modified /etc/ppp/options. I am attaching it.

Revision history for this message
João Neves (jneves) wrote :

Could you check if you have related messages in /var/log/auth.log?

Maybe something like:

Apr 25 01:43:41 home dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.42" (uid=1000 pid=6083 comm="/usr/lib/indicator-applet/indicator-applet --oaf-a") interface="org.freedesktop.DBus.Properties" member="Get" error name="(unset)" requested_reply=0 destination=":1.56" (uid=0 pid=8443 comm="/usr/lib/NetworkManager/nm-dispatcher.action "))

Revision history for this message
Peter Miller (pmiller-opensource) wrote :

I am seeing things like this

Apr 30 16:22:39 hawk dbus-daemon: Rejected send message, 7 matched rules; type="
method_call", sender=":1.55" (uid=0 pid=5953 comm="/usr/sbin/pppd nodetach lock
nodefaultroute ttyUSB") interface="org.freedesktop.NetworkManager.PPP" member="S
etState" error name="(unset)" requested_reply=0 destination="org.freedesktop.Net
workManager" (uid=0 pid=2247 comm="/usr/sbin/NetworkManager --pid-file /var/run/
Netwo"))

when NM is doing this.

Revision history for this message
Peter Miller (pmiller-opensource) wrote :

I should mention that this is on a clean Jaunty i386 install, kept up-to-date daily.

Revision history for this message
Peter Miller (pmiller-opensource) wrote :

ii network-manager 0.7.1~rc4.1.cf199a964-0ubuntu2 network management framework daemon
ii network-manager-gnome 0.7.1~rc4.1-0ubuntu2 network management framework (GNOME frontend

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

dupe of bug 371291 - check the "official workaround" in the summary

Changed in network-manager (Ubuntu):
status: Incomplete → Triaged
Revision history for this message
AIAMUZZ (muzafsh-113) wrote :

My System : Aspire One ZG5
OS : Ubuntu 10.10 (Maverick)
3G Device : Gobi 2000 (inbuilt)

sorry i seem to have been hit with this bug - a "pppd_timed_out"

The first connection throws up an almost connected log. (Attached File : First 3G connection attempt)

whereas subsequent attempts to connect throws a very minimal log. (Attached File : Second 3G connection attempt)

And i am absolutely unable to connect to the internet.

Please help me fix this issue

thanks

Revision history for this message
AIAMUZZ (muzafsh-113) wrote :

a very minimal log on second and subsequent connection attempts !!!

not sure why on second/subsequent attempts the log is not as detailed as the first attempt at connecting after bootup

help most appreciated.

thanks

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.