Bluetooth sap driver initialization failed

Saved searches

Use saved searches to filter your results more quickly

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bluetooth headset not working: Sap driver initialization failed. #103161

Bluetooth headset not working: Sap driver initialization failed. #103161

Comments

Describe the bug
I’m expriencing regression in bluetooth support for pulseaudio (and bluetooth in general).

From log ( journalctl -eu bluetoot ):

Nov 08 20:59:11 nixos-mainframe systemd[1]: Starting Bluetooth service. Nov 08 20:59:11 nixos-mainframe bluetoothd[1157]: Bluetooth daemon 5.54 Nov 08 20:59:11 nixos-mainframe bluetoothd[1157]: Starting SDP server Nov 08 20:59:11 nixos-mainframe systemd[1]: Started Bluetooth service. Nov 08 20:59:11 nixos-mainframe bluetoothd[1157]: Bluetooth management interface 1.14 initialized Nov 08 20:59:11 nixos-mainframe bluetoothd[1157]: Sap driver initialization failed. Nov 08 20:59:11 nixos-mainframe bluetoothd[1157]: sap-server: Operation not permitted (1) Nov 08 20:59:19 nixos-mainframe bluetoothd[1157]: Endpoint registered: sender=:1.56 path=/MediaEndpoint/A2DPSource/VENDOR/LDAC Nov 08 20:59:19 nixos-mainframe bluetoothd[1157]: Endpoint registered: sender=:1.56 path=/MediaEndpoint/A2DPSource/VENDOR/APTXHD Nov 08 20:59:19 nixos-mainframe bluetoothd[1157]: Endpoint registered: sender=:1.56 path=/MediaEndpoint/A2DPSource/VENDOR/APTX Nov 08 20:59:19 nixos-mainframe bluetoothd[1157]: Endpoint registered: sender=:1.56 path=/MediaEndpoint/A2DPSource/AAC Nov 08 20:59:19 nixos-mainframe bluetoothd[1157]: Endpoint registered: sender=:1.56 path=/MediaEndpoint/A2DPSource/SBC Nov 08 20:59:19 nixos-mainframe bluetoothd[1157]: Endpoint registered: sender=:1.56 path=/MediaEndpoint/A2DPSink/VENDOR/APTXHD Nov 08 20:59:19 nixos-mainframe bluetoothd[1157]: Endpoint registered: sender=:1.56 path=/MediaEndpoint/A2DPSink/VENDOR/APTX Nov 08 20:59:19 nixos-mainframe bluetoothd[1157]: Endpoint registered: sender=:1.56 path=/MediaEndpoint/A2DPSink/AAC Nov 08 20:59:19 nixos-mainframe bluetoothd[1157]: Endpoint registered: sender=:1.56 path=/MediaEndpoint/A2DPSink/SBC Nov 08 20:59:33 nixos-mainframe bluetoothd[1157]: 00:1B:66:C0:F6:98: error updating services: Host is down (112) 

I’m also experiencing regression with connectivity of XBox One Wireless Controller which requires disabling of ertm ( echo ‘Y’ >| /sys/module/bluetooth/parameters/disable_ertm ) normally but I’m enable to connect it. I haven’t tried to connect any other bluetooth device so all I tried don’t work at the moment for me.

To Reproduce
Steps to reproduce the behavior:

hardware = < pulseaudio = < # Sound config enable = true; package = pkgs.pulseaudioFull; extraModules = [ pkgs.pulseaudio-modules-bt ]; support32Bit = true; extraConfig = " load-module module-switch-on-connect "; >; # Bluetooth bluetooth = < enable = true; >; >; >; 

Expected behavior
Devices should be connected and working.

Additional context
Add any other context about the problem here.

Notify maintainers
cc @rnhmjoj who worked on Bluetooth recently.

Metadata
Please run nix-shell -p nix-info —run «nix-info -m» and paste the result.

 - system: `"x86_64-linux"` - host os: `Linux 5.4.75, NixOS, 21.03pre250878.a52e974cff8 (Okapi)` - multi-user?: `yes` - sandbox: `yes` - version: `nix-env (Nix) 2.3.8` - channels(root): `"nixos-21.03pre250878.a52e974cff8, nixos-hardware"` - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos` 

# a list of nixpkgs attributes affected by the problem attribute: # a list of nixos modules affected by the problem module:

The text was updated successfully, but these errors were encountered:

Источник

Ошибка SAP при статусе службы Bluetooth

Я получаю сообщение об ошибке состояния службы Bluetooth.

Мне нужно руководство, чтобы устранить эту ошибку.

 pi@raspberrypi:~ $ sudo service bluetooth status * bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled) Active: active (running) since Sat 2016-01-09 19:12:47 UTC; 1min 12s ago Docs: man:bluetoothd(8) Main PID: 370 (bluetoothd) Status: "Running" CGroup: /system.slice/bluetooth.service `-370 /usr/lib/bluetooth/bluetoothd Jan 09 19:12:46 raspberrypi bluetoothd[370]: Bluetooth daemon 5.23 Jan 09 19:12:47 raspberrypi bluetoothd[370]: Starting SDP server Jan 09 19:12:47 raspberrypi systemd[1]: Started Bluetooth service. Jan 09 19:12:47 raspberrypi bluetoothd[370]: Bluetooth management interface 1.9 initialized Jan 09 19:12:47 raspberrypi bluetoothd[370]: Sap driver initialization failed. Jan 09 19:12:47 raspberrypi bluetoothd[370]: sap-server: Operation not permitted (1) pi@raspberrypi:~ $ 

В этом контексте sap является протоколом доступа к SIM-карте и, следовательно, скорее всего, связан с подключением к мобильному телефону (и предположительно к Интернет-данным). Учитывая , что все остальные сообщения об успешном запуске в Bluetooth — демон , я не совсем уверен , что это ошибка как таковая .

SAP связан с доступом к симу, для получения дополнительной информации об этом bugs.launchpad.net/ubuntu/+source/bluez/+bug/1629632

Источник

Arch Linux

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)

Источник