Bug 706770 - NetworkManager in Gnome 3 is in many ways not configurable and has many bugs
Summary: NetworkManager in Gnome 3 is in many ways not configurable and has many bugs
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: control-center
Version: rawhide
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Control Center Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-22 21:46 UTC by Rolle
Modified: 2012-05-19 02:23 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-05-19 02:23:39 UTC
Type: ---


Attachments (Terms of Use)
messages.bz2 (198.53 KB, application/x-bzip)
2011-05-22 21:46 UTC, Rolle
no flags Details
dmesg (70.17 KB, text/plain)
2011-05-22 21:47 UTC, Rolle
no flags Details

Description Rolle 2011-05-22 21:46:04 UTC
Created attachment 500308 [details]
messages.bz2

Description of problem:
Since Gnome 3 there is the new "Gnome3"-NetworkManager. Which is buggy in many ways. Sometimes a function doesn't work. The main problem is the faulty configuration-process.
I could only change options when a connection has been established. But this is useless, whenn no connection will be automatically established and the "options"-Button doesn't work.
Mobile broadband connections are seriously no configurable.
I couldn't add new connections. Here I can only choose a protocoll (VNC,...) but that doesn't help when I will add a new wired connection or a new broadband connection is impossible to edit the options, bevor I connect to the automatically configured parameters or no automaticaly.

Version-Release number of selected component (if applicable):
Fedora 15 Beta, Gnome 3

How reproducible:
Very often

Steps to Reproduce:
1. boot Fedora
2. when a wired connection (f.i. eth0)is automatically configured, disconnect the ethernet-cacble
3. try to configure that connection

4. Plugin a Surfstick
5. Wait until it is configured and try to manipulate that connection is most times unavailable

Actual results:
It doesn't work.

Expected results:
- can configure, when the cable is disconnected
- the configuration of the autmaticaly configured USB-Surfstick-connection

Additional info:

Comment 1 Rolle 2011-05-22 21:47:19 UTC
Created attachment 500309 [details]
dmesg

Comment 2 Liam Dennehy 2011-06-10 09:39:34 UTC
The GUI is lacking a method to invoke nm-connection-editor, which provides functionality for editing all connections, both for on- and offline interfaces.

I have a feeling this is simply because it doesn't conform to the new aesthetic and I happen to like the look and simplicity of the new "Network" windows, but removing the advanced connection editor from menus too is simply daft, I expect it to be around somewhere I can click to.

Google-ing for the appropriate launch command when it used to be in the menu is a regression. At the very least, put it in a menu, or add a button to kick it off from the new window.

Comment 3 Pavel Šimerda (pavlix) 2011-07-01 22:32:14 UTC
I also couldn't use Fedora 15 & NetworkManager at all without knowing nm-connection-editor and starting it from terminal.

If it can't be fixed in line with the current graphical interface, it would be good to at least provide a button and not to pretend everything works.

Comment 4 collura 2011-07-19 05:07:05 UTC
from comment#0:

   > I could only change options when a connection has been established.

on comment#0:
couldnt get to options for disconnected network.
i was trying to delete a second network from gui.
the network was trying to autoconnect [even though set not to] 
instead of the other network that was set to autoconnect [but was not connecting] (...which is another report...)

on comment#3:
yah, calling nm-connection-editor directly was pretty handy.

Comment 5 Pavel Šimerda (pavlix) 2012-03-18 22:40:27 UTC
Many things changed since this bug was reported. NM in F17/Gnome seems rather usable to me.


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