After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 703228 - Huawei E352 automatic lost connection after some time
Huawei E352 automatic lost connection after some time
Status: RESOLVED OBSOLETE
Product: NetworkManager
Classification: Platform
Component: ModemManager
0.9.8
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2013-06-28 08:51 UTC by Igor Gnatenko
Modified: 2014-03-10 19:28 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
lsusb -v (9.15 KB, text/plain)
2013-06-28 08:51 UTC, Igor Gnatenko
Details
modem-manager debug log (60.72 KB, text/plain)
2013-06-28 08:53 UTC, Igor Gnatenko
Details
network-manger debug log (17.21 KB, text/x-log)
2013-06-28 08:54 UTC, Igor Gnatenko
Details
lost connection from modem-manager debug log (2.79 KB, text/plain)
2013-06-28 09:01 UTC, Igor Gnatenko
Details

Description Igor Gnatenko 2013-06-28 08:51:35 UTC
Created attachment 247953 [details]
lsusb -v

Steps to reproduce:
1. Connect megafon modem (Huawei E352)
2. Connect to network with NM
3. Work in internet or wait ~ 1 minute
4. Connection lost
5. goto 2

Version:
NetworkManager-0.9.8.2-2.fc19.x86_64
ModemManager-0.6.2.0-1.fc19.x86_64

Logs and info in attached files.
Comment 1 Igor Gnatenko 2013-06-28 08:53:50 UTC
Created attachment 247954 [details]
modem-manager debug log
Comment 2 Igor Gnatenko 2013-06-28 08:54:26 UTC
Created attachment 247955 [details]
network-manger debug log
Comment 3 Igor Gnatenko 2013-06-28 09:01:37 UTC
Created attachment 247956 [details]
lost connection from modem-manager debug log
Comment 4 Aleksander Morgado 2014-03-10 19:11:57 UTC
Does this still happen? ModemManager just gets a NO CARRIER error; notifying of the network disconnection.

Would be worth trying with MM 1.x built with QMI support, as this seems to be a QMI-capable device.
Comment 5 Igor Gnatenko 2014-03-10 19:24:22 UTC
Unfortunately I can't reproduce, because don't have this modem at this time.
Comment 6 Aleksander Morgado 2014-03-10 19:28:30 UTC
I'm going to close it as obsolete. For the looks of it, could very well be a random issue in the network... If you can ever repro it with MM 1.x; please reopen. Thanks!