newbie Bluetooth questions

[David]

I have never used Bluetooth device in Linux, until today.

Device ( a speaker ) paired, but would not connect.
( Disclaimer:    I have a 6 year old ASUS motherboard )

Here are some terminal displays:

[me@localhost ~]$ systemctl status bluetooth
● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled;
vendor>
     Active: active (running) since Wed 2020-07-08 08:53:29 CDT; 4h 28min
ago
       Docs: man:bluetoothd(8)
   Main PID: 756 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 18759)
     Memory: 2.7M
        CPU: 192ms
     CGroup: /system.slice/bluetooth.service
             └─756 /usr/libexec/bluetooth/bluetoothd

Jul 08 08:53:28 localhost.localdomain systemd[1]: Starting Bluetooth
service...
Jul 08 08:53:29 localhost.localdomain bluetoothd[756]: Bluetooth daemon 5.54
Jul 08 08:53:29 localhost.localdomain systemd[1]: Started Bluetooth service.
Jul 08 08:53:29 localhost.localdomain bluetoothd[756]: Starting SDP server
Jul 08 08:53:29 localhost.localdomain bluetoothd[756]: Bluetooth management
int>
Jul 08 08:53:29 localhost.localdomain bluetoothd[756]: *Failed to set mode*:
Bloc>
Jul 08 08:53:39 localhost.localdomain bluetoothd[756]: *Failed to set mode*:
Bloc>
Jul 08 13:06:01 localhost.localdomain bluetoothd[756]: Endpoint registered:
sen>
Jul 08 13:06:01 localhost.localdomain bluetoothd[756]: Endpoint registered:
sen>

[me@localhost ~]$ bluetoothctl
Agent registered

