I think neither rsyslog, nor cups, or sssd, are the correct packages for
this bug, but I agree that spreading out the investigation over two
different bugs is not good.
I'll mark https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2064088 as
a duplicate, and add cups and sssd tasks to this one for
Do you think we should mark #2064088 as a duplicate of this (or vice-
versa), if we're confident this is the same underlying issue?
There are some outstanding questions for me on that bug, but it might
make sense to focus our comments in one place going forward.
--
You received this bug notifica
Andreas and I spent some time this afternoon investigating this issue.
Here are our findings.
First, we noticed that the paths being reported by apparmor on dmesg
appear to be relative to /run. This is just an impression, though: I
believe that, for some reason, apparmor/systemd/something-else is
So far it's rsyslog, cups, and sssd (just confirmed via
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2064088).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/2064096
I've just found that the cups.service is also experiencing the same
behaviour. Again it has the service type 'notify'.
I suspect other services using this type will have the same problem.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is sub
Here's how to reproduce this in a LXD VM:
Download Ubuntu 24.04 Desktop image into ~/Downloads
Import the ISO
$ lxc storage volume import default ~/Downloads/ubuntu-24.04-desktop-amd64.iso
24.04-desktop --type=iso
Prepare a LXD VM
$ lxc init --empty --vm lxd-noble-fde -c limits.memory=6GiB -c l
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: rsyslog (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.n
Azure CVM images are impacted by the same issue. I see on #2064088 that
this is an tpm-backed FDE system. So I think it's the same problem here
if those desktop images use an systemd-based initramfs.
For now I suspect that the issue is due to systemd starting services and
setting up UNIX sockets (
8 matches
Mail list logo
