Bug 923800 - Unable to connect to Internet using Huawei K3765 USB Modem
Summary: Unable to connect to Internet using Huawei K3765 USB Modem
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 18
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-20 13:26 UTC by Raul Casado
Modified: 2014-02-05 20:08 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-05 20:08:40 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
yum info NetworkManager (1.43 KB, text/plain)
2013-03-20 13:26 UTC, Raul Casado
no flags Details
Dmesg extract (1.44 KB, text/plain)
2013-03-20 13:27 UTC, Raul Casado
no flags Details
syslog extract (19.17 KB, text/plain)
2013-03-20 13:28 UTC, Raul Casado
no flags Details

Description Raul Casado 2013-03-20 13:26:35 UTC
Created attachment 713246 [details]
yum info NetworkManager

Description of problem:
After pluging a Huawei K3765 and setting a ISP profile, there is no way to connect to Internet.

The modem seems to be detected. Even you can set up and ISP profile (vía nm-connection-editor seems otherwise there is no response). But when you choose to connect to your ISP from the dropdown list in the Network Manager (NM) desktop icon, nothing seems to happen.

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


How reproducible:
Get a Huawei K3765 USB 3G Modem, plug it, set an ISP provider profile and try to connect.

Steps to Reproduce:
1. Plug a Huawei K3765 (see dmesg extrat and syslog)
2. Activate Mobile Broandband through the NetworkManager desktop icon
3. Set an ISP (I wasn't able to do it through NetworkManager, so i run 'nm-connection-editor')
4. Try to connect (see syslog extract)
  
Actual results:
Nothing happens

Expected results:
Icon NM change to GSM/HSDPA and have access to Internet

Additional info:
dmesg, yum info and syslog extract attached

Comment 1 Raul Casado 2013-03-20 13:27:35 UTC
Created attachment 713247 [details]
Dmesg extract

dmesg extract

Comment 2 Raul Casado 2013-03-20 13:28:31 UTC
Created attachment 713249 [details]
syslog extract

Syslog extract

BTW, it was working fine in F17

Comment 3 Fedora End Of Life 2013-12-21 12:19:24 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 
'version' of '18'.

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 prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 to Fedora 18's end of life.

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 4 Fedora End Of Life 2014-02-05 20:08:40 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.


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