Is the solution described in comment #143 and comment #147 really the
correct one?
In short, that means dbus always stops on the event deconfiguring-
networking, which is emitted when /etc/init.d/networking stop is
called.
In other words, whenever /etc/init.d/networking stop is called, dbus gets
Is the solution described in comment #143 and comment #147 really the
correct one?
In short, that means dbus always stops on the event deconfiguring-
networking, which is emitted when /etc/init.d/networking stop is
called.
In other words, whenever /etc/init.d/networking stop is called, dbus gets
I'm also having the same problem.
I was able to track the cause of this problem and find a workaround that
seems to work.
1 - Cause:
The event deconfiguring-networking is fired whenever
/etc/init.d/networking stop is called.
If you read the source of /etc/init.d/networking you can see this
I was also having this issue and I patched it myself. I posted the patch
at http://forum.xchat.org/viewtopic.php?f=5t=5797
--
xchat disconnect then reconnect loses channel info
https://bugs.launchpad.net/bugs/215078
You received this bug notification because you are a member of Ubuntu
Bugs,
