Error starting bluetooth service in systemd: ● bluetooth.service - Bluetooth service Loaded: loaded (/usr/lib64/systemd/system/bluetooth.service; enabled) Active: active (running) since sáb 2015-04-11 04:20:38 CLST; 17min ago Docs: man:bluetoothd(8) Main PID: 2581 (bluetoothd) Status: "Running" CGroup: /system.slice/bluetooth.service └─2581 /usr/libexec/bluetooth/bluetoothd abr 11 04:20:37 Q92B37PZMW71FP bluetoothd[2581]: Bluetooth daemon 5.25 abr 11 04:20:38 Q92B37PZMW71FP bluetoothd[2581]: Starting SDP server abr 11 04:20:38 Q92B37PZMW71FP bluetoothd[2581]: Bluetooth management interface 1.8 initialized abr 11 04:20:39 Q92B37PZMW71FP bluetoothd[2581]: Sap driver initialization failed. abr 11 04:20:39 Q92B37PZMW71FP bluetoothd[2581]: sap-server: Operation not permitted (1) abr 11 04:21:50 pipe-PC bluetoothd[2581]: Endpoint registered: sender=:1.31 path=/MediaEndpoint/A2DPSource abr 11 04:21:50 pipe-PC bluetoothd[2581]: Endpoint registered: sender=:1.31 path=/MediaEndpoint/A2DPSink abr 11 04:37:50 pipe-PC systemd[1]: Started Bluetooth service. lines 4-5 are error messages, it always show that but service is running, using version 5.25.
Created attachment 401022 [details] env
Created attachment 401024 [details] lspci
Created attachment 401026 [details] make.conf
Created attachment 401028 [details] kernel config
That is normal because that device is likely not available on your PC: http://en.wikipedia.org/wiki/List_of_Bluetooth_profiles#SIM_Access_Profile_.28SAP.2C_SIM.2C_rSAP.29 https://bugs.archlinux.org/task/41247
mm, thx for the answer, the solution proposed is start bluetoothd disabling sap server, but for that we most modify the service file of systemd, i think can be better idea add a config file in /etc/conf.d/ with parameters for the service. ¿what do you think?
Well, using config files is in general discouraged: https://wiki.gentoo.org/wiki/Project:Systemd/Ebuild_policy#Unit_file_guidelineshttps://wiki.gentoo.org/wiki/Project:Systemd/conf.d_files And, in this case, it's not really needed as the daemon is ready to not find the SAP device and show an error but still run without any other issues :/
