Originally reported by tbys on 2012-10-29: Issuing: sudo restart networking or sudo /etc/init.d/networking restart causes dbus to shutdown, bringing down the desktop manager and does not restart gracefully. Renders the UX useless and forces user to drop to tty1 to fix. This bug is discussed at length in https://bugs.launchpad.net/ubuntu/+bug/1072518 But the above summary accurately describes the problem. Reporting to dbus devs as no relevant bug was found in this bugzilla and is assumed that this is the first notification. As of yet, it is unknown what party is responsible for correcting the problem, but 119 users have reported being affected by this bug. Ubuntu devs have remained quiet thus far. We the users, would appreciate any guidance and would whole-heartedly appreciate a solution.
(In reply to comment #0) > Issuing: > > sudo restart networking > > or > > sudo /etc/init.d/networking restart > > causes dbus to shutdown, bringing down the desktop manager and does not > restart gracefully. Renders the UX useless and forces user to drop to tty1 > to fix. That works fine on my Debian system with systemd; dbus is not restarted. I suspect this might be a problem with the Upstart init integration, which is an Ubuntu addition and is not maintained on freedesktop.org. Resolving as NOTOURBUG, please take this up with the people who ship that Upstart job. If it's the same as the patch proposed on <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712167>, the culprit is probably the "stop on deconfiguring-networking" stanza in the Upstart job. Restarting the system dbus-daemon is not a supported action.
Thanks. Next step will be as you've suggested. Also will contact contact Upstart for guidance.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.