>> I have found another issue that I am not sure if it is a bug or not. It
>> seems that the ModemManager cannot detect the first time that I insert the
>> modem.
>> > After try with many ports it prints the next lines:
>> > ModemManager[7749]: <debug> [1361368039.448167] [mm-serial-port.c:994]
>> > mm_serial_port_close(): (ttyUSB0) device open count is 0 (close)
>> > ModemManager[7749]: <debug> [1361368039.448198] [mm-serial-port.c:1010]
>> > mm_serial_port_close(): (ttyUSB0) closing serial port...
>> > ModemManager[7749]: <debug> [1361368039.449123] [mm-serial-port.c:1041]
>> > mm_serial_port_close(): (ttyUSB0) serial port closed
>> > ModemManager[7749]: <debug> [1361368039.449164] [mm-serial-port.c:1109]
>> > mm_serial_port_close_force(): (ttyUSB0) forced to close port
>> > ModemManager[7749]: <debug> [1361368039.449231] [mm-plugin-manager.c:352]
>> > plugin_supports_port_ready(): (Plugin Manager) (Huawei) [ttyUSB0] found
>> > best plugin for port
>> > ModemManager[7749]: <debug> [1361368039.449274] [mm-plugin-manager.c:238]
>> > port_probe_context_finished(): (Plugin Manager) 'ttyUSB0' port probe
>> > finished, last one in device, but minimum probing time not consumed yet
>> > ('24.443516' seconds elapsed)
>> >
>> > But If I unplug and plug it again it will recognize the modem.
>> >
> Ah, my heisenbug. Yes, I've been the whole morning trying to reproduce
> it after I saw it yesterday. We configure a timeout to be run 2s after
> we initialize the device probing, but for some reason it doesn't get
> fired. Nice to see that I'm not the only one seeing it, will try to
> track it down these days. Do you have a full debug log of this issue
> happening? Or just that snippet?
Pushed a fix to handle this issue; let me know if you see it again.
Cheers!
--
Aleksander
_______________________________________________
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list
