Summary: | net-wireless/bluez Error sap driver | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Lagu <felipematas> |
Component: | [OLD] Unspecified | Assignee: | Pacho Ramos <pacho> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
env
lspci make.conf kernel config |
Description
Lagu
2015-04-11 07:48:28 UTC
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 :/ |