Bug 1474067

Summary:	Cannot connect to APN with Hewlett-Packard lt4112 Gobi 4G Module Network Device
Product:	[Fedora] Fedora	Reporter:	steffen.bornemann
Component:	NetworkManager	Assignee:	Lubomir Rintel <lkundrak>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	26	CC:	alexey.maslennikov, bgalvani, dcbw, fgiudici, lkundrak
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-05-29 12:28:06 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description steffen.bornemann 2017-07-23 14:39:14 UTC

User-Agent:       Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.104 Safari/537.36
Build Identifier: 

ul 23 16:26:50 elitebook ModemManager[1064]: <warn>  Couldn't initialize PDP context with our APN: 'Serial command timed out'
Jul 23 16:26:50 elitebook ModemManager[1064]: <info>  Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> registered)
Jul 23 16:26:50 elitebook NetworkManager[1237]: <info>  [1500820010.0539] (ttyUSB1): modem state changed, 'connecting' --> 'registered' (reason: user-requested)
Jul 23 16:26:50 elitebook ModemManager[1064]: <info>  Simple connect started...
Jul 23 16:26:50 elitebook ModemManager[1064]: <info>  Simple connect state (4/8): Wait to get fully enabled
Jul 23 16:26:50 elitebook ModemManager[1064]: <info>  Simple connect state (5/8): Register
Jul 23 16:26:50 elitebook ModemManager[1064]: <info>  Simple connect state (6/8): Bearer
Jul 23 16:26:50 elitebook ModemManager[1064]: <info>  Simple connect state (7/8): Connect
Jul 23 16:26:50 elitebook ModemManager[1064]: <info>  Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
Jul 23 16:26:50 elitebook NetworkManager[1237]: <info>  [1500820010.0557] (ttyUSB1): modem state changed, 'registered' --> 'connecting' (reason: user-requested)
Jul 23 16:26:56 elitebook ModemManager[1064]: <warn>  Couldn't initialize PDP context with our APN: 'Serial command timed out'
Jul 23 16:26:56 elitebook ModemManager[1064]: <info>  Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> registered)
Jul 23 16:26:56 elitebook NetworkManager[1237]: <info>  [1500820016.0537] (ttyUSB1): modem state changed, 'connecting' --> 'registered' (reason: user-requested)
Jul 23 16:26:56 elitebook NetworkManager[1237]: <warn>  [1500820016.0538] modem-broadband[ttyUSB1]: failed to connect modem: Serial command timed out
Jul 23 16:26:56 elitebook NetworkManager[1237]: <info>  [1500820016.0538] device (ttyUSB1): state change: prepare -> failed (reason 'unknown', internal state 'managed')
Jul 23 16:26:56 elitebook NetworkManager[1237]: <warn>  [1500820016.0542] device (ttyUSB1): Activation: failed for connection 'Telekom MultiSIM'
Jul 23 16:26:56 elitebook NetworkManager[1237]: <info>  [1500820016.0547] device (ttyUSB1): state change: failed -> disconnected (reason 'none', internal state 'managed')


-----
Latest Firmware flashed.
Settings for T-Mobile are correct from KDE.
Works in Debian Stretch and Windows.
Signal Strength and Carrier and Access Technology are shown correctly.


Reproducible: Always

Steps to Reproduce:
1.Create a new Mobile Broadband Connection
2.Choose the LTE Modem, Country and Telekom/T-Mobile Plan
3.Try to connect.
Actual Results:  
NetworkManager tries to connect for a long time and stops then. Connect Button could be pressed again.

Expected Results:  
Connect with Telekom APN and receive an IP Adress.

Comment 1 steffen.bornemann 2017-08-11 09:26:31 UTC

do you need more information?

Comment 2 Fedora End Of Life 2018-05-03 08:08:43 UTC

This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2018-05-29 12:28:06 UTC

Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
is no longer maintained, which means that it will not receive any
further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.