Hi thread. Sebastien, personally, I attempted to use that command several times already with the intent to reset my networking subsystem state. Because of some other bug, my system stops resolving hostnames at some point, and redoing the connection is the easiest way to make network operational again. And oftentimes, the simple CLI command is more accessible than half a dosen clicks.
In short: I want to `restart networking` simply because I've restarted each and every service out there, and it was always fine. At least, it never ended up in any loss of my working data. As a bonus, `restart <anyservice>` restarted *only* the service requested, not the whole desktop session. So, either the manual invokation of `/etc/init.d/networking restart` should require an interactive confirmation (with appropriate warnings about data loss), or even reject the command altogether. Or alternatively, if the `networking` service doesn't represent the networking subsystem itself, then it should be renamed. Or, if it does, then the question shall be answered: what's the bloody business networking subsystem has to do with DBus system bus? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1072518 Title: Restarting network crashes (apparently) the desktop manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1072518/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
