[Bug 1072518] Re: Restart networking crashes dbus and the desktop manager
Dimitri John Ledkov
launchpad at surgut.co.uk
Wed Mar 19 18:13:39 UTC 2014
@ ivan-kukobko
This "sudo service network-manager restart" does not crash dbus.
This "sudo service network-interface restart" makes no-sense, as no instance is specified and it's an instance job.
Please file separate, new bugs for any issues that you have. And let
developers responsible for these component to triage them appropriately.
@ bgonza868
Read the job, and look at the events. As it stands now, stopping (or restarting networking service) is intended to only happen during shutdown. As all network interfaces are deconfigured, all network filesystems are unmounted, system dbus is stopped, all graphical user sessions are killed, network-manager/bluetooth/avahi/ofono are all stopped. This is why networking job is only supported to be started on boot, and stopped on shutdown. There is no logic to support interactive stopping or restarting this job in Ubuntu. This has nothing to do with freedesktop, other operating systems, other upstream projects, syvinit, upstart or systemd. This is purely what networking.conf upstart job supports doing as shipped in the ifupdown package in ubuntu today.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1072518
Title:
Restart networking crashes dbus and the desktop manager
Status in D-Bus:
Invalid
Status in “dbus” package in Ubuntu:
Invalid
Status in “ifupdown” package in Ubuntu:
In Progress
Status in “sysvinit” package in Ubuntu:
Invalid
Status in “upstart” package in Ubuntu:
Invalid
Bug description:
=========== WARNING ===============
Doing:
sudo restart networking
or
sudo /etc/init.d/networking restart.
============ WILL TEAR DOWN MOST OF YOUR DESKTOP =============
Networking is a generic job which brings up all networking interfaces
in the right order at boot.
It should never be stopped nor restarted.
It is only stop at shutdown to correctly bring down all the networking
interfaces in the right order again.
=========== DO NOT RESTART NETWORKING ===============
If you want to reconfigure all networking interface you can use
something like:
ifdown eth0
ifup eth0
Or all interfaces with:
ifdown -a --exclude=lo && ifup -a --exclude=lo
To manage notifications about this bug go to:
https://bugs.launchpad.net/dbus/+bug/1072518/+subscriptions
More information about the foundations-bugs
mailing list