Ok, I was able to reproduce this in a VM setup (following https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2064096/comments/4). And if the apparmor profile is removed for sssd, even though it was in complain mode (not enforce), then sssd starts just fine.
To clarify, this is happening when installing Noble desktop with the TPM+FDE option. It doesn't look like it's an sssd bug. This is also happening with cups and rsyslog. Where exactly the problem is we don't know yet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064088 Title: sssd service fails to start in noble numbat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2064088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
