BlueZ error setting privacy on Raspbian
I am trying to use BlueZ 5.45 on a raspberry pi running Raspbian Jessie and cannot set up BlueZ to use LE Privacy. When I start the bluetooth daemon I get the following messages:
Jul 26 22:00:19 raspberrypi bluetoothd[18971]: Bluetooth daemon 5.45
Jul 26 22:00:19 raspberrypi bluetoothd[18971]: Starting SDP server
Jul 26 22:00:19 raspberrypi bluetoothd[18971]: Bluetooth management interface 1.14 initialized
Jul 26 22:00:19 raspberrypi bluetoothd[18971]: No IRK stored
Jul 26 22:00:19 raspberrypi bluetoothd[18971]: Failed to open crypto
Jul 26 22:00:19 raspberrypi systemd[1]: Started Bluetooth service.
BlueZ tries to set up LE Privacy, finds there is no IRK stored, but does not have access to the crypto functions in the kernel to generate one.
How can I get past this error?
Privacy was set by adding the line Privacy = device
to /etc/bluetooth/main.conf
and adding a symlink at /usr/local/etc
.
linux bluetooth bluez
bumped to the homepage by Community♦ 1 hour ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I am trying to use BlueZ 5.45 on a raspberry pi running Raspbian Jessie and cannot set up BlueZ to use LE Privacy. When I start the bluetooth daemon I get the following messages:
Jul 26 22:00:19 raspberrypi bluetoothd[18971]: Bluetooth daemon 5.45
Jul 26 22:00:19 raspberrypi bluetoothd[18971]: Starting SDP server
Jul 26 22:00:19 raspberrypi bluetoothd[18971]: Bluetooth management interface 1.14 initialized
Jul 26 22:00:19 raspberrypi bluetoothd[18971]: No IRK stored
Jul 26 22:00:19 raspberrypi bluetoothd[18971]: Failed to open crypto
Jul 26 22:00:19 raspberrypi systemd[1]: Started Bluetooth service.
BlueZ tries to set up LE Privacy, finds there is no IRK stored, but does not have access to the crypto functions in the kernel to generate one.
How can I get past this error?
Privacy was set by adding the line Privacy = device
to /etc/bluetooth/main.conf
and adding a symlink at /usr/local/etc
.
linux bluetooth bluez
bumped to the homepage by Community♦ 1 hour ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I am trying to use BlueZ 5.45 on a raspberry pi running Raspbian Jessie and cannot set up BlueZ to use LE Privacy. When I start the bluetooth daemon I get the following messages:
Jul 26 22:00:19 raspberrypi bluetoothd[18971]: Bluetooth daemon 5.45
Jul 26 22:00:19 raspberrypi bluetoothd[18971]: Starting SDP server
Jul 26 22:00:19 raspberrypi bluetoothd[18971]: Bluetooth management interface 1.14 initialized
Jul 26 22:00:19 raspberrypi bluetoothd[18971]: No IRK stored
Jul 26 22:00:19 raspberrypi bluetoothd[18971]: Failed to open crypto
Jul 26 22:00:19 raspberrypi systemd[1]: Started Bluetooth service.
BlueZ tries to set up LE Privacy, finds there is no IRK stored, but does not have access to the crypto functions in the kernel to generate one.
How can I get past this error?
Privacy was set by adding the line Privacy = device
to /etc/bluetooth/main.conf
and adding a symlink at /usr/local/etc
.
linux bluetooth bluez
I am trying to use BlueZ 5.45 on a raspberry pi running Raspbian Jessie and cannot set up BlueZ to use LE Privacy. When I start the bluetooth daemon I get the following messages:
Jul 26 22:00:19 raspberrypi bluetoothd[18971]: Bluetooth daemon 5.45
Jul 26 22:00:19 raspberrypi bluetoothd[18971]: Starting SDP server
Jul 26 22:00:19 raspberrypi bluetoothd[18971]: Bluetooth management interface 1.14 initialized
Jul 26 22:00:19 raspberrypi bluetoothd[18971]: No IRK stored
Jul 26 22:00:19 raspberrypi bluetoothd[18971]: Failed to open crypto
Jul 26 22:00:19 raspberrypi systemd[1]: Started Bluetooth service.
BlueZ tries to set up LE Privacy, finds there is no IRK stored, but does not have access to the crypto functions in the kernel to generate one.
How can I get past this error?
Privacy was set by adding the line Privacy = device
to /etc/bluetooth/main.conf
and adding a symlink at /usr/local/etc
.
linux bluetooth bluez
linux bluetooth bluez
asked Jul 26 '17 at 22:25
user243636user243636
63
63
bumped to the homepage by Community♦ 1 hour ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 1 hour ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Change to privacy = off but set Controller = le in /etc/bluetooth/main.conf
seems to have fixed most for me still tinkering with bluetooth to get autoconnect to mobile phone when near at boot time or thereof...there have been others, but I don't think it is of any concern
also edit the bluetooth.service file = /etc/systemd/system/bluetooth.target.wants/bluetooth.service add in the file ExecStart=/usr/lib/bluetooth/bluetoothd --compat --noplugin=sap -E most of the errors will disappear except service change handle error
– user221166
Jan 6 '18 at 3:02
Please edit your answer to include everything, instead of adding a comment.
– Patrick Mevzek
Jan 6 '18 at 3:11
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f382031%2fbluez-error-setting-privacy-on-raspbian%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Change to privacy = off but set Controller = le in /etc/bluetooth/main.conf
seems to have fixed most for me still tinkering with bluetooth to get autoconnect to mobile phone when near at boot time or thereof...there have been others, but I don't think it is of any concern
also edit the bluetooth.service file = /etc/systemd/system/bluetooth.target.wants/bluetooth.service add in the file ExecStart=/usr/lib/bluetooth/bluetoothd --compat --noplugin=sap -E most of the errors will disappear except service change handle error
– user221166
Jan 6 '18 at 3:02
Please edit your answer to include everything, instead of adding a comment.
– Patrick Mevzek
Jan 6 '18 at 3:11
add a comment |
Change to privacy = off but set Controller = le in /etc/bluetooth/main.conf
seems to have fixed most for me still tinkering with bluetooth to get autoconnect to mobile phone when near at boot time or thereof...there have been others, but I don't think it is of any concern
also edit the bluetooth.service file = /etc/systemd/system/bluetooth.target.wants/bluetooth.service add in the file ExecStart=/usr/lib/bluetooth/bluetoothd --compat --noplugin=sap -E most of the errors will disappear except service change handle error
– user221166
Jan 6 '18 at 3:02
Please edit your answer to include everything, instead of adding a comment.
– Patrick Mevzek
Jan 6 '18 at 3:11
add a comment |
Change to privacy = off but set Controller = le in /etc/bluetooth/main.conf
seems to have fixed most for me still tinkering with bluetooth to get autoconnect to mobile phone when near at boot time or thereof...there have been others, but I don't think it is of any concern
Change to privacy = off but set Controller = le in /etc/bluetooth/main.conf
seems to have fixed most for me still tinkering with bluetooth to get autoconnect to mobile phone when near at boot time or thereof...there have been others, but I don't think it is of any concern
answered Jan 6 '18 at 2:58
user221166user221166
1
1
also edit the bluetooth.service file = /etc/systemd/system/bluetooth.target.wants/bluetooth.service add in the file ExecStart=/usr/lib/bluetooth/bluetoothd --compat --noplugin=sap -E most of the errors will disappear except service change handle error
– user221166
Jan 6 '18 at 3:02
Please edit your answer to include everything, instead of adding a comment.
– Patrick Mevzek
Jan 6 '18 at 3:11
add a comment |
also edit the bluetooth.service file = /etc/systemd/system/bluetooth.target.wants/bluetooth.service add in the file ExecStart=/usr/lib/bluetooth/bluetoothd --compat --noplugin=sap -E most of the errors will disappear except service change handle error
– user221166
Jan 6 '18 at 3:02
Please edit your answer to include everything, instead of adding a comment.
– Patrick Mevzek
Jan 6 '18 at 3:11
also edit the bluetooth.service file = /etc/systemd/system/bluetooth.target.wants/bluetooth.service add in the file ExecStart=/usr/lib/bluetooth/bluetoothd --compat --noplugin=sap -E most of the errors will disappear except service change handle error
– user221166
Jan 6 '18 at 3:02
also edit the bluetooth.service file = /etc/systemd/system/bluetooth.target.wants/bluetooth.service add in the file ExecStart=/usr/lib/bluetooth/bluetoothd --compat --noplugin=sap -E most of the errors will disappear except service change handle error
– user221166
Jan 6 '18 at 3:02
Please edit your answer to include everything, instead of adding a comment.
– Patrick Mevzek
Jan 6 '18 at 3:11
Please edit your answer to include everything, instead of adding a comment.
– Patrick Mevzek
Jan 6 '18 at 3:11
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f382031%2fbluez-error-setting-privacy-on-raspbian%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown