Am 08.01.2017 um 00:47 schrieb Gedalya: > On 01/07/2017 06:43 PM, Michael Biebl wrote: >>> As stated in the last few messages in this bug report, the problem appears exclusively when not using systemd as init. >>> At Yves-Alexis's request I confirmed the symptoms do not occur when booting with systemd as init. >>> >>> This is the n'th recurrence of, basically, the same problem, just the added issue with light-locker is new. >>> In previous times as well, things did work when using systemd as init. >> Since the reassign message did not include this information, this was >> not clear. >> >> Thanks for confirming this works with systemd as PID 1. >> So this seems to be a problem in the SysV - systemd shim layer, i.e. >> systemd-shim. >> Reassigning accordingly. >> >> Word of warning: systemd-shim is orphaned and currently has no >> maintainer. So my recommendation would be to stick with systemd-sysv. >> > > On the other hand, this did work well in all versions of systemd prior to 232-1, confirmed specifically with 231-10. > Would there be a way, and particularly due to systemd-shim being orphaned, to identify the problem and possibly fix it with systemd? You are asking the wrong audience here, you should ask people using sysvinit as PID 1. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
Attachment:
signature.asc
Description: OpenPGP digital signature