as Eoan will be EOL in weeks, marking this wontfix.
** Changed in: systemd (Ubuntu Eoan)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Changed in: systemd (Ubuntu Eoan)
Assignee: Dan Streetman (ddstreet) => (unassigned)
** Changed in: systemd (Ubuntu Eoan)
Status: In Progress => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
That's interesting. With secure boot and lockdown in place there is no
bpf, and without bpf systemd services' acls dont work. Not critical but
essentially totally broken :D
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
>these messages actually come from the kernel, I believe they are
expected (maybe only in secure boot >mode, I haven't looked into the new
'lockdown' stuff yet). The lack of 'kernel_lockdown' manpage >appears to
be already reported in bug 1767971.
This PC is indeed using secure boot. Here are the
** Changed in: systemd
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1851056
Title:
"Proceeding WITHOUT firewalling in effect!"
** Also affects: systemd (Ubuntu Eoan)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: In Progress => Fix Released
** Bug watch added: github.com/systemd/systemd/issues #12673
https://github.com/systemd/systemd/issues/12673
** Also affects: systemd
> Hmm, that probably needs a further look...can you open a new bug for
that, so we can use this one only to fix the scary systemd 'WITHOUT
firewalling' log?
actually, beofre you open a new bug, let me look into the upstream
backport a bit more first.
--
You received this bug notification
> [ 1.904409] Lockdown: systemd: /dev/mem,kmem,port is restricted; see man
> kernel_lockdown.7
> [ 1.907029] Lockdown: systemd: BPF is restricted; see man kernel_lockdown.7
these messages actually come from the kernel, I believe they are
expected (maybe only in secure boot mode, I haven't looked
** Changed in: systemd (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1851056
Title:
"Proceeding WITHOUT firewalling in
+ Sorry, missed a few lines that may be relevant in that updated log...
It directly continues:
[1.991595] EXT4-fs (sdb2): re-mounted. Opts: errors=remount-ro
[1.993146] bpfilter: Loaded bpfilter_umh pid 418
#Nothing that looks out of place after that
Partition setup: sdb1 is an EFI
Just tested the systemd version from your PPA...
There are some changes:
[1.883017] systemd[1]: systemd 242 running in system mode. (+PAM +AUDIT
+SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS
+ACL +XZ +LZ4>
[1.901801] systemd[1]: Detected architecture
can you test with the systemd from this ppa to see if it fixes the warning logs:
https://launchpad.net/~ddstreet/+archive/ubuntu/systemd
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
12 matches
Mail list logo
