Package: dbus
Version: 1.10.6-1
Followup-For: Bug #805449
So while I was restarting the system for another dbus update, I actually
changed my mind. This should be of critical priority because of the way we're
using it. A systemd-based system becomes essentially un-usable after a dbus
restart.
It
We've already had some concerns about that issue at the local institute...
Am 18. November 2015 12:10:24 MEZ, schrieb Yuri D'Elia :
>I realize debian has nothing to do with this, but still, as long as you
>don't close the bug, I'm fine with wontfix...
I don't think this should be marked wontfixed
On 18/11/15 11:23, Simon McVittie wrote:
>> We can re-exec init, but not dbus?
>
> Yes. Handing off IPC connections across a re-exec is a feature of
> significant complexity, which will break the system if done wrong; it
> would require support for serializing and deserializing dbus-daemon's
> ent
Control: severity 805449 wishlist
Control: tags 805449 + upstream wontfix
On 18/11/15 09:45, Yuri D'Elia wrote:
> A reboot is required to replace the running dbus-daemon.
...
> We can re-exec init, but not dbus?
Yes. Handing off IPC connections across a re-exec is a feature of
significant complex
Package: dbus
Version: 1.10.4-1
Severity: normal
Setting up dbus (1.10.4-1) ...
A reboot is required to replace the running dbus-daemon.
Somehow I have a big problem with that.
We can re-exec init, but not dbus?
5 matches
Mail list logo
