Unfortunately with systemd-227 the behaviour hasn't been changed. Vladimir.
On 21/10/15 13:26, Vlad wrote: > Thanks for the explanation. I'll try 227 asap. > > Vladimir. > > On 20/10/15 12:19, Lennart Poettering wrote: >> On Tue, 20.10.15 08:21, Vlad (vo...@vovan.nl) wrote: >> >>> Hello, >>> >>> On my laptop the backlight service is stopped at boot instead of starting: >>> >>> # journalctl -a -b | grep backl >>> Oct 20 08:13:09 *** systemd[1]: Stopped Load/Save Screen Backlight >>> Brightness of backlight:intel_backlight. >>> Oct 20 08:13:09 *** systemd[1]: Removed slice >>> system-systemd\x2dbacklight.slice. >>> >>> However I can start/stop service manually and the backlight is properly >>> restored/saved in /var/lib/systemd/backlight/pci... >>> >>> I'd appreciate any ideas (running systemd-226). >> Most likely you have an rfkill device that appears and the disappears, >> possibly because a firmware rfkill device is replaced by a >> driver-level one. >> >> Either way, in 227 the code around this has changed quite a bit, the >> service is now a singleton and works quite differently. It's now >> started each time an rfkill event happens, and then exits after a few >> seconds. We precisely made this change to deal better with rfkill >> devices that appear only temporarily. >> >> Lennart >> > _______________________________________________ > systemd-devel mailing list > systemd-devel@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/systemd-devel _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
