This bug was fixed in the package rsyslog - 8.2312.0-3ubuntu9.1
---------------
rsyslog (8.2312.0-3ubuntu9.1) noble; urgency=medium
* d/usr.sbin.rsyslog: add apparmor rule to allow reading systemd sessions
(LP: #2056768)
* d/usr.sbin.rsyslogd: add AppArmor rule to allow the imjournal module to
work (LP: #2073628)
* d/usr.sbin.rsyslogd: add AppArmor rule to allow access to disable_ipv6
inside /proc (LP: #2061726)
* d/t/logcheck: when checking the journal, only consider current boot
(LP: #2100765)
-- Andreas Hasenack <[email protected]> Tue, 11 Mar 2025 15:25:47
-0300
** Changed in: rsyslog (Ubuntu Noble)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100765
Title:
Consistent DEP8/s390x failure: boot notice unexpectedly in journalctl
logs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2100765/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