[bluetooth]# show
Controller E0:B9:A5:F3:04:9C (public)
Name: localhost.localdomain
Alias: localhost.localdomain
Class: 0x001c0104
Powered: yes
Discoverable: yes
DiscoverableTimeout: 0x00000000
Pairable: yes
UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
UUID: Audio Source              (0000110a-0000-1000-8000-00805f9b34fb)
UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
UUID: Headset AG                (00001112-0000-1000-8000-00805f9b34fb)
UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
UUID: Headset                   (00001108-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: OBEX File Transfer        (00001106-0000-1000-8000-00805f9b34fb)
UUID: Message Notification Se.. (00001133-0000-1000-8000-00805f9b34fb)
UUID: IrMC Sync                 (00001104-0000-1000-8000-00805f9b34fb)
UUID: Message Access Server     (00001132-0000-1000-8000-00805f9b34fb)
UUID: OBEX Object Push          (00001105-0000-1000-8000-00805f9b34fb)
UUID: Phonebook Access Server   (0000112f-0000-1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0536
Discovering: yes
Advertising Features:
ActiveInstances: 0x00
SupportedInstances: 0x05
SupportedIncludes: tx-power
SupportedIncludes: appearance
SupportedIncludes: local-name
[CHG] Device 7C:B4:7F:21:F0:D1 RSSI: -61
[CHG] Device 7C:B4:7F:21:F0:D1 RSSI: -63
[CHG] Device 7C:B4:7F:21:F0:D1 RSSI: -70

David Locklear

[Samuel Sieb]

On 7/8/20 11:28 AM, David wrote:
> I have never used Bluetooth device in Linux, until today.
>
> Device ( a speaker ) paired, but would not connect.

I don't remember which Desktop you're using.  How are you trying to 
connect it?  Where do you see it paired but not connected?
> ( Disclaimer:    I have a 6 year old ASUS motherboard )

That sounds like a desktop.  Does it have built-in bluetooth or are you 
using a usb bluetooth dongle?

[David]

> I will look in my BIOS to see if Bluetooth is enabled

[Tom Horsley]

On Wed, 8 Jul 2020 18:32:27 -0500
David wrote:
> > I will look in my BIOS to see if Bluetooth is enabled

Another factor: Older motherboards may not support bluetooth 4.0,
and new bluetooth devices often only talk 4.0 (because of power
considerations).

[David]

My motherboard ASUS P8Z77 allegedly is Bluetooth 4.0 compatible.   BIOS
says enabled.

Gnome 3.37.3 says "paired" but not connected.

Both my iPhone8 and Android cheap phone connected while wearing a
blind-fold on.
( Just being sarcastic ).

As I said, I have never used Bluetooth on Linux, and seldom ever used it.
  But I got
a fancy Bluetooth speaker for my birthday, and wanted to listen to some
groovy tunes.

By the way, my Rawhide update today seemed to go well ( rc4 of the kernel
and all the new
Gnome stuff ).

I guess next I will purchase a Bluetooth dongle ??

[Ed Greshko]

On 2020-07-09 10:53, David wrote:
> My motherboard ASUS P8Z77 allegedly is Bluetooth 4.0 compatible.   BIOS says enabled.
>
> Gnome 3.37.3 says "paired" but not connected.

When you run bluetoothctl from the command line what does

devices

show?

[David]

Thank you for the quick response

[me@localhost ~]$ bluetoothctl
Agent registered
[CHG] Controller E0:B9:A5:F3:04:9C Pairable: yes

[bluetooth]# devices
Device 7C:B4:7F:21:F0:D1 BSSK9065

[  Sidenote:  ****BSSK9065**** is the correct name of my bluetooth speaker ]

[bluetooth]# show
Controller E0:B9:A5:F3:04:9C (public)
Name: localhost.localdomain
Alias: localhost.localdomain
Class: 0x001c0104
Powered: yes
Discoverable: yes
DiscoverableTimeout: 0x00000000
Pairable: yes
UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
UUID: Audio Source              (0000110a-0000-1000-8000-00805f9b34fb)
UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
UUID: Headset AG                (00001112-0000-1000-8000-00805f9b34fb)
UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
UUID: Headset                   (00001108-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: OBEX File Transfer        (00001106-0000-1000-8000-00805f9b34fb)
UUID: Message Notification Se.. (00001133-0000-1000-8000-00805f9b34fb)
UUID: IrMC Sync                 (00001104-0000-1000-8000-00805f9b34fb)
UUID: Message Access Server     (00001132-0000-1000-8000-00805f9b34fb)
UUID: OBEX Object Push          (00001105-0000-1000-8000-00805f9b34fb)
UUID: Phonebook Access Server   (0000112f-0000-1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0536
Discovering: no
Advertising Features:
ActiveInstances: 0x00
SupportedInstances: 0x05
SupportedIncludes: tx-power
SupportedIncludes: appearance
SupportedIncludes: local-name
[bluetooth]#

On Wed, Jul 8, 2020 at 10:26 PM Ed Greshko  wrote:
> On 2020-07-09 10:53, David wrote:
> > My motherboard ASUS P8Z77 allegedly is Bluetooth 4.0 compatible.   BIOS
>
> says enabled.
> > Gnome 3.37.3 says "paired" but not connected.
>
> When you run bluetoothctl from the command line what does
>
> devices
>
> show?
>
> --
> The key to getting good answers is to ask good questions.
> _______________________________________________
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]

[Ed Greshko]

On 2020-07-09 11:48, David wrote:
> me@localhost ~]$ bluetoothctl
> Agent registered
> [CHG] Controller E0:B9:A5:F3:04:9C Pairable: yes
>
> [bluetooth]# devices
> Device 7C:B4:7F:21:F0:D1 BSSK9065

With the speaker powered on.  What do you get when you do

[bluetooth]# connect 7C:B4:7F:21:F0:D1

??

[David]

Attempting to connect to 7C:B4:7F:21:F0:D1
[CHG] Device 7C:B4:7F:21:F0:D1 Paired: yes
Failed to connect: org.bluez.Error.Failed

On Wed, Jul 8, 2020 at 10:53 PM Ed Greshko  wrote:
> On 2020-07-09 11:48, David wrote:
> > me@localhost ~]$ bluetoothctl
> > Agent registered
> > [CHG] Controller E0:B9:A5:F3:04:9C Pairable: yes
> >
> > [bluetooth]# devices
> > Device 7C:B4:7F:21:F0:D1 BSSK9065
>
> With the speaker powered on.  What do you get when you do
>
> [bluetooth]# connect 7C:B4:7F:21:F0:D1
>
> ??
>
> --
> The key to getting good answers is to ask good questions.
> _______________________________________________
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]

[Ed Greshko]

