Bug 22429 - pppd_timed_out(): Looks like pppd didn't initialize our dbus module
: pppd_timed_out(): Looks like pppd didn't initialize our dbus module
Status: CLOSED FIXED
: Sisyphus
(All bugs in Sisyphus/ModemManager)
: unstable
: all Linux
: P3 normal
Assigned To:
:
:
:
:
:
  Show dependency tree
 
Reported: 2009-12-02 11:51 by
Modified: 2010-01-25 15:12 (History)


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2009-12-02 11:51:21
ModemManager увидел мой телефон (подключенный через USB-serial-порт). Однако
подключение не проходит:
Dec  2 12:46:49 ildar NetworkManager: <info>  Activation (ttyUSB0) starting
conn
ection 'KCell' 
Dec  2 12:46:49 ildar NetworkManager: <info>  (ttyUSB0): device state change: 3 
-> 4 (reason 0) 
Dec  2 12:46:49 ildar NetworkManager: <info>  Activation (ttyUSB0) Stage 1 of 5 
(Device Prepare) scheduled... 
Dec  2 12:46:49 ildar NetworkManager: <info>  Activation (ttyUSB0) Stage 1 of 5
(Device Prepare) started... 
Dec  2 12:46:49 ildar NetworkManager: <info>  Activation (ttyUSB0) Stage 1 of 5
(Device Prepare) complete. 
Dec  2 12:46:49 ildar modem-manager: (ttyUSB0) opening serial device...
Dec  2 12:46:50 ildar NetworkManager: <info>  Activation (ttyUSB0) Stage 2 of 5
(Device Configure) scheduled... 
Dec  2 12:46:50 ildar NetworkManager: <info>  Activation (ttyUSB0) Stage 2 of 5
(Device Configure) starting... 
Dec  2 12:46:50 ildar NetworkManager: <info>  (ttyUSB0): device state change: 4
-> 5 (reason 0) 
Dec  2 12:46:51 ildar NetworkManager: <info>  Activation (ttyUSB0) Stage 2 of 5
(Device Configure) successful. 
Dec  2 12:46:51 ildar NetworkManager: <info>  Activation (ttyUSB0) Stage 3 of 5
(IP Configure Start) scheduled. 
Dec  2 12:46:51 ildar NetworkManager: <info>  Activation (ttyUSB0) Stage 2 of 5
(Device Configure) complete. 
Dec  2 12:46:51 ildar NetworkManager: <info>  Activation (ttyUSB0) Stage 3 of 5
(IP Configure Start) started... 
Dec  2 12:46:51 ildar NetworkManager: <info>  (ttyUSB0): device state change: 5
-> 7 (reason 0) 
Dec  2 12:46:51 ildar NetworkManager: <info>  Starting pppd connection 
Dec  2 12:46:51 ildar pppd[13028]: Plugin /usr/lib/pppd/2.4.4/nm-pppd-plugin.so
loaded.
Dec  2 12:46:51 ildar pppd[13028]: pppd 2.4.4 started by root, uid 0
Dec  2 12:46:51 ildar NetworkManager: <info>  Activation (ttyUSB0) Stage 4 of 5
(IP6 Configure Get) scheduled... 
Dec  2 12:46:51 ildar NetworkManager: <info>  Activation (ttyUSB0) Stage 3 of 5
(IP Configure Start) complete. 
Dec  2 12:46:51 ildar NetworkManager: <info>  Activation (ttyUSB0) Stage 4 of 5
(IP6 Configure Get) started... 
Dec  2 12:46:51 ildar NetworkManager: <info>  Activation (ttyUSB0) Stage 4 of 5
(IP6 Configure Get) complete. 
Dec  2 12:46:51 ildar pppd[13028]: Using interface ppp0
Dec  2 12:46:51 ildar pppd[13028]: Connect: ppp0 <--> /dev/ttyUSB0
Dec  2 12:47:11 ildar NetworkManager: <WARN>  pppd_timed_out(): Looks like pppd
didn't initialize our dbus module 
Dec  2 12:47:11 ildar NetworkManager: <info>  (ttyUSB0): device state change: 7
-> 9 (reason 14) 
Dec  2 12:47:11 ildar pppd[13028]: Terminating on signal 15
Dec  2 12:47:11 ildar NetworkManager: <info>  Marking connection 'KCell'
invalid. 
Dec  2 12:47:11 ildar NetworkManager: <info>  Activation (ttyUSB0) failed. 

P.S. хотелось бы знать, что пришло на смену
    /lib/udev/nm-modem-probe --verbose --export /dev/ttyUSBx
у ModemManage-а больше нет nm-modem-probe
------- Comment #1 From 2010-01-09 22:06:11 -------
(In reply to comment #0)
> P.S. хотелось бы знать, что пришло на смену
>     /lib/udev/nm-modem-probe --verbose --export /dev/ttyUSBx
> у ModemManage-а больше нет nm-modem-probe

MM и пришел. Он сам выполняет опрос модема.

Если проблема актуальна на текущей версии, то от root выполните
service NetworkManager stop
NM_PPP_DEBUG=1 /usr/sbin/NetworkManager --no-daemon
Покажите вывод при попытке подключения.
------- Comment #2 From 2010-01-25 15:12:44 -------
с последними версиями MM все проблемы пропали, и отлаживать стало нечего.

# NM_PPP_DEBUG=1 NM_SERIAL_DEBUG=1 /usr/sbin/NetworkManager --no-daemon
похоже, практически лучшее средство для отладки подобных проблем.
Спасибо.