GNOME Bugzilla – Bug 562685
Impossible to edit a connection created during the installation or hamachi connection
Last modified: 2009-12-28 03:59:51 UTC
Please describe the problem: I have two wire connections : eth0, created at boot, and ham0, a connection created by hamachi. I can edit neither. Steps to reproduce: 1. Install a brand new Fedora 10 while connected to your *box 2. open nm-connection-editor as a normal user by right-clicking on the applet 3. select connection eth0 4. try to edit it Actual results: All Fields are disabled, only the Discard button is enabled Expected results: To edit my connection, and to connect as root when clicking on the "Apply" button Does this happen every time? yes Other information:
Create a new connection with the settings you need, by clicking the "Add" button.
Thank you, I know this workaround (and another one, which is remove nm and use ifconfig), I just wanted to report this bug (because it IS a bug, isn't it?).
Not really, that connection is a read-only connection, hence why it's grayed out. If you create a new wired connection, that "automatic" one will go away.
Ok, but you may agree that it is quite strange for a normal user not to be able to do anything for this connection (and very, very strange for the superuser). When I try to edit this connection, I can see two keys in front of the "Apply" button, so I would tend to think that after editing the connection, I would have to authenticate as root, and everything would be fine... why not? Thanks for your answers.
I created a new wired connection, but the old one won't go away, nm-settings.c tells me on line 333 :"Read-only connections may not be deleted". Quite logic in fact. What can I do (if not with the GUI, maybe someting could be done with the CLI) Bye
I have the same problem. Besides it says that the device is not managed and I have a connection called "ifupdown (eth0)" and says never. This is my /etc/network/interfaces. auto lo
I solved the problem by restarting the system. Maybe I should have restart some service but I do not know which one. Does anybody knows why?
Is this still an issue with the latest F-10 NM update? If so, what specific NM version are you running?
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!