Hi,
yes, I am using GRUB with Secure Boot enabled. SB does apparently make
it so the variable does not get cached.
So imo, the problem is that the command only even tries to read the
variable from the cache and not from `/sys`.
I will file it upstream. Thanks for helping!
--
Regards,
Thomas
`/sys/firmware/efi/efivars/`. However this directory does not exist on
my system, even after running the command to set the `SystemdOptions`
var.
--
Cheers,
Thomas Mühlbacher
it introduces any kind of regression,
actually.
--
Cheers,
Thomas Mühlbacher
Hi,
I found this bugreport after already opening one with resolvconf and
I just thought I'd link you to the one I made:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968015
Cheers,
Thomas Mühlbacher
setup again with `PathExists=` dropped from
`resolvconf-pull-resolved.path` and it stops the errors from occurring,
however I did not verify that this way the service still does what it's
supposed to.
Cheers,
Thomas Mühlbacher
onf` but it's in the
`Recommends` of a lot of other packages so it will be installed on many
systems that might use `resolved`, which is already a part of the
`systemd` package.
Cheers,
Thomas Mühlbacher
6 matches
Mail list logo
