Github messages for voidlinux
 help / color / mirror / Atom feed
From: UsernameRandomlyGenerated <UsernameRandomlyGenerated@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Pulseaudio, apparmor and bluetooth audio
Date: Tue, 01 Feb 2022 16:05:21 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35344@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1151 bytes --]

New issue by UsernameRandomlyGenerated on void-packages repository

https://github.com/void-linux/void-packages/issues/35344

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System

* xuname:  
Void 5.15.17_1 x86_64-musl AuthenticAMD uptodate rFF
* package:  
pulseaudio-15.0_3
apparmor-3.0.3_2
bluez-5.63_1

### Expected behavior
Bluetooth headphones working.
### Actual behavior
You can connect bluetooth speakers/headphones but the default mode is OFF and trying to toggle A2DP instantly reverts to off.
### Steps to reproduce the behavior
1. Use pulseaudio and install&enable apparmor
2. Connect bluetooth speakers or headset
3. Check desktop environment sound settings

That's what I get in dmesg from apparmor (repeated a couple times):
'[   81.703876] audit: type=1400 audit(1643727351.998:80): apparmor="DENIED" operation="sendmsg" profile="pulseaudio" pid=1759 comm="bluetooth" family="bluetooth" sock_type="seqpacket" protocol=0 requested_mask="send" denied_mask="send"'


             reply	other threads:[~2022-02-01 15:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-01 15:05 UsernameRandomlyGenerated [this message]
2022-06-23  2:15 ` github-actions
2022-07-08  2:14 ` [ISSUE] [CLOSED] " github-actions

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35344@inbox.vuxu.org \
    --to=usernamerandomlygenerated@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).