Bug#811497: Unclean shutdown after switch from sysvinit-core to systemd-sysv if systemd-shim is installed (and running)

[Michael Biebl]

Am 19.01.2016 um 15:10 schrieb Michael Biebl:
> Am 19.01.2016 um 15:01 schrieb Michael Biebl:
>> Package: systemd-sysv
>> Version: 228-4
>> Severity: important
>>
>> If sysvinit-core is the active PID 1 and systemd-shim is installed and
>> running, installing systemd-sysv will lead to an unclean shutdown and a
>> dirty file system on the next boot.
>>
>> Afaics, the problem is, that /sbin/{reboot,poweroff,shutdown} as shipped
>> by systemd-sysv does not talk to PID 1 via /run/initctl but uses D-Bus
>> if the org.freedesktop.systemd1 D-Bus name is taken, which is the case
>> if systemd-shim is installed.
> 
> Small correction here: systemd-shim does not need to be running prior to
> calling reboot. Merely being installed is sufficient, as systemd-shim is
> D-Bus activated, so will be started on demand.

Martin and Ansgar suggested on IRC, that we could/should add a
Conflicts: systemd-shim to systemd-sysv.

In general, that is probably the right thing to do anyway, but in this
particular case, we run into another issue: the systemd-shim process is
not stopped when the systemd-shim package is uninstalled (a bug on its
own). We could possibly fix that via a stable upload for systemd-shim.



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20160119/14bb26b4/attachment-0002.sig>