Bug 703613 - NetworkManager cannot be configured
Summary: NetworkManager cannot be configured
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 15
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-10 19:46 UTC by Onyeibo Oku
Modified: 2012-08-07 15:58 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-07 15:58:47 UTC
Type: ---


Attachments (Terms of Use)
xsession logs (1.96 KB, application/x-gzip)
2011-05-12 14:24 UTC, Onyeibo Oku
no flags Details

Description Onyeibo Oku 2011-05-10 19:46:09 UTC
Description of problem:
Attempting to configure NM through 'System Settings' on user menu brings up the new Control-Centre.  The two LAN ports on my Desktop show up but are permanently disabled.  All buttons are frozen making it impossible to configure NM.

Going through nm-connection-editor (from the terminal), I'm able to set manual IP addresses, and change Connection name, but the 'Save' button remains disabled.

Version-Release number of selected component (if applicable):
NetworkManager-0.8.999-1.fc15.x86_64

How reproducible:
Did the installation Twice ... same result


Steps to Reproduce:
1. Run Installation on Fedora 15 (Beta)
2. Boot up and attempt a network Configuration
3. In my case, either you can't access the editor from 'System Settings'->Network, OR you can't save changes if you go through the terminal (nm-connection-editor)
  
Actual results:
1. Cannot access UI to change LAN settings from Control Centre
2. Cannot Save changes made through nm-connection-editor

Expected results:
1. Access the setup UI from 'System Settings'->Network
2. Be able to save changes made with nm-connection-editor


Additional info:

Comment 1 Jirka Klimes 2011-05-11 08:34:08 UTC
"Options..." button in Network control-center is disabled unless a connection is activated (it is used to open editor for active connection).
You should be able to click on ON/OFF switch to connect.

'Save" button in the editor is disabled when some configuration is invalid (e.g. you select Manual method, but don't enter any IP). Please check that you enter connect data. Do you see any errors in .xsession-errors?

Comment 2 Onyeibo Oku 2011-05-12 14:24:09 UTC
Created attachment 498555 [details]
xsession logs

Comment 3 Onyeibo Oku 2011-05-12 14:44:00 UTC
(In reply to comment #1)
> "Options..." button in Network control-center is disabled unless a connection
> is activated (it is used to open editor for active connection).
> You should be able to click on ON/OFF switch to connect.
> 
> 'Save" button in the editor is disabled when some configuration is invalid
> (e.g. you select Manual method, but don't enter any IP). Please check that you
> enter connect data. Do you see any errors in .xsession-errors?

Switching the buttons you suggested this is what happens:
The Dialogue says 'Connecting' for a few minutes then disconnects
I have attached .xsession-error files.

The setup I have performed on this machine is not unique.  I have done similar setups on other systems.  So you can be rest assured that the nm-connection-editor settings were correct.

Comment 4 Jirka Klimes 2011-05-13 09:58:07 UTC
Please run nm-connection-editor in a terminal and post what it spits.
Also, could you grab /var/log/messages from NetworkManager startup (there are messages about reading the connections).

Comment 5 Onyeibo Oku 2011-05-13 22:16:14 UTC
Strange

For the first time in weeks, nm-connection-editor worked as expected.  Saved the network configuration and it recognized both ports perfectly.  I'll watch this trend again.

Comment 6 Fedora End Of Life 2012-08-07 15:58:50 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached 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 to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

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.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


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