Created attachment 1175374 [details] ModemManager log Description of problem: Since a few weeks I am not able to connect to a mobile network anymore with a Huawwei ME906s-158 modem in a ThinkPad T460p. It used to work sporadically when cold booting the machine (suspend-resume broke it), but now it doesn't. What I noticed is that event though you can create a new configuration for the modem in the gnome network settings, after the assistant finishes the new connection is nowhere to be found and thus can't be selected to connect with. Also, trying to enable the modem from the system menu (top right) in gnome shell does nothing at all. Trying to connect from the command line with 'mmcli -m 0 --simple-connect="apn=internet"' (apn works on my phone with the same operator) results in 'error: couldn't connect the modem: 'GDBus.Error:org.freedesktop.ModemManager1.Error.MobileEquipment.NetworkTimeout: Network timeout'' debug output of ModemManager is attached. Version-Release number of selected component (if applicable): 1.6 / 0.3.rc3.fc24 How reproducible: try to connect to a network with Huawei ME906s-158 using either the gnome network settings UI or mmcli with 'mmcli -m 0 --simple-connect="apn=internet"' Actual results: Modem does not connect. the UI doesn't event show that it tries to connect. Expected results: The UI shows that it is trying to connect; the modem actually connects to the network. Additional info: I did a fresh install last week from a live USB. In this session I was able to connect. Maybe there was a regression in ModemManager.
correction: connection works again after cold booting, suspend/resume still breaks the ability to connect. should I create a new bug for that?
Hi, thanks for reporting. Can you please provide the output of: mmcli -m <your modem id> after a cold boot (when is working) and also after a suspend resume (when it is not working)?
Created attachment 1178966 [details] mmcli output after suspend (doesn't work)
Created attachment 1178967 [details] mmcli output after reboot (works)
I just resumed, tried to connect (didn't work), ran mmcli -m 0, rebooted, connected (did work), ran mmcli -m 0 a second time. Outputs attached.
you can work around this issue by restarting NetworkManager.service, so it seems to be a problem of ModemManager not initializing things properly after resume.
Hi, thanks for the report. I think this is fixed in the ModemManager package that is now in testing. Please try the updated packages from the bug #1341303 and reopen this bug if the problem persists. Thank you Lubo *** This bug has been marked as a duplicate of bug 1341303 ***