linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael Ávila de Espíndola" <rafael@espindo.la>
To: linux-bluetooth@vger.kernel.org
Cc: luiz.dentz@gmail.com, "Rafael Ávila de Espíndola" <rafael@espindo.la>
Subject: [PATCH] Mention disabling SELinux in HACKING
Date: Tue, 12 May 2020 02:36:39 +0000	[thread overview]
Message-ID: <20200512023609.43163-1-rafael@espindo.la> (raw)

Running bluetoothd from the build directory I noticed that as soon as
a bluetooth audio device was connect, bluetoothd would be disconnected
from dbus and print

Disconnected from D-Bus. Exiting.

Luiz Augusto von Dentz suggested trying with SELinux disabled and that
solved the problem.

This patch just documents how to disable SELinux before running
bluetoothd from the build directory. I would love to say more about
why that is needed, but could not find anything on the audit log.
---
 HACKING | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/HACKING b/HACKING
index e10986fcb..29b136b34 100644
--- a/HACKING
+++ b/HACKING
@@ -76,6 +76,9 @@ automatically includes this option.
   Copy configuration file which specifies the required security policies
     # sudo cp ./src/bluetooth.conf /etc/dbus-1/system.d/
 
+  Disable SELinux
+    # sudo setenforce 0
+
   Run daemon in foreground with debugging
     # sudo ./src/bluetoothd -n -d -f ./src/main.conf
 
-- 
2.26.2



             reply	other threads:[~2020-05-12  2:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-12  2:36 Rafael Ávila de Espíndola [this message]
2020-05-19 15:58 ` [PATCH] Mention disabling SELinux in HACKING Rafael Avila de Espindola
2020-05-19 17:57   ` Luiz Augusto von Dentz

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=20200512023609.43163-1-rafael@espindo.la \
    --to=rafael@espindo.la \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    /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).