Yeah that is the mentioned workaround that we have identified before wrapped up nicely for consumption. Still - like many others - I'd want to understand the problem :-)
And BTW I wanted to mention a lot of thanks to everyone participating so far! It makes me feel proud of our user community to work together constructively until we find it. And another BTW we need to be careful as I think we might have at least one or two other cases here on the bug that might look like the same symptom but have different reasons. So if/once we apply that change some (with other root causes) might say "still not working for me" but those we'd then need to fork out into other bugs to track down their individual root causes. I have no sssd setup around but will ask someone for help on that. Thanks for this new opportunity to this. And even if the sssd approach fails, I think despite still not being able to recreate it there are by now enough people hit and fixed by adding the dgram rule that we have together come up. The libvirtd profile itself is after all meant to be very lenient (not the guests, but the host service). So by now it might be fair to at least propose that even IF I can't reproduce still. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890858 Title: AppArmor profile causes QEMU/KVM - Not Connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1890858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
