Yes, I do believe it's the same PA instance, I had not noticed it restarting (e.g. pavucontrol losing the connection) when testing around this bug.
Also, I'm not sure if it helps, but the module likes to spam a ton of
pulseaudio[11451]: E: [pulseaudio] module-snap-policy.c: AppArmor profile could not be retrieved.
pulseaudio[11451]: E: [pulseaudio] module-snap-policy.c: AppArmor profile could not be retrieved.
pulseaudio[11451]: E: [pulseaudio] module-snap-policy.c: AppArmor profile could not be retrieved.
pulseaudio[11451]: E: [pulseaudio] module-snap-policy.c: AppArmor profile could not be retrieved.
into the log even when *not* running as a snap. I don't know if this is related as I've found it to be harmless to the functionality of my programm when running outside snaps.
Yes, I do believe it's the same PA instance, I had not noticed it restarting (e.g. pavucontrol losing the connection) when testing around this bug.
Also, I'm not sure if it helps, but the module likes to spam a ton of
pulseaudio[ 11451]: E: [pulseaudio] module- snap-policy. c: AppArmor profile could not be retrieved. 11451]: E: [pulseaudio] module- snap-policy. c: AppArmor profile could not be retrieved. 11451]: E: [pulseaudio] module- snap-policy. c: AppArmor profile could not be retrieved. 11451]: E: [pulseaudio] module- snap-policy. c: AppArmor profile could not be retrieved.
pulseaudio[
pulseaudio[
pulseaudio[
into the log even when *not* running as a snap. I don't know if this is related as I've found it to be harmless to the functionality of my programm when running outside snaps.