Bug#846661: Processed: light-locker: screen remains black after unlock
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? signature.asc Description: OpenPGP digital signature
Bug#846661: Processed: light-locker: screen remains black after unlock
On 01/07/2017 06:47 PM, Gedalya wrote: > On the other hand, this did work well in all versions of systemd prior to > 232-1 Misspoke: it came and went several times.
Bug#846661: Processed: light-locker: screen remains black after unlock
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? It should go without saying that people who are avoiding systemd (well, trying hard to avoid it, but not being allowed to), are more than aware of systemd's existence, and are consciously choosing to avoid it.
Bug#846661: Processed: light-locker: screen remains black after unlock
Control: reassign -1 systemd-shim Am 08.01.2017 um 00:22 schrieb Gedalya: > On 01/07/2017 06:18 PM, Michael Biebl wrote: >> Control: tags -1 + moreinfo >> >> Can you reproduce the reproduce the problem with systemd as PID 1? >> >> loginctl unlock-session works fine here (using systemd-sysv). >> >> Michael > > 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. Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#846661: Processed: light-locker: screen remains black after unlock
On 01/07/2017 06:18 PM, Michael Biebl wrote: > Control: tags -1 + moreinfo > > Can you reproduce the reproduce the problem with systemd as PID 1? > > loginctl unlock-session works fine here (using systemd-sysv). > > Michael 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. Thanks, Gedalya
Bug#846661: Processed: light-locker: screen remains black after unlock
Control: tags -1 + moreinfo Can you reproduce the reproduce the problem with systemd as PID 1? loginctl unlock-session works fine here (using systemd-sysv). Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
