Bug 836425

Summary: Activating a connection under Mobile Broadband does not turn the switch to "ON"
Product: [Fedora] Fedora Reporter: Ankur Sinha (FranciscoD) <sanjay.ankur>
Component: gnome-shellAssignee: Owen Taylor <otaylor>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: danw, dcbw, jklimes, maxamillion, otaylor, samkraju, shaikhnavid14, walters
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 14:19:04 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:
Attachments:
Description Flags
Screenshot showing mobile broadband connected but switch still in OFF state
none
Another screenshot showing mobile broadband connected but switch still in OFF state none

Description Ankur Sinha (FranciscoD) 2012-06-29 04:21:33 UTC
Created attachment 595173 [details]
Screenshot showing mobile broadband connected but switch still in OFF state

Description of problem:
When I select one of my mobile broadband connections, the switch does not turn ON when the connection is activated

Version-Release number of selected component (if applicable):
NetworkManager-0.9.4.0-9.git20120521.fc17.x86_64


How reproducible:
Always

Steps to Reproduce:
1. Connect a USB mobile broadband dongle and wait for applet to list it
2. Click on the name to activate it, wait for it to activate
3. Click the applet
  
Actual results:
The mobile broadband switch is still OFF, in spite of the connection being active

Expected results:
The switch should turn on.

Additional info:
--

Comment 1 Ankur Sinha (FranciscoD) 2012-06-29 04:22:02 UTC
Created attachment 595174 [details]
Another screenshot showing mobile broadband connected but switch still in OFF state

Comment 2 Jirka Klimes 2012-07-12 11:32:03 UTC
If the connection is correctly established by NM, the problem is gnome-shell's network-indicator.

The connection should be listed:
$ nmcli con status
$ nmcli dev status

Comment 3 Ankur Sinha (FranciscoD) 2012-07-13 11:08:50 UTC
(In reply to comment #2)
> If the connection is correctly established by NM, the problem is
> gnome-shell's network-indicator.
> 
> The connection should be listed:
> $ nmcli con status
> $ nmcli dev status

Hi Jirka,

Confirming that the connection is correctly established and that nmcli works as expected:

[ankur@ankur ~]$ nmcli con status
NAME                      UUID                                   DEVICES    DEFAULT  VPN   MASTER-PATH
Tata Indicom (Photon+) connection 385059f4-5895-4a3b-8b2f-19af8e66a312   ttyUSB0    yes      no    not set
[ankur@ankur ~]$ nmcli dev status
DEVICE     TYPE              STATE
ttyUSB0    cdma              connected
7C:61:93:B8:F6:4E bluetooth         disconnected
p1p2       802-3-ethernet    unavailable
wlan0      802-11-wireless   unavailable
[ankur@ankur ~]$

Thanks for changing the component to the correct one. 

Thanks,
Warm regards,
Ankur

Comment 4 Fedora End Of Life 2013-04-03 16:39:45 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 5 Fedora End Of Life 2015-01-09 17:13:31 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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 6 Fedora End Of Life 2015-02-17 14:19:04 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.