On 2020-07-09 12:01, David wrote:
> Attempting to connect to 7C:B4:7F:21:F0:D1
> [CHG] Device 7C:B4:7F:21:F0:D1 Paired: yes
> Failed to connect: org.bluez.Error.Failed

Are the packages pulseaudio-module-bluetooth and bluez installed?

[David]

sudo dnf install pulseaudio-module-bluetooth bluez
[sudo]:
Last metadata expiration check: 2:05:16 ago on Wed 08 Jul 2020 09:13:17 PM
CDT.
Package pulseaudio-module-bluetooth-13.99.1-4.fc33.x86_64 is already
installed.
Package bluez-5.54-2.fc33.x86_64 is already installed.
Dependencies resolved.
Nothing to do.
Complete!

[Ed Greshko]

On 2020-07-09 12:20, David wrote:
> sudo dnf install pulseaudio-module-bluetooth bluez
> [sudo]:
> Last metadata expiration check: 2:05:16 ago on Wed 08 Jul 2020 09:13:17 PM CDT.
> Package pulseaudio-module-bluetooth-13.99.1-4.fc33.x86_64 is already installed.
> Package bluez-5.54-2.fc33.x86_64 is already installed.
> Dependencies resolved.
> Nothing to do.
> Complete!

In one terminal session, issue the command

bluetoothctl power off

Then, in a second terminal session run

btmon

Back in the first terminal session, issue the comman

bluetoothctl power on
and then
bluetoothctl connect 7C:B4:7F:21:F0:D1

And show the results of btmon.

[Samuel Sieb]

On 7/8/20 7:53 PM, David wrote:
> Gnome 3.37.3 says "paired" but not connected.

Open a terminal window and run "sudo journalctl -fa".  Then click the 
connect switch for the device in the bluetooth settings.  See what log 
messages get generated for it.

[David]

$ sudo journalctl -fa
[sudo] password:
-- Logs begin at Tue 2020-04-07 15:46:50 CDT. --
Jul 08 23:01:57 localhost.localdomain systemd[1]: Starting Fingerprint
Authentication Daemon...
Jul 08 23:01:57 localhost.localdomain systemd[1]: Started Fingerprint
Authentication Daemon.
Jul 08 23:01:57 localhost.localdomain audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=fprintd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=?
addr=? terminal=? res=success'
Jul 08 23:02:02 localhost.localdomain audit[6161]: USER_AUTH pid=6161
uid=1000 auid=1000 ses=3
subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
msg='op=PAM:authentication grantors=pam_usertype,pam_localuser,pam_unix
acct="david" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0
res=success'
Jul 08 23:02:02 localhost.localdomain audit[6161]: USER_ACCT pid=6161
uid=1000 auid=1000 ses=3
subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
msg='op=PAM:accounting grantors=pam_unix,pam_localuser acct="david"
exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Jul 08 23:02:02 localhost.localdomain sudo[6161]:    david : TTY=pts/0 ;
PWD=/home/david ; USER=root ; COMMAND=/usr/bin/journalctl -fa
Jul 08 23:02:02 localhost.localdomain audit[6161]: USER_CMD pid=6161
uid=1000 auid=1000 ses=3
subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
msg='cwd="/home/david" cmd=6A6F75726E616C63746C202D6661 exe="/usr/bin/sudo"
terminal=pts/0 res=success'
Jul 08 23:02:02 localhost.localdomain audit[6161]: CRED_REFR pid=6161 uid=0
auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
msg='op=PAM:setcred grantors=pam_localuser,pam_unix acct="root"
exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0 res=success'
Jul 08 23:02:02 localhost.localdomain sudo[6161]: pam_unix(sudo:session):
session opened for user root(uid=0) by (uid=0)
Jul 08 23:02:02 localhost.localdomain audit[6161]: USER_START pid=6161
uid=0 auid=1000 ses=3
subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
msg='op=PAM:session_open
grantors=pam_keyinit,pam_limits,pam_keyinit,pam_limits,pam_systemd,pam_unix
acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/0
res=success'
Jul 08 23:02:18 localhost.localdomain gnome-shell[1621]: JS ERROR:
Exception in callback for signal: trigger: TypeError: pspec is null
                                                         _easeActorProperty
