topic title: Bluetooth failing to pair (org.bluez.Error.AuthenticationRejected)
Posts: 65
THX1138
Joined: 14 Sep 2017
#1
I would like to pair a bluetooth device on my antiX installation. I can't find relevant information and tried to follow this general Debian instruction (
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://wiki.debian.org/BluetoothUser"
linktext was:"https://wiki.debian.org/BluetoothUser"
====================================
) but am stuck because it gives instructions for GNOME and KDE, telling me to install the bluetooth GUI. I think that antiX already has all the bluetooth stuff installed but I don't know how to invoke the GUI to get started.

I have a Wyse V90L thin client and a Belkin F8T009 Bluetooth adapter and this Bluetooth remote control 
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://www.amazon.co.uk/Ckeyin-Bluetooth-Wireless-Control-Smartphone/dp/B00VV4TRAS/ref=sr_1_12?ie=UTF8&qid=1505500144&sr=8-12&keywords=bluetooth+remote"
linktext was:"https://www.amazon.co.uk/Ckeyin-Bluetoo ... B00VV4TRAS"
====================================


Edit: I tried some stuff from further down the page and there were some hits among the misses. I feel I got pretty close but I still fall at the last hurdle.

Code: Select all

sean@teleprompter:~
$ bluetoothctl help
[NEW] Controller 00:0A:3A:68:AD:A8 BlueZ 5.23 [default]
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# devices
[bluetooth]# scan on
Discovery started
[CHG] Controller 00:0A:3A:68:AD:A8 Discovering: yes
[NEW] Device AA:00:00:00:1E:D9 Bluetooth Remote Shutter
[NEW] Device 00:01:95:24:82:C7 00-01-95-24-82-C7
[CHG] Device 00:01:95:24:82:C7 LegacyPairing: no
[CHG] Device 00:01:95:24:82:C7 RSSI: 127
[CHG] Device 00:01:95:24:82:C7 Name: seantron2000
[CHG] Device 00:01:95:24:82:C7 Alias: seantron2000
[CHG] Device 00:01:95:24:82:C7 LegacyPairing: yes
[CHG] Device 00:01:95:24:82:C7 RSSI is nil
[bluetooth]# pair AA:00:00:00:1E:D9
Attempting to pair with AA:00:00:00:1E:D9
[CHG] Device AA:00:00:00:1E:D9 Connected: yes
Failed to pair: org.bluez.Error.AuthenticationRejected
[CHG] Device AA:00:00:00:1E:D9 Connected: no
[bluetooth]# trust AA:00:00:00:1E:D9
[CHG] Device AA:00:00:00:1E:D9 Trusted: yes
Changing AA:00:00:00:1E:D9 trust succeeded
[bluetooth]# pair AA:00:00:00:1E:D9
Attempting to pair with AA:00:00:00:1E:D9
[CHG] Device AA:00:00:00:1E:D9 Connected: yes
Failed to pair: org.bluez.Error.AuthenticationRejected
[CHG] Device AA:00:00:00:1E:D9 Connected: no
[bluetooth]#
My device doesn't need a PIN to pair, FYI. It does not come with a PIN or a means to enter a PIN. Thanks for any advice.
Last edited by THX1138 on 18 Sep 2017, 08:33, edited 1 time in total.
Posts: 4,164
rokytnji
Joined: 20 Feb 2009
#2
I kinda ran into errors like you show at the end of your readout. I ended up going with PulseAudio instead of ALSA sound system on my laptop to fix my pairing issue. Different hardware though and I cannot explain real well but , I referred to this page to get my wireless proprietary bluetooth external usb speaker going .



========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://www.linuxliteos.com/forums/tutorials-27/%28solved%29-enabling-full-bluetooth-support-in-linux-lite/"
linktext was:"https://www.linuxliteos.com/forums/tuto ... inux-lite/"
====================================


