[SOLVED]bluetooth error - sap driver initialization failed

Kotrfa · 2014-11-11 08:52:47

Hello,

I have problem with bluetooth (since I installed Arch 4 years ago ). I've noticed that there are two errors (one is probably just consequence of the first). Nothing else except this is in journalctl and the same message I get when i manually restart bluetoothd through systemctl. Here is an output of status:

● bluetooth.service - Bluetooth service
   Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled)
   Active: active (running) since Tue 2014-11-11 09:41:40 CET; 2s ago
     Docs: man:bluetoothd(8)
 Main PID: 1495 (bluetoothd)
   Status: "Running"
   CGroup: /system.slice/bluetooth.service
           └─1495 /usr/lib/bluetooth/bluetoothd

Nov 11 09:41:40 530uarch bluetoothd[1495]: Bluetooth daemon 5.24
Nov 11 09:41:40 530uarch bluetoothd[1495]: Starting SDP server
Nov 11 09:41:40 530uarch bluetoothd[1495]: Bluetooth management interface 1.7 initialized
Nov 11 09:41:40 530uarch bluetoothd[1495]: Sap driver initialization failed.
Nov 11 09:41:40 530uarch bluetoothd[1495]: sap-server: Operation not permitted (1)
Nov 11 09:41:40 530uarch bluetoothd[1495]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSource
Nov 11 09:41:40 530uarch bluetoothd[1495]: Endpoint registered: sender=:1.10 path=/MediaEndpoint/A2DPSink

I've found some info here but it's KDE-desktop related.

My /etc/bluetooth/main.conf is in it's default and active lines are:

[General]
# Default adaper name
# %h - substituted for hostname
# %d - substituted for adapter id
Name = %h-%d

# Default device class. Only the major and minor device class bits are
# considered.
Class = 0x000100

# How long to stay in discoverable mode before going back to non-discoverable
# The value is in seconds. Default is 180, i.e. 3 minutes.
# 0 = disable timer, i.e. stay discoverable forever
DiscoverableTimeout = 0

# How long to stay in pairable mode before going back to non-discoverable
# The value is in seconds. Default is 0.
# 0 = disable timer, i.e. stay pairable forever
PairableTimeout = 0

# Automatic connection for bonded devices driven by platform/user events.
# If a platform plugin uses this mechanism, automatic connections will be
# enabled during the interval defined below. Initially, this feature
# intends to be used to establish connections to ATT channels.
AutoConnectTimeout = 60

# What value should be assumed for the adapter Powered property when
# SetProperty(Powered, ...) hasn't been called yet. Defaults to true
InitiallyPowered = true

# Do reverse service discovery for previously unknown devices that connect to
# us. This option is really only needed for qualification since the BITE tester
# doesn't like us doing reverse SDP for some test cases (though there could in
# theory be other useful purposes for this too). Defaults to true.
ReverseServiceDiscovery = true

# Enable name resolving after inquiry. Set it to 'false' if you don't need
# remote devices name and want shorter discovery cycle. Defaults to 'true'.
NameResolving = true

# Enable runtime persistency of debug link keys. Default is false which
# makes debug link keys valid only for the duration of the connection
# that they were created for.
DebugKeys = false

Anyway - when I want to connect my keyboard, I have to go to bluetoothctl, connect, disconnect and then again connect - then it's working OK. During that I get this errors:

Nov 11 09:53:40 530uarch bluetoothd[1495]: Can't get HIDP connection info

The keyboard also gets disconnected after cca 5 minutes of inactivity and bluetooth daemon use 100% of one core for no reason. When I type something on keyboard, it gets back to normal. And the best thing? When I hit Caps Lock on my BT keyboard, it stops working and disconnect from laptop. I have to disconnect it first in bluetoothctl and connect it again!

I guess this should be first step in making it work.

My friend with other laptop and other keyboard has exactly same problems. Thanks to lack of documentation for Bluez it's hard to find out what's going on. Really - this is one of the things that pisses me off the most in Linux.

Last edited by Kotrfa (2014-11-13 08:03:51)

Kotrfa · 2014-11-13 08:03:24

Ok, solved by installing bluez4 from AUR and then use commands which I've found on wiki for BT keyboard here. And then added this to my autostarted applications:

if [[ `rfkill list bluetooth | grep Soft|awk '{print $3}i'` == 'no' ]]; then bluez-test-input connect 20:73:**:55:**:88; fi

Last edited by Kotrfa (2014-11-13 08:03:38)

scot · 2017-04-22 20:01:04

I've only just installed debian an hour ago, so am asking some obvious noob questions. I'll prob have no choice but t figure it out before you see this, but if you do have just a minute to help the bluetoothed clueless who have the identical problem:

1. what does it mean to install a package from AUR? I s that a repo one needs to add, or what? if you've no time to explain, just the commands to type would help a lot.

2. Where do I add that line ( "if [[ `rfkill... fi" if I want to add it to MY autostart applications. Thanks

Last edited by scot (2017-04-22 20:01:52)

scot · 2017-04-22 21:14:33

Actually, I think i might have a solution. To be honest, I read the 'welcome message for noobs' and it was just a little, uh, unwelcoming. I felt a little bit like i was a baptist who had wandered by chance into a quaker prayer meeting. Anyway, i kept my mouth shut and didn't say to anyone that in fact I had just installed debian -- and I hoped i would be able to read the wiki article here on installing bluetooth. *IT* didn't mention the package 'bluetooth' that i had just installed. So i did a quick "apt-get remove bluetooth ; apt-get install bluez". And then i paired and connected using the bluetoothctl shell, as described in the wiki at https://wiki.archlinux.org/index.php/bluetooth.It worked flawlessly. I'm typing on the keyboard I just connected by following that wiki.
no errors anywhere as far as i can tell.
Before I removed the bluetooth pkg i was seeing exactly the errors you described.

scott

c00ter · 2017-04-23 00:09:44

@scot, not only have you necrobumped a very old thread, but you are running and asking questions regarding Debian. Forum rules allow for discussion and support of Arch Linux only. Please ask for help in your own distribution forums. Reference: Arch Forum Rules

Last edited by c00ter (2017-04-23 00:10:50)

WorMzy · 2017-04-23 00:23:14

As noted, please seek support from your chosen distribution's community.

Closing.

Arch Linux

#1 2014-11-11 08:52:47

[SOLVED]bluetooth error - sap driver initialization failed

#2 2014-11-13 08:03:24

Re: [SOLVED]bluetooth error - sap driver initialization failed

#3 2017-04-22 20:01:04

Re: [SOLVED]bluetooth error - sap driver initialization failed

#4 2017-04-22 21:14:33

Re: [SOLVED]bluetooth error - sap driver initialization failed

#5 2017-04-23 00:09:44

Re: [SOLVED]bluetooth error - sap driver initialization failed

#6 2017-04-23 00:23:14

Re: [SOLVED]bluetooth error - sap driver initialization failed

Board footer