|
Done, but when I try to enable the modem with "[sudo] mmcli -m 0
-e" (or also with "mmcli -L") I get "couldn't find the ModemManager
process in the bus"... I've checked with "ps -def" and gdb+MM seems
running. Only for curiosity, why Ubuntu "stock" MM+NM enables the modem by itself and latest MM+NM does not? Thank you On 27/03/2013 19:45, Aleksander Morgado
wrote:
On 27/03/13 17:49, Enrico Murador - Research & Development - CET wrote:On 27/03/2013 17:36, Aleksander Morgado wrote:That sequence is extremely strange... Was there any MM crash in between?Yes... I've taken a quick look, the ModemManager PID changes just after the completion of "mmcli -m 0 -e" command (after writing "successfully enabled").Then, please manually run it like this: $> sudo mv /usr/sbin/ModemManager / $> sudo killall -9 ModemManager $> sudo gdb --args /ModemManager --debug Re-run the sequence, and once it crashes, and still within gdb, run "bt". That should give us the backtrace. Also attach the debug logs whenever you get them. You may need to install additional packages (debug symbols) to get a good backtrace, though. Or, otherwise, just get the latest MM from git and compile it yourself. After the test, just do this to recover the original place for the ModemManager file: $> sudo mv /ModemManager /usr/sbin --
Enrico Murador R&D
|
