Bluetooth - bluez service doesn't exist after update to Qt6

Hello,sorry for my bad english I’m from France :wink:

For the moment i could share documents beetween PC and phone (Moto G4+) normally.I never had issues to connect my advices and sharing under Kde.Friday I updated my system after to add a hard disk to create my nexcloud later and to test my new fiber connection (amazing :star_struck:).I discover system was under Plasma 6 and Qt6 now.When I wanted to transfer a document from PC to my phone (with Dolphin → Share) it doesn’t work.

[biscotte@cracotte ~]$ systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: disabled)
     Active: active (running) since Sun 2024-03-10 14:41:52 CET; 1h 11min ago
       Docs: man:bluetoothd(8)
   Main PID: 766 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 19070)
     Memory: 2.6M (peak: 3.2M)
        CPU: 43ms
     CGroup: /system.slice/bluetooth.service
             └─766 /usr/lib/bluetooth/bluetoothd

mars 10 14:41:58 cracotte bluetoothd[766]: Endpoint registered: sender=:1.29 path=/MediaEndpoint/A2DPSource/aptx_ll_0
mars 10 14:41:58 cracotte bluetoothd[766]: Endpoint registered: sender=:1.29 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
mars 10 14:41:58 cracotte bluetoothd[766]: Endpoint registered: sender=:1.29 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
mars 10 14:41:58 cracotte bluetoothd[766]: Endpoint registered: sender=:1.29 path=/MediaEndpoint/A2DPSource/faststream
mars 10 14:41:58 cracotte bluetoothd[766]: Endpoint registered: sender=:1.29 path=/MediaEndpoint/A2DPSource/faststream_duplex
mars 10 14:41:58 cracotte bluetoothd[766]: Endpoint registered: sender=:1.29 path=/MediaEndpoint/A2DPSink/opus_05
mars 10 14:41:58 cracotte bluetoothd[766]: Endpoint registered: sender=:1.29 path=/MediaEndpoint/A2DPSource/opus_05
mars 10 14:41:58 cracotte bluetoothd[766]: Endpoint registered: sender=:1.29 path=/MediaEndpoint/A2DPSink/opus_05_duplex
mars 10 14:41:58 cracotte bluetoothd[766]: Endpoint registered: sender=:1.29 path=/MediaEndpoint/A2DPSource/opus_05_duplex
mars 10 14:48:36 cracotte bluetoothd[766]: /org/bluez/hci0/dev_88_79_7E_9D_5F_BE/fd0: fd(30) ready

My devices are recognize and there seems not to be an harware problem

[biscotte@cracotte ~]$ rfkill
ID TYPE      DEVICE     SOFT     HARD
 1 bluetooth hci0   débloqué débloqué
 2 wlan      phy0   débloqué débloqué

After search on the web and the forum I don’t fix the issue.But perhaps the problem is due to a conflict with Qt6.I don’t know.