Might help. Might not. Like I said. Mine was different hardware.
Posts: 4,164
rokytnji
Joined: 20 Feb 2009
#3
Also. Installing PulseAudio requires some editing of /etc/preferences.d contents in folder. You need to comment out everything in systemd00 < The line entries >\

Comment out means means opening file manager as root. First. Make a backup

Code: Select all

sudo cp /etc/preferences.d/systemd00 /etc/preferences.d/systemd00.backup
Now you can edit systemd00 and have the original .

After commenting out lines in text editor ( # tag in front of each line and saved the file in root rox filer and root text editor)

Close everything and saved the edited file 1st. Then open a terminal do

Code: Select all

sudo apt-get update
Let finish. Then you can install pulseaudio using synaptic manager. After a successful install. Repeat your steps to get into /etc.preferences.d and undo the comments. You can do this 2 ways. You can delete systemd00 file and 1st. Then rename systemd.00.old to systemd00. Close and do

Code: Select all

sudo apt-get update
To bring your install back to stock.

The other way to do this. Rename systemd00 to systemd00.old . Then,  rename systemd00.backup  to systemd00.

Then make a systemd00.old.readme

Write in it. Then save it. This way you know what you did when time passes by and you forget.,
systemd.old is for using packages that require systemd dependencies to install.  to enable. rename to systemd00. Then run"sudo apt-get update". Then install required application you wish to install. to disable. Use your original systemd00 file you saved as backup. Renameing it to systemd00 from whatever you named it to stay in place. Then"sudo apt-get update" again to keep my install stock.
I am not sure a systemd free version of pulseaudio is available in the meta package installer < You can poke around and look > . The packages in the meta package installer are developer made packages that are custom packages for us since we are a systemd free distro.  Means basically. The systemd stuff has been left out of items in the meta package installer.
Posts: 65
THX1138
Joined: 14 Sep 2017
#4
Thanks very much for your response but I can't see PulseAudio helping since it totally all about sound whereas I'm not even going to have speakers attached to my system (it's going to be a teleprompter)?

I have put some logs here which was asked for in a thread I posted in the Debian forum (that thread got moved to offtopic and stopped receiving replies). Are there any others I should check? I was able to pair my Bluetooth headset although there is no sound from it (as I said though, I don't need this to work; only the Bluetooth remote control).

Code: Select all

sean@teleprompter:/var/log
$ sudo grep -i blue syslog
Sep 15 14:16:19 teleprompter kernel: [    3.570193] usb 2-2: Product: Belkin Bluetooth Device
Sep 15 14:16:19 teleprompter kernel: [    7.940657] Bluetooth: Core ver 2.21
Sep 15 14:16:19 teleprompter kernel: [    7.940739] Bluetooth: HCI device and connection manager initialized
Sep 15 14:16:19 teleprompter kernel: [    7.940758] Bluetooth: HCI socket layer initialized
Sep 15 14:16:19 teleprompter kernel: [    7.940771] Bluetooth: L2CAP socket layer initialized
Sep 15 14:16:19 teleprompter kernel: [    7.940821] Bluetooth: SCO socket layer initialized
Sep 15 14:16:21 teleprompter bluetoothd[2053]: Bluetooth daemon 5.23
Sep 15 14:16:21 teleprompter bluetoothd[2053]: Starting SDP server
Sep 15 14:16:21 teleprompter kernel: [   40.380678] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Sep 15 14:16:21 teleprompter kernel: [   40.380697] Bluetooth: BNEP filters: protocol multicast
Sep 15 14:16:21 teleprompter kernel: [   40.380724] Bluetooth: BNEP socket layer initialized
Sep 15 14:16:21 teleprompter bluetoothd[2053]: Bluetooth management interface 1.10 initialized
Sep 15 14:16:21 teleprompter bluetoothd[2053]: Sap driver initialization failed.
Sep 15 14:16:21 teleprompter bluetoothd[2053]: sap-server: Operation not permitted (1)
Sep 15 19:04:28 teleprompter bluetoothd[2053]: Sap driver initialization failed.
Sep 15 19:04:28 teleprompter bluetoothd[2053]: sap-server: Operation not permitted (1)
Sep 15 19:53:21 teleprompter bluetoothd[2053]: Sap driver initialization failed.
Sep 15 19:53:21 teleprompter bluetoothd[2053]: sap-server: Operation not permitted (1)
Sep 15 19:59:32 teleprompter kernel: [ 2426.316110] Bluetooth: RFCOMM TTY layer initialized
Sep 15 19:59:32 teleprompter kernel: [ 2426.316151] Bluetooth: RFCOMM socket layer initialized
Sep 15 19:59:32 teleprompter kernel: [ 2426.316186] Bluetooth: RFCOMM ver 1.11
Sep 15 20:02:22 teleprompter bluetoothd[2053]: No agent available for request type 4
Sep 15 20:02:22 teleprompter bluetoothd[2053]: device_notify_pin: Operation not permitted
Sep 15 20:02:52 teleprompter bluetoothd[2053]: No agent available for request type 4
Sep 15 20:02:52 teleprompter bluetoothd[2053]: device_notify_pin: Operation not permitted

Code: Select all

sean@teleprompter:/var/log
$ sudo grep -i blue dmesg|more
[    3.570193] usb 2-2: Product: Belkin Bluetooth Device
[    7.940657] Bluetooth: Core ver 2.21
[    7.940739] Bluetooth: HCI device and connection manager initialized
[    7.940758] Bluetooth: HCI socket layer initialized
[    7.940771] Bluetooth: L2CAP socket layer initialized
[    7.940821] Bluetooth: SCO socket layer initialized
sean@teleprompter:/var/log

Code: Select all

sean@teleprompter:/var/log
$ sudo grep -i blue daemon.log
Sep 15 14:16:21 teleprompter bluetoothd[2053]: Bluetooth daemon 5.23
Sep 15 14:16:21 teleprompter bluetoothd[2053]: Starting SDP server
Sep 15 14:16:21 teleprompter bluetoothd[2053]: Bluetooth management interface 1.10 initialized
Sep 15 14:16:21 teleprompter bluetoothd[2053]: Sap driver initialization failed.
Sep 15 14:16:21 teleprompter bluetoothd[2053]: sap-server: Operation not permitted (1)
Sep 15 19:04:28 teleprompter bluetoothd[2053]: Sap driver initialization failed.
Sep 15 19:04:28 teleprompter bluetoothd[2053]: sap-server: Operation not permitted (1)
Sep 15 19:53:21 teleprompter bluetoothd[2053]: Sap driver initialization failed.
Sep 15 19:53:21 teleprompter bluetoothd[2053]: sap-server: Operation not permitted (1)
Sep 15 20:02:22 teleprompter bluetoothd[2053]: No agent available for request type 4
Sep 15 20:02:22 teleprompter bluetoothd[2053]: device_notify_pin: Operation not permitted
Sep 15 20:02:52 teleprompter bluetoothd[2053]: No agent available for request type 4
Sep 15 20:02:52 teleprompter bluetoothd[2053]: device_notify_pin: Operation not permitted
Sep 16 01:15:10 teleprompter bluetoothd[2053]: Sap driver initialization failed.
Sep 16 01:15:10 teleprompter bluetoothd[2053]: sap-server: Operation not permitted (1)
Sep 17 21:39:36 teleprompter bluetoothd[2053]: Sap driver initialization failed.
Sep 17 21:39:36 teleprompter bluetoothd[2053]: sap-server: Operation not permitted (1)
sean@teleprompter:/var/log
Posts: 65
THX1138
Joined: 14 Sep 2017
#5
After much ado, it turns out that the Bluetooth adapter I was using was not able to do pairing without a PIN. I didn't realise that was a possibility.