Bug 604127 - knetworkmanager Manage Connections screen is empty
Summary: knetworkmanager Manage Connections screen is empty
Alias: None
Product: Fedora
Classification: Fedora
Component: knetworkmanager (Show other bugs)
(Show other bugs)
Version: 13
Hardware: All Linux
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2010-06-15 13:29 UTC by Fred Wells
Modified: 2010-06-18 17:43 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-06-18 17:27:58 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Fred Wells 2010-06-15 13:29:00 UTC
Description of problem:

"Manage Connections" screen is empty.  Thus, unable to edit available connections.

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


How reproducible:


Steps to Reproduce:
1. Login to KDE
2. Open knetworkmanager "Manage Connections" screen from systray
3. Observe empty list
Actual results:

Empty (wired) connection list.

Expected results:

List available network interfaces

Additional info:

Comment 1 Rex Dieter 2010-06-15 15:38:22 UTC
Click "Add"

Comment 2 Fred Wells 2010-06-15 21:59:30 UTC
Why would I click "Add"?  I'm not adding a new one.  I simply want to edit an existing one.  nm-app, system-config-network each list the available interfaces whereas knetworkmanager does not.

Comment 3 Thomas Janssen 2010-06-17 19:48:39 UTC
Maybe you could explain the actual problem.

The *wired* tab is always empty. If you have a cable in your box, it gets automatically connected with it trough boot time.
What needs to be edited there?

Comment 4 Rex Dieter 2010-06-17 19:58:34 UTC
I think the reporter's expectation is to see an entry appear automatically when a wired interface is present (to match what nm-applet does).  knm currently doesn't do that, since it currently distinguishes between automatic connections and 'managed' (aka customized) ones.

(Not that knm is particularly good at doing 'managed' connections, but that's a separate topic).

anyway, If I'm correct about this, I'm not sure there's much constructive point to keeping this wishlist/rfe open in rh bugzilla (as we likely won't be the ones implementing it).

Comment 5 Fred Wells 2010-06-18 13:40:41 UTC
Rex has it right.  The user's expectation is to be able to 'manage' (as its name implies) any existing connections as well as the ability to add new ones, as nm-applet does. As an example, what if a user wants to disable (not remove) eth0 altogether and enable wlan0??

Comment 6 Thomas Janssen 2010-06-18 17:27:58 UTC
I see. Well, i'm with Rex here. We will not be the ones implementing this feature.

If you want this feature implemented file a RFE with upstreams bugtracker. http://bugs.kde.org

I will close this bug as 'notabug', though, thank you for helping to make KDE/Fedora better!

Best Regards

Comment 7 Rex Dieter 2010-06-18 17:43:03 UTC
In the meantime, if you find knetworkmanager doesn't suit your needs, you can still use nm-applet if you wish,

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