apparmor.d Wireplumber breaks on reboot

Enforcing the wireplumber profile causes only the dummy driver to be mapped on reboot. aa-log has no logs for some reason and journalctl only shows this: wireplumber[5151]: default: Failed to get percentage from UPower: org.freedesktop.DBus.Error.NameHasNoOwner

I haven't tested with other pipewire related profiles so this could affect them as well.

Jun 20 '24 22:06 Stoppedpuma

This seems unrelated to apparmor: the profile already has access to org.freedesktop.UPower and this is not enforced on non Ubuntu distribution anyway.

Jun 20 '24 22:06 roddhjav

Setting the profile in complain mode fixes this, doesn't that make this an issue related to apparmor.d?

Jun 20 '24 22:06 Stoppedpuma

This seems to just happen randomly with some profile in the make enforce profiles. No idea which ones as this seemed to happen randomly even when setting all pipewire related profiles and wireplumber set to complain, it just makes it possible to work correctly after a reboot. When I'm using my own list of enforced profiles I can't seem to reproduce this. Any ideas on where to go from here for debugging this? No logs are appearing anywhere besides the one I posted above.

Jun 21 '24 08:06 Stoppedpuma

Do you get any log from aa-log -s (even unrelated to wireplumber)?

Jun 21 '24 12:06 roddhjav

No

Jun 21 '24 14:06 Stoppedpuma

It's also probably worth mentioning that I managed to get audio to work somehow by switching to TTY-2 and playing an audio file while using the make enforce profiles. I only managed to get this to work once but I also haven't tried it more than three or so times.

Jun 21 '24 14:06 Stoppedpuma

Hum, can you tell me more about you setup? Distribution, DE, how you enabled wireplumber?

Jul 04 '24 20:07 roddhjav

Arch Linux, Hyprland, Wireplumber starts through systemd service.

Jul 05 '24 01:07 Stoppedpuma

I have never tested Hyprland, so... I don't know, and I won't be able to test it anytime soon.

I am surprised that Hyprland even start with apparmor.d. Especially when aa-log/aa-log -s does not report anything.

Jul 06 '24 20:07 roddhjav

Turns out the profile causing this issue is systemd-logind, nothing to do with pipewire or wireplumber profiles.

Jul 09 '24 06:07 Stoppedpuma

Can you give me more: why do you think it is systemd-logind? any log?

Jul 09 '24 11:07 roddhjav

Still no logs unfortunately , I figured this out by setting every profile to enforce. Setting systemd-logind to complain fixes this.

Jul 09 '24 15:07 Stoppedpuma

I'm also on Hyprland/Arch. I'd like to add that audio does work for me with systemd-logind on enforce, even though I also have the same error.

Jul 10 '24 17:07 odomingao

As it does not seems to be related to apparmor I am closing the issue.

Sep 17 '24 11:09 roddhjav