This is not a bug but wanted behavior. Instead of forcefully breaking
connections, we're notifying (via the reboot icon in panel, or a red
power icon now) that it would be a good time after upgrading
NetworkManager to reboot. Nothing it forced upon the users :) If you
want to restart NetworkManager alone then it will work just as well;
it's just that rebooting is a sure way to know it has been restarted.
Given the risk of other changes from updates, it remains a good
practice.
Closing as Won't Fix. This is substancially better than breaking
connection with a forceful reload of NM, and we do want to avoid asking
the user for such things.
** Changed in: network-manager (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/337746
Title:
Do not require reboot on installation
Status in “network-manager” package in Ubuntu:
Won't Fix
Bug description:
Version: network-
manager_0.7~~svn20081018t105859-0ubuntu1.8.10.2_amd64.deb
In postinst there are those three lines:
# request a reboot (NM tears down interfaces on restart
# which is not the way we want to go)
/usr/share/update-notifier/notify-reboot-required
I'm not sure I exactly understand what is meant by "tears down".
Is it just the effect of "ifdown <if> ; ifup <if>" (breaking sockets,
etc...) ?
In that case reboot is much worse ! Wouldn't it be possible to
ask the user whether (s)he prefers a reboot or a tearing
down of the connections ?
Thanks !
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/337746/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
