Bug 695038 - Network icon in top bar shows unnamed interfaces, Network settings show limit information
Summary: Network icon in top bar shows unnamed interfaces, Network settings show limit...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 15
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-09 23:28 UTC by Matt Willsher
Modified: 2012-07-10 17:23 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-07-10 17:23:06 UTC
Type: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Matt Willsher 2011-04-09 23:28:02 UTC 
Description of problem:

Upon clicking the little network icon in the top bar, the drop down shows the following:

Wired   ON
        OFF
        OFF
        ON

Network Settings

I have 3 NICS and I can't tell what is connected or what the mystery ON entry is. 

Upon going to the network settings I see three Wired entries, one of which is is connected, two of which aren't. The connected one has a static IP assigned but doesn't show the IP address only the connection speed and MAC address. 

Upon configuring the options for the connected NIC, they are not applied. The NIC needs to switched off and on again.

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


How reproducible:

Consistent

Steps to Reproduce:
1.
2.
3.
  
Actual results:

As above

Expected results:

Drop down shows names as assigned in the network settings. Network settings names should assigned names rather than wired. 
Settings can be applied and saved rather than having the need to turn off then on again the NIC.

Additional info:
Comment 1 Dan Winship 2011-04-20 20:53:31 UTC 
This should be mostly fixed by 3.0.1 next week-ish
Comment 2 Dan Winship 2012-07-10 17:23:06 UTC 
(In reply to comment #1)
> This should be mostly fixed by 3.0.1 next week-ish

which was a long time ago now
Note You need to log in before you can comment on or make changes to this bug.