On Tue, Jul 26, 2016 at 01:33:00AM -0400, Jon LaBadie wrote:
On Mon, Jul 25, 2016 at 11:57:24PM +0100, Patrick O'Callaghan
wrote:
> On Tue, 2016-07-26 at 05:55 +0800, Ed Greshko wrote:
> >
> > On 07/26/16 02:49, Roger Wells wrote:
> > >
> > > Something changed (although not fatally):
> > > I use Bluetooth speakers quite often.
> > > Back in F22 or so after pairing the device merely turning it on caused
> > > Fedora to connect to it.
> > > Several months ago, now on F23, (not sure when this problem appeared)
> > > that changed and after turning the speaker on, I have to go into
> > > Bluetooth Settings where the device appears as "Disconnected",
select it
> > > and activate the "Connection" switch several times and it will
> > > eventually connect and be available for selection in the "Sound
> > > Settings" after which it works fine.
> > > Is there a path back?
> > >
> > > The setup is up to date Fedora 23 using Gnome 3.18.1-1.fc23.x86_64
> > > TIA,
> >
> > I use F24, a Bluetooth headset, and KDE. The GUI may be different but I think
gnome
> > should have similar settings.
> >
> > On my settings for the headset I have "trusted" checked. Then there
is another "tab"
> > called "Advanced Settings". There is a drop down box for
"Accept Automatically" and I
> > have "Trusted Devices" selected.
> >
> > When I power on my headset it is connected automatically.
>
> Interesting. A recent thread (around July 8) concerned similar problems
> with BT mice. I wonder if this is the solution. I confess I'd never
> looked at the Advanced Settings when trying to solve this.
>
I was the OP on that thread. I saw the trusted setting and am fairly
sure I tried it with no improvement.
I stopped using the bt mouse. Even turned off bt in the bios.
Will revisit the issue with the trusted setting and report back
It seems "trust" is the key. I had difficulty turning it on for
my mouse device. In blueman-manager, there are menu items and
a separate icon button to turn on trust. These did not complain
but didn't set the mouse as a trusted device either.
I went into bluetoothctl, found the device id, and used the
trust <dev_id> command. It reported setting "trust succeeded".
Sure enough, when I went back into the gui blueman-manager,
it was showing the trust icon for my mouse.
Now rebooting with the mouse on, or starting the mouse after
booting, it comes right up.
Seems like blueman-manager needs a fix to get trust working.
Jon
--
Jon H. LaBadie jonfu(a)jgcomp.com