On Fri, Feb 20, 2009 at 08:59:57AM -, nullack wrote:
I am sure it is a regression because I used to be able to edit the MTU
under Intrepid, and now with Jaunty I am prevented from doing so. Please
refer to bug #258743.
This isnt a regression ... in intrepid it was a bug that the UI
I attempted to reproduce this bug with an install based on the ubuntu
live cd (build 20090305.1) and it looks to me like this issue has been
addressed; I am able to edit wired network settings, including MTU (and
it appears to be persistent across reboots, so bug #258743 may also be
fixed.)
Are you sure that this is a regression? Indeed you can't edit
automatically generated connections, but it's possible to delete them
and create a manual configuration for e. g. your ethernet connection.
That works well.
** Changed in: network-manager (Ubuntu Jaunty)
Importance: High = Medium
I am sure it is a regression because I used to be able to edit the MTU
under Intrepid, and now with Jaunty I am prevented from doing so. Please
refer to bug #258743.
--
Wrong Network Manager Security Defaults
https://bugs.launchpad.net/bugs/328928
You received this bug notification because you
Yes, Martin, I verified that in intrepid, I could edit things like the
MTU and whether the ip address was dhcp or static before marking as a
regression. Though it is worth pointing out that in intrepid, any such
changes would not survive a reboot.
That said, regardless of whether it's a
Steve Beattie [2009-02-20 17:28 -]:
Though it is worth pointing out that in intrepid, any such changes
would not survive a reboot.
Ah, maybe that's the reason why the change was made in the first
place?
. If it's intended behavior that auto interfaces are not to be
edited, then the UI
I see this as well, confirming. This is with network-manager
0.7.1~rc1-0ubuntu2 and network-manager-gnome
0.7.1~rc1+20090219+bzr974-0ubuntu1. Marking as a regression against
intrepid's behavior.
** Changed in: network-manager (Ubuntu)
Status: New = Confirmed
** Changed in: network-manager