[biscotte@cracotte ~]$ journalctl -b | grep blue
mars 10 14:41:52 cracotte bluetoothd[766]: Bluetooth daemon 5.73
mars 10 14:41:52 cracotte bluetoothd[766]: Starting SDP server
mars 10 14:41:52 cracotte dbus-daemon[767]: [system] Activating systemd to hand-off: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.2' (uid=0 pid=766 comm="/usr/lib/bluetooth/bluetoothd")
mars 10 14:41:52 cracotte bluetoothd[766]: src/plugin.c:init_plugin() System does not support bap plugin
mars 10 14:41:52 cracotte bluetoothd[766]: src/plugin.c:init_plugin() System does not support bass plugin
mars 10 14:41:52 cracotte bluetoothd[766]: src/plugin.c:init_plugin() System does not support mcp plugin
mars 10 14:41:52 cracotte bluetoothd[766]: src/plugin.c:init_plugin() System does not support vcp plugin
mars 10 14:41:52 cracotte bluetoothd[766]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled
mars 10 14:41:52 cracotte bluetoothd[766]: src/plugin.c:init_plugin() System does not support micp plugin
mars 10 14:41:52 cracotte bluetoothd[766]: src/plugin.c:init_plugin() System does not support ccp plugin
mars 10 14:41:52 cracotte bluetoothd[766]: src/plugin.c:init_plugin() System does not support csip plugin
mars 10 14:41:52 cracotte bluetoothd[766]: Bluetooth management interface 1.22 initialized
mars 10 14:41:52 cracotte bluetoothd[766]: Battery Provider Manager created
mars 10 14:41:52 cracotte bluetoothd[766]: Failed to load LTKs for hci0: Invalid Parameters (0x0d)
mars 10 14:41:52 cracotte bluetoothd[766]: Failed to load IRKs for hci0: Invalid Parameters (0x0d)
mars 10 14:41:53 cracotte NetworkManager[886]: <info>  [1710078113.1737] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.46.0-2/libnm-device-plugin-bluetooth.so)
mars 10 14:41:58 cracotte bluetoothd[766]: Endpoint registered: sender=:1.29 path=/MediaEndpoint/A2DPSource/ldac
mars 10 14:41:58 cracotte bluetoothd[766]: Endpoint registered: sender=:1.29 path=/MediaEndpoint/A2DPSink/aptx_hd
mars 10 14:41:58 cracotte bluetoothd[766]: Endpoint registered: sender=:1.29 path=/MediaEndpoint/A2DPSource/aptx_hd
mars 10 14:41:58 cracotte bluetoothd[766]: Endpoint registered: sender=:1.29 path=/MediaEndpoint/A2DPSink/aptx
mars 10 14:41:58 cracotte bluetoothd[766]: Endpoint registered: sender=:1.29 path=/MediaEndpoint/A2DPSource/aptx
mars 10 14:41:58 cracotte bluetoothd[766]: Endpoint registered: sender=:1.29 path=/MediaEndpoint/A2DPSink/aac
mars 10 14:41:58 cracotte bluetoothd[766]: Endpoint registered: sender=:1.29 path=/MediaEndpoint/A2DPSource/aac
mars 10 14:41:58 cracotte bluetoothd[766]: Endpoint registered: sender=:1.29 path=/MediaEndpoint/A2DPSink/sbc
mars 10 14:41:58 cracotte bluetoothd[766]: Endpoint registered: sender=:1.29 path=/MediaEndpoint/A2DPSource/sbc
mars 10 14:41:58 cracotte bluetoothd[766]: Endpoint registered: sender=:1.29 path=/MediaEndpoint/A2DPSink/sbc_xq
mars 10 14:41:58 cracotte bluetoothd[766]: Endpoint registered: sender=:1.29 path=/MediaEndpoint/A2DPSource/sbc_xq
mars 10 14:41:58 cracotte bluetoothd[766]: Endpoint registered: sender=:1.29 path=/MediaEndpoint/A2DPSource/aptx_ll_1
mars 10 14:41:58 cracotte bluetoothd[766]: Endpoint registered: sender=:1.29 path=/MediaEndpoint/A2DPSource/aptx_ll_0
mars 10 14:41:58 cracotte bluetoothd[766]: Endpoint registered: sender=:1.29 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
mars 10 14:41:58 cracotte bluetoothd[766]: Endpoint registered: sender=:1.29 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
mars 10 14:41:58 cracotte bluetoothd[766]: Endpoint registered: sender=:1.29 path=/MediaEndpoint/A2DPSource/faststream
mars 10 14:41:58 cracotte bluetoothd[766]: Endpoint registered: sender=:1.29 path=/MediaEndpoint/A2DPSource/faststream_duplex
mars 10 14:41:58 cracotte bluetoothd[766]: Endpoint registered: sender=:1.29 path=/MediaEndpoint/A2DPSink/opus_05
mars 10 14:41:58 cracotte bluetoothd[766]: Endpoint registered: sender=:1.29 path=/MediaEndpoint/A2DPSource/opus_05
mars 10 14:41:58 cracotte bluetoothd[766]: Endpoint registered: sender=:1.29 path=/MediaEndpoint/A2DPSink/opus_05_duplex
mars 10 14:41:58 cracotte bluetoothd[766]: Endpoint registered: sender=:1.29 path=/MediaEndpoint/A2DPSource/opus_05_duplex
mars 10 14:41:58 cracotte kded6[1205]: kf.bluezqt: PendingCall Error: "The name org.bluez.obex was not provided by any .service files"
mars 10 14:42:44 cracotte bluedevil-sendfile[3035]: kf.bluezqt: PendingCall Error: "The name org.bluez.obex was not provided by any .service files"
mars 10 14:48:36 cracotte bluetoothd[766]: /org/bluez/hci0/dev_88_79_7E_9D_5F_BE/fd0: fd(30) ready
mars 10 14:48:43 cracotte bluedevil-sendfile[3421]: kf.bluezqt: PendingCall Error: "The name org.bluez.obex was not provided by any .service files"
mars 10 14:52:05 cracotte bluedevil-sendfile[3500]: kf.bluezqt: PendingCall Error: "The name org.bluez.obex was not provided by any .service files"
mars 10 15:02:54 cracotte bluedevil-sendfile[3665]: kf.bluezqt: PendingCall Error: "The name org.bluez.obex was not provided by any .service files"
mars 10 15:34:13 cracotte bluedevil-sendfile[4812]: kf.bluezqt: PendingCall Error: "The name org.bluez.obex was not provided by any .service files"

This is my bluez paquages installed on my system.

bluez 5.73-3
bluez-libs 5.73-3
bluez-qt 6.0.0-1
bluez-qt5 5.115.0-1
bluez-utils 5.73-3