@resource:///org/gnome/shell/ui/environment.js:215:42
                                                         init/
Clutter.Actor.prototype.ease_property
@resource:///org/gnome/shell/ui/environment.js:280:9
                                                         _shadeBackgrounds
@resource:///org/gnome/shell/ui/overview.js:262:28
                                                         _animateVisible
@resource:///org/gnome/shell/ui/overview.js:590:14
                                                         show
@resource:///org/gnome/shell/ui/overview.js:567:14
                                                         toggle
@resource:///org/gnome/shell/ui/overview.js:690:18
                                                         _toggleOverview
@resource:///org/gnome/shell/ui/layout.js:1234:27
                                                         _emit
@resource:///org/gnome/gjs/modules/core/_signals.js:133:47
                                                         _trigger
@resource:///org/gnome/shell/ui/layout.js:1365:14
                                                         _onBarrierHit
@resource:///org/gnome/shell/ui/layout.js:1407:18
Jul 08 23:02:19 localhost.localdomain gnome-shell[1621]: JS ERROR:
TypeError: pspec is null
                                                         _easeActorProperty
@resource:///org/gnome/shell/ui/environment.js:215:42
                                                         init/
Clutter.Actor.prototype.ease_property
@resource:///org/gnome/shell/ui/environment.js:280:9
                                                         _unshadeBackgrounds
@resource:///org/gnome/shell/ui/overview.js:248:28
                                                         _animateNotVisible
@resource:///org/gnome/shell/ui/overview.js:654:14
                                                         hide
@resource:///org/gnome/shell/ui/overview.js:634:14
                                                         activateWindow
@resource:///org/gnome/shell/ui/main.js:672:14
                                                         _onCloneSelected
@resource:///org/gnome/shell/ui/workspace.js:1273:14
                                                         _activate
@resource:///org/gnome/shell/ui/windowPreview.js:655:14

_init/<@resource:///org/gnome/shell/ui/windowPreview.js:247:51
Jul 08 23:02:27 localhost.localdomain systemd[1]: fprintd.service:
Succeeded.
Jul 08 23:02:27 localhost.localdomain audit[1]: SERVICE_STOP pid=1 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=fprintd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=?
addr=? terminal=? res=success'

On Wed, Jul 8, 2020 at 10:49 PM Samuel Sieb  wrote:
> On 7/8/20 7:53 PM, David wrote:
> > Gnome 3.37.3 says "paired" but not connected.
>
> Open a terminal window and run "sudo journalctl -fa".  Then click the
> connect switch for the device in the bluetooth settings.  See what log
> messages get generated for it.
> _______________________________________________
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]

[Samuel Sieb]

On 7/8/20 9:03 PM, David wrote:
> $ sudo journalctl -fa

I don't see anything about bluetooth in there.  Don't copy everything. 
After you press the bluetooth device connect button, there should be 
some lines about bluetooth, pulseaudio, kernel input devices. That's the 
section I'm looking for.

However, I just tested it myself and there's actually very little (and 
possibly no) information until it connects.  So if it doesn't connect, 
there might be nothing.

I'm not sure what else to suggest other than to try removing the device 
and then pairing it again.  And make sure it's not paired to some other 
device first.

[Ed Greshko]

On 2020-07-09 12:23, Samuel Sieb wrote:
> I'm not sure what else to suggest other than to try removing the device and then pairing it again.  And make sure it's not paired to some other device first.

Or connected.

I had BT earphones that could be paired with multiple devices but only connected to one at a time.

[David]

For a nano-second Gnome Bluetooth Setting ( from top right corner ) says
connected, but then
disconnects and never reconnects.      The spinning thing goes on forever
like The Energizer Bunny,
searching for devices and list several unknown devices that are light grey
and can't be clicked on.

On Wed, Jul 8, 2020 at 11:41 PM Ed Greshko  wrote:
> On 2020-07-09 12:23, Samuel Sieb wrote:
> > I'm not sure what else to suggest other than to try removing the device
>
> and then pairing it again.  And make sure it's not paired to some other
> device first.
>
> Or connected.
>
> I had BT earphones that could be paired with multiple devices but only
> connected to one at a time.
>
> --
> The key to getting good answers is to ask good questions.
> _______________________________________________
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]