Bug#967917: Fix for unit file

Also seeing this problem. The issue can be fixed by editing the unit file. In the [Service] section, edit the ExecStart line so that it reads: ExecStart=/bin/true You'll then need to run: sudo systemctl daemon-reload sudo systemctl restart blk-availability.service to reload the unit file.

Bug#967917: Unresponsive system

I use GNU / Linux Debian testing 64-bit fully updated [kernel 5.3.0-3-amd64] and the past week or so, my entire system has become unresponsive at random times. 5 minutes ago, while I was listening to music, my system stop playing the track and became fully unresponsive. I switched to a

Bug#967917: olgas.newt.com 2020-08-10 19:02 -0700 System Events

I'm seeing these frequent, annoying messages on bullseye as well. Should we be concerned? Or should we report an issue with logcheck to ignore them? logcheck system account wrote: > System Events > =-=-=-=-=-=-= > Aug 10 18:31:50 olgas systemd[1]: blk-availability.service: Cannot add >

Bug#967917:

Seeing this problem as well with the latest LVM package update on unstable. Setting up dmeventd (2:1.02.171-2) ... dm-event.service is a disabled or a static unit not running, not starting it. Setting up systemd-sysv (246-2) ... Setting up grub2-common (2.04-9) ... Setting up libnss-systemd:amd64

Bug#967917: blk-availability.service: Cannot add dependency job, ignoring: Unit blk-availability.service has a bad unit file setting.

Package: lvm2 Version: 2.03.09-2 Severity: normal I'm seeing these errors messages in my logs every hour: Aug 4 14:30:33 systemd[1]: blk-availability.service: Cannot add dependency job, ignoring: Unit blk-availability has a bad unit file setting. Aug 4 14:34:28 systemd[1]: