Bug 1244725 - The Mobile Broadband does not initialize and gets deactivated almost immediately.
Summary: The Mobile Broadband does not initialize and gets deactivated almost immediat...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: ModemManager
Version: 22
Hardware: i386
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-20 11:27 UTC by samuel.matende
Modified: 2016-03-31 13:03 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-03-31 13:03:40 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

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.


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