Welcome to the forum! :smile:

Have you seen these articles: https://discovery.endeavouros.com/?s=bluetooth
Maybe some of them could be of help to you.

Hello yes I did it and I read archwiki too and several post on github or reddit etc…
I found this and Dolphin use BluezQt to send a file.My devices are paired and bluedevil works fine (I can listen music normally to my bluetooth speakers).But it can’t transfer a file to my phone while it worked fine before update to Qt6.

That may be an issue with Qt6 or Plasma6. Their sites may have more info or bug report about this. If so, I believe they will fix it, hopefully soon.

I looked for bluez 's homepage project to see if my bugs had been reported but no :cry:
I’m going to report it on the Qt team and to see on their forum if another one had the same issue.
If I fix the pb I will report it on my post here

1 Like

Hmmm, interesting. I’m on plasma 6 too. I have all the packages installed and bluetooth is working fine for my keyboard, mouse, and earbuds.

When I do what @biscotte describes, Plasma indicates my phone is not available. However it does work with KDE connect.

@biscotte Have you attempted to use KDE connect to send the document? I sent a 4.5mb photo and took less than one second. Maybe that would be a solution for you?

I don’t know if this topic is related or of any help.

Edit: I forgot to add. What packages are listed with pacman -Ss bluez (or with yay, depending on your preference)? For Plasma 6, this is what I have installed (a couple of which I manually installed and may or may not be installed for you.):

extra/bluez 5.73-3 [installed]
    Daemons for the bluetooth protocol stack
extra/bluez-libs 5.73-3 [installed]
    Deprecated libraries for the bluetooth protocol stack
extra/bluez-qt 6.0.0-1 (kf6) [installed]
    Qt wrapper for Bluez 5 DBus API
extra/bluez-qt5 5.115.0-1 (kf5) [installed]
    Qt wrapper for Bluez 5 DBus API
extra/bluez-tools 0.2.0-5 [installed]
    A set of tools to manage Bluetooth devices for Linux
extra/bluez-utils 5.73-3 [installed]
    Development and debugging utilities for the bluetooth protocol stack

Additionally, @biscotte please check if bluez-obex is installed. It was separated out from bluez and is required for sharing or transferring files via bluetooth. You can use pacman -Ss bluez-obex to see if it is installed.

3 Likes

Hello I didn’t need to use it until now.I could sent a file without before my upgrade.But I’m going to attempt with KDE Connect.

[biscotte@cracotte ~]$ pacman -Ss bluez
extra/bluez 5.73-3 [installé]
    Daemons for the bluetooth protocol stack
extra/bluez-cups 5.73-3
    CUPS printer backend for Bluetooth printers
extra/bluez-deprecated-tools 5.73-3
    Deprecated tools that are no longer maintained
extra/bluez-hid2hci 5.73-3
    Put HID proxying bluetooth HCI's into HCI mode
extra/bluez-libs 5.73-3 [installé]
    Deprecated libraries for the bluetooth protocol stack
extra/bluez-mesh 5.73-3
    Services for bluetooth mesh
extra/bluez-obex 5.73-3
    Object Exchange daemon for sharing content
extra/bluez-qt 6.0.0-1 (kf6) [installé]
    Qt wrapper for Bluez 5 DBus API
extra/bluez-qt5 5.115.0-1 (kf5) [installé]
    Qt wrapper for Bluez 5 DBus API
extra/bluez-tools 0.2.0-5
    A set of tools to manage Bluetooth devices for Linux
extra/bluez-utils 5.73-3 [installé]
    Development and debugging utilities for the bluetooth protocol stack
extra/python-bluepy 1.3.0-9
    Python module for interfacing with Bluetooth LE devices through Bluez
extra/python-pybluez 0.23.r58.g4d46ce1-2
    Python wrapper for the BlueZ Bluetooth stack

I notice I doesn’t have extra/bluez-tools and bluez-obex installed.I install it now.I make an attempt now.

:pray: :pray: You’re the great master :star_struck: It works fine now after installing the obex package
I don’t know why I didn’t think it before I’m stupid It was obvious :sweat: I spent a lot of time about github so I know it better now lol

1 Like

Please mark @misanthrope’s post as solution since their post pointed out the solution.

1 Like

I checked the box “Solution” under his post,isn’t it?

2 Likes

@biscotte You’re not stupid. We all need help and have things to learn. It was separated out in Arch into different packages and it’s easy to miss that in the documentation.

I’m glad it worked! If you ever have problems in the future, try KDE Connect. It’s brilliant and has many other features as well.

Ok I was under Xfce before because of older Pc and slow performance.KDE was too “big” for my system but now, with a recent PC, Kde is powerful and had functionnalities Xfce doesn’t have.
I try Kde connect later when I had to read documentation about it.Thanks for your help and I’m sure we’ll meet again on the forum :vulcan_salute:

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.