Bug 1244725

Summary: The Mobile Broadband does not initialize and gets deactivated almost immediately.
Product: [Fedora] Fedora Reporter: samuel.matende
Component: ModemManagerAssignee: Lubomir Rintel <lkundrak>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 22CC: dcbw, me
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-03-31 13:03:40 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description samuel.matende 2015-07-20 11:27:27 UTC 
Description of problem:

Once the modem is attached, I am prompted to provide the SIM PIN which is accepted and the modem is recognised and listed as one of the possible network connections under Networks. To connect to the Wireless Mobile Broadband network, I click on the network provider. This reports that "The Modem has failed to initialize" then "The xxxxxxx (provider) connection has been deactivated"

Version-Release number of selected component (if applicable):

ModemManager-1.4.6-1.fc22.i686

How reproducible:

Modem connection has not worked since the upgrade from f21 to f22

Steps to Reproduce:
1.
2.
3.

Actual results:

(i) Modem has failed to initialize
(ii) The xxxxxx connection has been deactivated.

Expected results:

Connection to the Wireless Mobile Broadband network

Additional info:
Comment 1 Fedora Admin XMLRPC Client 2015-08-18 14:54:24 UTC 
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 2 Pete Travis 2015-08-27 18:41:29 UTC 
Unflagging for relnotes.  If you can reproduce on F23, please discuss with Fedora QA about replicating the issue and submitting for the commonbugs report.
Comment 3 Lubomir Rintel 2016-03-31 13:03:40 UTC 
Please re-open the bug report with more information.

Specifically, please capture the logs:

$ su
# journalctl -fl |tee log.txt
<attempt to activate the connection>
<press CTRL+C>
#

...and attach log.txt

Thanks.