network manager doesn't restart/update actual network configuration on exit

[josh]

1) Open Network Manager
2) Wired Tab
3) Edit
4) IPv4 settings
5) Method: Manual
6) Set Address/Netmask/Gateway
7) OK
8) Close

command line: ifconfig
notice that ip address is not updated

I had to /etc/init.d/NetworkManager restart to get my new settings -- very annoying, shouldn't be that way.

[josh (josh-m-sharpe)]

Further -- I just rebooted and now those settings I added have been dropped and I'm back to an "Automatic" connection.

Wtf is an "automatic" connection anyways -- sounds like microsoft windows to me.

[goto (gotolaunchpad)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in network-manager.
For future reference you might be interested to know that a lot of applications have bug reporting functionality built in to them. This can be accessed via the Report a Problem option in the Help menu for the application with which you are having an issue. You can learn more about this feature at https://wiki.ubuntu.com/ReportingBugs.
What version of Ubuntu and network-manager do you use?

[Alexander Sack (asac)]

Launchpad Bug Tracker wrote:
> You have been subscribed to a public bug:
>
> 1) Open Network Manager
> 2) Wired Tab
> 3) Edit
> 4) IPv4 settings
> 5) Method: Manual
> 6) Set Address/Netmask/Gateway
> 7) OK
> 8) Close
>
> command line: ifconfig
> notice that ip address is not updated
>
> I had to /etc/init.d/NetworkManager restart to get my new settings --
> very annoying, shouldn't be that way.
>
>
please test the network-manager in nm team PPA for intrepid:
https://launchpad.net/~network-manager/+archive

 status incomplete

Thanks

[josh (josh-m-sharpe)]

I just installed 8.10(amd64) from scratch. I'm pretty sure I've had this
problem with the i386 version as well.

There is no network-manager binary. I think it is NetworkManager, but
executing this does nothing that I can see. NetworkManager does not accept
-v or --version options. Synaptic tells me that the network-manager package
is version 0.7~~svn20081018t105859-0ubuntu1.8.10.1 (I'm not making that
up).

Thanks.

On Wed, Dec 31, 2008 at 1:26 PM, goto <email address hidden> wrote:

> Thank you for taking the time to report this bug and helping to make Ubuntu
> better. This bug did not have a package associated with it, which is
> important for ensuring that it gets looked at by the proper developers. You
> can learn more about finding the right package at
> https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug
> as a bug in network-manager.
> For future reference you might be interested to know that a lot of
> applications have bug reporting functionality built in to them. This can be
> accessed via the Report a Problem option in the Help menu for the
> application with which you are having an issue. You can learn more about
> this feature at https://wiki.ubuntu.com/ReportingBugs.
> What version of Ubuntu and network-manager do you use?
>
> ** Changed in: network-manager (Ubuntu)
> Sourcepackagename: None => network-manager
> Status: New => Incomplete
>
> --
> network manager doesn't restart/update actual network configuration on exit
> https://bugs.launchpad.net/bugs/312749
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[goto (gotolaunchpad)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Jaunty Jackalope. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.

[Victor Vargas (kamus)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments.

Regards