Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
Cannot send files via bluetooth
Cannot send files via bluetooth
I'm using Debian 12 and have installed the necessary packages for bluetooth, including blueman. I can connect to my bluetooth speaker but when attempting to send a file to it I get the error message from blueman : "Unable to find service record" and the file isn't sent. Any suggestions? Thanks in advance for any advice.
- Hallvor
- Global Moderator
- Posts: 2046
- Joined: 2009-04-16 18:35
- Location: Kristiansand, Norway
- Has thanked: 152 times
- Been thanked: 213 times
Re: Cannot send files via bluetooth
Please post the output of
Code: Select all
systemctl status bluetooth
[HowTo] Install and configure Debian bookworm
Debian 12 | KDE Plasma | ThinkPad T440s | 4 × Intel® Core™ i7-4600U CPU @ 2.10GHz | 12 GiB RAM | Mesa Intel® HD Graphics 4400 | 1 TB SSD
Debian 12 | KDE Plasma | ThinkPad T440s | 4 × Intel® Core™ i7-4600U CPU @ 2.10GHz | 12 GiB RAM | Mesa Intel® HD Graphics 4400 | 1 TB SSD
Re: Cannot send files via bluetooth
Hi Hallvor, thanks for the response. The output is:
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; preset: en>
Active: active (running) since Mon 2023-08-07 15:44:50 BST; 18h ago
Docs: man:bluetoothd(8)
Main PID: 697 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 9104)
Memory: 3.4M
CPU: 540ms
CGroup: /system.slice/bluetooth.service
└─697 /usr/libexec/bluetooth/bluetoothd
Warning: some journal files were not opened due to insufficient permissions.
lines 1-13/13 (END)
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; preset: en>
Active: active (running) since Mon 2023-08-07 15:44:50 BST; 18h ago
Docs: man:bluetoothd(8)
Main PID: 697 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 9104)
Memory: 3.4M
CPU: 540ms
CGroup: /system.slice/bluetooth.service
└─697 /usr/libexec/bluetooth/bluetoothd
Warning: some journal files were not opened due to insufficient permissions.
lines 1-13/13 (END)
- Hallvor
- Global Moderator
- Posts: 2046
- Joined: 2009-04-16 18:35
- Location: Kristiansand, Norway
- Has thanked: 152 times
- Been thanked: 213 times
Re: Cannot send files via bluetooth
It looks fine so far. Let's see some log entries:
Edit: I found this. It may be related to insufficient permissions on the remote device: https://askubuntu.com/questions/145767/ ... to-another
Code: Select all
# journalctl -u bluetooth.service
[HowTo] Install and configure Debian bookworm
Debian 12 | KDE Plasma | ThinkPad T440s | 4 × Intel® Core™ i7-4600U CPU @ 2.10GHz | 12 GiB RAM | Mesa Intel® HD Graphics 4400 | 1 TB SSD
Debian 12 | KDE Plasma | ThinkPad T440s | 4 × Intel® Core™ i7-4600U CPU @ 2.10GHz | 12 GiB RAM | Mesa Intel® HD Graphics 4400 | 1 TB SSD
Re: Cannot send files via bluetooth
There's no output from the journalctl command.
Regarding your link, not sure how or if it's even possible to set permissions on the speaker. I don't think it's necessary because it works fine sending a file from my portable mp3 player.
The issue was raised on the blueman github pages a few years ago.
https://github.com/blueman-project/blueman/issues/996
Regarding your link, not sure how or if it's even possible to set permissions on the speaker. I don't think it's necessary because it works fine sending a file from my portable mp3 player.
The issue was raised on the blueman github pages a few years ago.
https://github.com/blueman-project/blueman/issues/996
- Hallvor
- Global Moderator
- Posts: 2046
- Joined: 2009-04-16 18:35
- Location: Kristiansand, Norway
- Has thanked: 152 times
- Been thanked: 213 times
Re: Cannot send files via bluetooth
There should be. Have you disabled logs?
[HowTo] Install and configure Debian bookworm
Debian 12 | KDE Plasma | ThinkPad T440s | 4 × Intel® Core™ i7-4600U CPU @ 2.10GHz | 12 GiB RAM | Mesa Intel® HD Graphics 4400 | 1 TB SSD
Debian 12 | KDE Plasma | ThinkPad T440s | 4 × Intel® Core™ i7-4600U CPU @ 2.10GHz | 12 GiB RAM | Mesa Intel® HD Graphics 4400 | 1 TB SSD
Re: Cannot send files via bluetooth
Ok, my mistake; I mistakenly included the hash symbol when copying the command. The output is:
Hint: You are currently not seeing messages from other users and the system.
Users in groups 'adm', 'systemd-journal' can see all messages.
Pass -q to turn off this notice.
-- No entries --
Hint: You are currently not seeing messages from other users and the system.
Users in groups 'adm', 'systemd-journal' can see all messages.
Pass -q to turn off this notice.
-- No entries --
- Hallvor
- Global Moderator
- Posts: 2046
- Joined: 2009-04-16 18:35
- Location: Kristiansand, Norway
- Has thanked: 152 times
- Been thanked: 213 times
Re: Cannot send files via bluetooth
# means that the command must be executed as root (or sudo)
$ means that the command should be executed as regular user
Oh, and what do you mean by "send a file to it"? You mean play music, I assume, and not physically sending a file to a speaker?
$ means that the command should be executed as regular user
Oh, and what do you mean by "send a file to it"? You mean play music, I assume, and not physically sending a file to a speaker?
[HowTo] Install and configure Debian bookworm
Debian 12 | KDE Plasma | ThinkPad T440s | 4 × Intel® Core™ i7-4600U CPU @ 2.10GHz | 12 GiB RAM | Mesa Intel® HD Graphics 4400 | 1 TB SSD
Debian 12 | KDE Plasma | ThinkPad T440s | 4 × Intel® Core™ i7-4600U CPU @ 2.10GHz | 12 GiB RAM | Mesa Intel® HD Graphics 4400 | 1 TB SSD
Re: Cannot send files via bluetooth
Ok, thanks. Yes by "sending a file" I mean play music.
So here is the output of journalctl :
So here is the output of journalctl :
Code: Select all
Aug 07 15:03:06 debian (uetoothd)[31021]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
Aug 07 15:03:06 debian systemd[1]: Starting bluetooth.service - Bluetooth service...
Aug 07 15:03:06 debian bluetoothd[31021]: Bluetooth daemon 5.66
Aug 07 15:03:06 debian systemd[1]: Started bluetooth.service - Bluetooth service.
Aug 07 15:03:06 debian bluetoothd[31021]: Starting SDP server
Aug 07 15:03:06 debian bluetoothd[31021]: profiles/audio/vcp.c:vcp_init() D-Bus experimental not enabled
Aug 07 15:03:06 debian bluetoothd[31021]: src/plugin.c:plugin_init() Failed to init vcp plugin
Aug 07 15:03:06 debian bluetoothd[31021]: profiles/audio/mcp.c:mcp_init() D-Bus experimental not enabled
Aug 07 15:03:06 debian bluetoothd[31021]: src/plugin.c:plugin_init() Failed to init mcp plugin
Aug 07 15:03:06 debian bluetoothd[31021]: profiles/audio/bap.c:bap_init() D-Bus experimental not enabled
Aug 07 15:03:06 debian bluetoothd[31021]: src/plugin.c:plugin_init() Failed to init bap plugin
Aug 07 15:03:06 debian bluetoothd[31021]: Bluetooth management interface 1.22 initialized
Aug 07 15:03:06 debian bluetoothd[31021]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
Aug 07 15:03:06 debian bluetoothd[31021]: sap-server: Operation not permitted (1)
Aug 07 15:21:53 debian bluetoothd[31021]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 41:42:00:00:03:BE: Protocol not available
Aug 07 15:41:44 debian bluetoothd[31021]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 41:42:00:00:03:BE: Protocol not available
Aug 07 15:44:24 debian bluetoothd[31021]: Terminating
Aug 07 15:44:24 debian systemd[1]: Stopping bluetooth.service - Bluetooth service...
Aug 07 15:44:24 debian bluetoothd[31021]: Stopping SDP server
Aug 07 15:44:24 debian bluetoothd[31021]: Exit
Aug 07 15:44:24 debian systemd[1]: bluetooth.service: Deactivated successfully.
Aug 07 15:44:24 debian systemd[1]: Stopped bluetooth.service - Bluetooth service.
-- Boot 9d8c2b7592af48f9958d2cf935c18e3c --
Aug 07 15:44:50 debian systemd[1]: Starting bluetooth.service - Bluetooth service...
Aug 07 15:44:50 debian (uetoothd)[697]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
Aug 07 15:44:50 debian bluetoothd[697]: Bluetooth daemon 5.66
Aug 07 15:44:50 debian systemd[1]: Started bluetooth.service - Bluetooth service.
Aug 07 15:44:50 debian bluetoothd[697]: Starting SDP server
Aug 07 15:44:50 debian bluetoothd[697]: profiles/audio/vcp.c:vcp_init() D-Bus experimental not enabled
Aug 07 15:44:50 debian bluetoothd[697]: src/plugin.c:plugin_init() Failed to init vcp plugin
Aug 07 15:44:50 debian bluetoothd[697]: profiles/audio/mcp.c:mcp_init() D-Bus experimental not enabled
Aug 07 15:44:50 debian bluetoothd[697]: src/plugin.c:plugin_init() Failed to init mcp plugin
Aug 07 15:44:50 debian bluetoothd[697]: profiles/audio/bap.c:bap_init() D-Bus experimental not enabled
Aug 07 15:44:50 debian bluetoothd[697]: src/plugin.c:plugin_init() Failed to init bap plugin
Aug 07 15:44:50 debian bluetoothd[697]: Bluetooth management interface 1.22 initialized
Aug 07 15:44:50 debian bluetoothd[697]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
Aug 07 15:44:50 debian bluetoothd[697]: sap-server: Operation not permitted (1)
Aug 07 15:44:53 debian bluetoothd[697]: Endpoint registered: sender=:1.26 path=/MediaEndpoint/A2DPSource/ldac_hq
Aug 07 15:44:53 debian bluetoothd[697]: Endpoint registered: sender=:1.26 path=/MediaEndpoint/A2DPSource/ldac_sq
Aug 07 15:44:53 debian bluetoothd[697]: Endpoint registered: sender=:1.26 path=/MediaEndpoint/A2DPSource/ldac_mq
Aug 07 15:44:53 debian bluetoothd[697]: Endpoint registered: sender=:1.26 path=/MediaEndpoint/A2DPSink/aptx_hd
Aug 07 15:44:53 debian bluetoothd[697]: Endpoint registered: sender=:1.26 path=/MediaEndpoint/A2DPSource/aptx_hd
Aug 07 15:44:53 debian bluetoothd[697]: Endpoint registered: sender=:1.26 path=/MediaEndpoint/A2DPSink/aptx
Aug 07 15:44:53 debian bluetoothd[697]: Endpoint registered: sender=:1.26 path=/MediaEndpoint/A2DPSource/aptx
Aug 07 15:44:53 debian bluetoothd[697]: Endpoint registered: sender=:1.26 path=/MediaEndpoint/A2DPSink/sbc
Aug 07 15:44:53 debian bluetoothd[697]: Endpoint registered: sender=:1.26 path=/MediaEndpoint/A2DPSource/sbc
Aug 07 15:44:53 debian bluetoothd[697]: Endpoint registered: sender=:1.26 path=/MediaEndpoint/A2DPSink/sbc_xq_453
Aug 07 15:44:53 debian bluetoothd[697]: Endpoint registered: sender=:1.26 path=/MediaEndpoint/A2DPSource/sbc_xq_453
Aug 07 15:44:53 debian bluetoothd[697]: Endpoint registered: sender=:1.26 path=/MediaEndpoint/A2DPSink/sbc_xq_512
Aug 07 15:44:53 debian bluetoothd[697]: Endpoint registered: sender=:1.26 path=/MediaEndpoint/A2DPSource/sbc_xq_512
Aug 07 15:44:53 debian bluetoothd[697]: Endpoint registered: sender=:1.26 path=/MediaEndpoint/A2DPSink/sbc_xq_552
Aug 07 15:44:53 debian bluetoothd[697]: Endpoint registered: sender=:1.26 path=/MediaEndpoint/A2DPSource/sbc_xq_552
Aug 07 15:45:15 debian bluetoothd[697]: Endpoint unregistered: sender=:1.26 path=/MediaEndpoint/A2DPSource/ldac_hq
Aug 07 15:45:15 debian bluetoothd[697]: Endpoint unregistered: sender=:1.26 path=/MediaEndpoint/A2DPSource/ldac_sq
Aug 07 15:45:15 debian bluetoothd[697]: Endpoint unregistered: sender=:1.26 path=/MediaEndpoint/A2DPSource/ldac_mq
Aug 07 15:45:15 debian bluetoothd[697]: Endpoint unregistered: sender=:1.26 path=/MediaEndpoint/A2DPSink/aptx_hd
Aug 07 15:45:15 debian bluetoothd[697]: Endpoint unregistered: sender=:1.26 path=/MediaEndpoint/A2DPSource/aptx_hd
Aug 07 15:45:15 debian bluetoothd[697]: Endpoint unregistered: sender=:1.26 path=/MediaEndpoint/A2DPSink/aptx
Aug 07 15:45:15 debian bluetoothd[697]: Endpoint unregistered: sender=:1.26 path=/MediaEndpoint/A2DPSource/aptx
Aug 07 15:45:15 debian bluetoothd[697]: Endpoint unregistered: sender=:1.26 path=/MediaEndpoint/A2DPSink/sbc
Aug 07 15:45:15 debian bluetoothd[697]: Endpoint unregistered: sender=:1.26 path=/MediaEndpoint/A2DPSource/sbc
Aug 07 15:45:15 debian bluetoothd[697]: Endpoint unregistered: sender=:1.26 path=/MediaEndpoint/A2DPSink/sbc_xq_453
Aug 07 15:45:15 debian bluetoothd[697]: Endpoint unregistered: sender=:1.26 path=/MediaEndpoint/A2DPSource/sbc_xq_453
Aug 07 15:45:15 debian bluetoothd[697]: Endpoint unregistered: sender=:1.26 path=/MediaEndpoint/A2DPSink/sbc_xq_512
Aug 07 15:45:15 debian bluetoothd[697]: Endpoint unregistered: sender=:1.26 path=/MediaEndpoint/A2DPSource/sbc_xq_512
Aug 07 15:45:15 debian bluetoothd[697]: Endpoint unregistered: sender=:1.26 path=/MediaEndpoint/A2DPSink/sbc_xq_552
Aug 07 15:45:15 debian bluetoothd[697]: Endpoint unregistered: sender=:1.26 path=/MediaEndpoint/A2DPSource/sbc_xq_552
Aug 07 15:45:15 debian bluetoothd[697]: Endpoint registered: sender=:1.48 path=/MediaEndpoint/A2DPSource/ldac_hq
Aug 07 15:45:15 debian bluetoothd[697]: Endpoint registered: sender=:1.48 path=/MediaEndpoint/A2DPSource/ldac_sq
Aug 07 15:45:15 debian bluetoothd[697]: Endpoint registered: sender=:1.48 path=/MediaEndpoint/A2DPSource/ldac_mq
Aug 07 15:45:15 debian bluetoothd[697]: Endpoint registered: sender=:1.48 path=/MediaEndpoint/A2DPSink/aptx_hd
Aug 07 15:45:15 debian bluetoothd[697]: Endpoint registered: sender=:1.48 path=/MediaEndpoint/A2DPSource/aptx_hd
Aug 07 15:45:15 debian bluetoothd[697]: Endpoint registered: sender=:1.48 path=/MediaEndpoint/A2DPSink/aptx
Aug 07 15:45:15 debian bluetoothd[697]: Endpoint registered: sender=:1.48 path=/MediaEndpoint/A2DPSource/aptx
Aug 07 15:45:15 debian bluetoothd[697]: Endpoint registered: sender=:1.48 path=/MediaEndpoint/A2DPSink/sbc
Aug 07 15:45:15 debian bluetoothd[697]: Endpoint registered: sender=:1.48 path=/MediaEndpoint/A2DPSource/sbc
Aug 07 15:45:15 debian bluetoothd[697]: Endpoint registered: sender=:1.48 path=/MediaEndpoint/A2DPSink/sbc_xq_453
Aug 07 15:45:15 debian bluetoothd[697]: Endpoint registered: sender=:1.48 path=/MediaEndpoint/A2DPSource/sbc_xq_453
Aug 07 15:45:15 debian bluetoothd[697]: Endpoint registered: sender=:1.48 path=/MediaEndpoint/A2DPSink/sbc_xq_512
Aug 07 15:45:15 debian bluetoothd[697]: Endpoint registered: sender=:1.48 path=/MediaEndpoint/A2DPSource/sbc_xq_512
Aug 07 15:45:15 debian bluetoothd[697]: Endpoint registered: sender=:1.48 path=/MediaEndpoint/A2DPSink/sbc_xq_552
Aug 07 15:45:15 debian bluetoothd[697]: Endpoint registered: sender=:1.48 path=/MediaEndpoint/A2DPSource/sbc_xq_552
Aug 07 15:45:51 debian bluetoothd[697]: /org/bluez/hci0/dev_41_42_00_00_03_BE/fd0: fd(40) ready
Aug 07 16:14:56 debian bluetoothd[697]: /org/bluez/hci0/dev_41_42_00_00_03_BE/fd1: fd(40) ready
Aug 07 16:19:01 debian bluetoothd[697]: /org/bluez/hci0/dev_41_42_00_00_03_BE/sep1/fd2: fd(40) ready
- sunrat
- Administrator
- Posts: 6600
- Joined: 2006-08-29 09:12
- Location: Melbourne, Australia
- Has thanked: 119 times
- Been thanked: 503 times
Re: Cannot send files via bluetooth
In Debian 12 using Pipewire, you need libspa-0.2-bluetooth for bluetooth audio. See the wiki - https://wiki.debian.org/PipeWire
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ” Remember to BACKUP!
Those who have lost data
...and those who have not lost data YET ” Remember to BACKUP!
Re: Cannot send files via bluetooth
Hi sunrat, I installed the pipewire meta-package as recommended but it hasn't solved the problem... or maybe you weren't suggesting that it would?
- Hallvor
- Global Moderator
- Posts: 2046
- Joined: 2009-04-16 18:35
- Location: Kristiansand, Norway
- Has thanked: 152 times
- Been thanked: 213 times
Re: Cannot send files via bluetooth
The error message "Protocol not available" suggests that the system is having trouble finding the appropriate protocol for audio streaming. It looks like a compatibility issue.
Does this work?
https://www.reddit.com/r/archlinux/comm ... _days_ago/
Does this work?
Code: Select all
rmmod btusb
rmmod btintel
modprobe btintel
modprobe btusb
[HowTo] Install and configure Debian bookworm
Debian 12 | KDE Plasma | ThinkPad T440s | 4 × Intel® Core™ i7-4600U CPU @ 2.10GHz | 12 GiB RAM | Mesa Intel® HD Graphics 4400 | 1 TB SSD
Debian 12 | KDE Plasma | ThinkPad T440s | 4 × Intel® Core™ i7-4600U CPU @ 2.10GHz | 12 GiB RAM | Mesa Intel® HD Graphics 4400 | 1 TB SSD
- sunrat
- Administrator
- Posts: 6600
- Joined: 2006-08-29 09:12
- Location: Melbourne, Australia
- Has thanked: 119 times
- Been thanked: 503 times
Re: Cannot send files via bluetooth
Show
Code: Select all
apt list --installed libspa-0.2-bluetooth
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ” Remember to BACKUP!
Those who have lost data
...and those who have not lost data YET ” Remember to BACKUP!
Re: Cannot send files via bluetooth
I'm afraid not.Hallvor wrote: ↑2023-08-08 14:47 The error message "Protocol not available" suggests that the system is having trouble finding the appropriate protocol for audio streaming. It looks like a compatibility issue.
Does this work?
https://www.reddit.com/r/archlinux/comm ... _days_ago/Code: Select all
rmmod btusb rmmod btintel modprobe btintel modprobe btusb
Thanks for trying to help, but it's not really a big deal and I have better things to do, so I'm giving up.
-
- Posts: 14
- Joined: 2024-04-04 01:53
- Has thanked: 3 times
Re: Cannot send files via bluetooth
Heh - this happens a lot with Bluetooth. It's so arcane that most just give up. I guess that's how you separate the men from the boys in Debian? If you see someone using Debian to play music through a Bluetooth speaker, should you: a) ask for his autograph?, b) fall to your knees before him and bow?, c) grovel and ask for help to get your system configured? One thing is for sure: You will not find the information required in the documentation. LOLJulesD wrote: ↑2023-08-09 08:52I'm afraid not.Hallvor wrote: ↑2023-08-08 14:47 The error message "Protocol not available" suggests that the system is having trouble finding the appropriate protocol for audio streaming. It looks like a compatibility issue.
Does this work?
https://www.reddit.com/r/archlinux/comm ... _days_ago/Code: Select all
rmmod btusb rmmod btintel modprobe btintel modprobe btusb
Thanks for trying to help, but it's not really a big deal and I have better things to do, so I'm giving up.