Return-Path: <cyrus@holtmann.org>
Message-ID: <1386857551.1982.43.camel@nuvo>
Subject: Re: mouse not found with bluez5 but was fine with bluez4
From: Bastien Nocera <hadess@hadess.net>
To: "Brian J. Murrell" <brian@interlinx.bc.ca>
Cc: Johan Hedberg <johan.hedberg@gmail.com>,
	linux-bluetooth@vger.kernel.org
Date: Thu, 12 Dec 2013 15:12:31 +0100
In-Reply-To: <1386856382.1982.42.camel@nuvo>
References: <1386680927.11483.6.camel@pc.interlinx.bc.ca>
	 <20131211092135.GA16525@x220.p-661hnu-f1>
	 <1386776083.31076.60.camel@bmurrell-mobl.amr.corp.intel.com>
	 <20131211192523.GA17953@x220.p-661hnu-f1>
	 <1386792806.3586.6.camel@bmurrell-mobl.amr.corp.intel.com>
	 <1386798596.1982.32.camel@nuvo>
	 <1386850542.3586.19.camel@bmurrell-mobl.amr.corp.intel.com>
	 <1386856382.1982.42.camel@nuvo>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Sender: linux-bluetooth-owner@vger.kernel.org
List-ID: <linux-bluetooth.vger.kernel.org>

On Thu, 2013-12-12 at 14:53 +0100, Bastien Nocera wrote:
<snip>
> There's plenty of SELinux warnings in there. Maybe you need to enable
> permissive mode, and/or file bugs about those.

Never mind, confusing with another headset issue I'm working on :/