** Also affects: sysvinit (Ubuntu)
Importance: Undecided
Status: New
--
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:
Restart networking crashes dbus and the desktop manager
Please take a look at
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1072518 and let us
know if this is the same issue or not.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273462
Title:
Multiple users affected
** Changed in: sysvinit (Ubuntu)
Status: New = Confirmed
--
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:
Restart networking crashes dbus and the desktop
Multiple users affected
** Changed in: upstart (Ubuntu)
Status: New = Confirmed
--
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:
Restart networking crashes dbus and the desktop
** Branch linked: lp:ubuntu/sysvinit
--
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:
Restart networking crashes dbus and the desktop manager
To manage notifications about this bug go
Restarting the networking subsystem is not a task that a user would need
to complete on a regular basis. I grant you that. However, there are a
few times that this is necessary and it is not acceptable to respond: a)
don't perform said task or b) perform it using another command X
The problem is
@Vincas
Thanks for the information. I had not read about the formal decision. However,
you are still agreeing with me that sysvinit is deprecated. So whether it's for
Upstart or Systemd, the existence of the now defunct networking init script
still needs to be addressed since for the forseeable
Also, I forgot to mention: Simon McVittie over on freedesktop confirms
that both
/etc/init.d/networking restart
and
restart networking
function as expected (correctly, no crashes) in Debian with systemd. So
this observation adds to why I think it's an upstart or sysvinit issue.
--
You
At Simon McVittie's suggestion (from dbus @freedesktop.org) and reding
some of the comments from the bug duplicates of this bug. The general
thought is that the Upstart/Sysvinit conflict may lie at the root of
this issue. Since 2 Ubuntu LTS releases ago, the dev's decided to use
Upstart for the
@Dimitri Thanks for the patch. This was all about tying up loose ends.
Many unofficial resources on the web and some official ones too
explicitly direct users to directly invoke that particular script.
Which, if you are not in the loop, as I was and apparently another 119
users were, will lead you
Reported issue to freedesktop as they maintain dbus
** Bug watch added: freedesktop.org Bugzilla #76344
https://bugs.freedesktop.org/show_bug.cgi?id=76344
** Also affects: dbus via
https://bugs.freedesktop.org/show_bug.cgi?id=76344
Importance: Unknown
Status: Unknown
--
You
** Package changed: ubuntu = dbus (Ubuntu)
--
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:
Restart networking crashes dbus and the desktop manager
To manage notifications about this
** Summary changed:
- Restart networking crashes (apparently) the desktop manager
+ Restart networking crashes dbus and the desktop manager
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1072518
Posted patch which is similar to skiantoz's but using comments instead
of code deletion. Invoking lvm2 to run is not necessary as lvm2 should
already be running since boot. The logic is that you would not have
installed a management app for the service if the service was not
already installed.
How does networking -stop differ from killing dbus? If for the sake of
argument I wanted to stop dbus without sigkilling it, how would I do that?
And how would I bring down all of my ifaces at the same time without
writing another script, which would bring them down sequentially at best?
This last
Hey, thanks for the tip, but we still need a proper solution. Why is dbus
brought down when networking stop is called?
On Apr 5, 2013 3:41 PM, Mathieu Trudel-Lapierre mathieu...@gmail.com
wrote:
If you're looking to restart network-manager, you'll want to do 'sudo
restart network-manager', not
/etc/init.d/networking stop is supposed to bring down your network
interfaces. It's not crashing your network connection, it's doing what it's
supposed to. The bug we're talking about is that it also brings down your
display manager, which it's not supposed to do. After you issue the stop
command,
Sorry, your response is invalid. At the mere mention of an unsupported
tool you disregarded this bug.
If you take notice of stgraber's steps, you'll notice in his
troubleshooting that he did not install webmin, thus confirming that
webmin is not the culprit.
I did not have this problem either
EDIT: I meant Cristian's steps not stgraber's
My apologies.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091399
Title:
/etc/init.d/networking stop causes system crashes
To manage notifications
19 matches
Mail list logo
