Enable D-Bus activation of bluetooth.service
cover Enable D-Bus activation of bluetooth.service
D-Bus can automatically launch programs on demand when a message is sent to their bus name. Bluez provides src/org.bluez.service for this purpose, but it writes "dbus-org.bluez.service" for the Systemd service name, while the Systemd service is actually named bluetooth.service (generated from src/bluetooth.service.in). The Systemd service defines an alias named dbus-org.bluez.service, but Systemd aliases only come into effect once a unit is enabled.
Effectively, this means that instead of launching bluetoothd on demand whenever it's requested, D-Bus activation is only used if the service is enabled but happens to not be running, such as the first time it's enabled or if it crashes.
Grant Moyer (1):
org.bluez.service: enable D-Bus activation of bluetooth.service
src/org.bluez.service | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
base-commit: 61a2b3d93897b04fb921a4fb229c0831d13807a8
Signature · 1 line
2.55.0
PATCH 1/1 org.bluez.service: enable D-Bus activation of bluetooth.service
D-Bus was configured to activate dbus-org.bluez.service, which is only an alias for bluetooth.service, and so isn't resolvable unless the service is already enabled. This means D-Bus cannot launch bluetoothd on demand in most cases (for example when running bluetootctl without the bluetoothd systemd unit configured to run at startup). This changes the D-Bus configuration to activate bluetooth.service itself, so that bluetoothd can be launched by D-Bus on demand.
--- src/org.bluez.service | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
src/org.bluez.service +1 -1
@@ -2,4 +2,4 @@ Name=org.bluez Exec=/bin/false User=root -SystemdService=dbus-org.bluez.service +SystemdService=bluetooth.service
Signature · 1 line
2.55.0
Re: [PATCH BlueZ 1/1] org.bluez.service: enable D-Bus activation of bluetooth.service
Quoted 9 lines · Grant Moyer
D-Bus was configured to activate dbus-org.bluez.service, which is only
an alias for bluetooth.service, and so isn't resolvable unless the service is already enabled. This means D-Bus cannot launch bluetoothd on demand in most cases (for example when running bluetootctl without the bluetoothd systemd unit configured to run at startup). This changes
the D-Bus configuration to activate bluetooth.service itself, so that bluetoothd can be launched by D-Bus on demand.
Which would mean that bluetoothd would get started on system where it is disabled, but somebody runs bluetoothctl as you mention?
Then that's a no. We do not want bluetoothd to get started unless the system configuration says that bluetooth.service is enabled. Otherwise it effectively makes it impossible to disable bluez without uninstalling bluez, which is very very complicated for integrated desktops.
Quoted 14 lines
---
src/org.bluez.service | 2 +-1 file changed, 1 insertion(+), 1 deletion(-)src/org.bluez.service +0
-0@@ -2,4 +2,4 @@Name=org.bluez
Exec=/bin/false
User=rootsrc/org.bluez.service +1
-1-SystemdService=dbus-org.bluez.service +SystemdService=bluetooth.service
This is automated email and please do not reply to this email!
Dear submitter,
Thank you for submitting the patches to the linux bluetooth mailing list. This is a CI test results with your patch series:
PW Link:https://patchwork.kernel.org/series/1163256/
---Test result---
Test Summary:
CheckPatch PASS 0.42 seconds GitLint PASS 0.32 seconds BuildEll PASS 20.00 seconds BluezMake PASS 380.72 seconds CheckSmatch PASS 296.26 seconds bluezmakeextell PASS 95.41 seconds IncrementalBuild PASS 383.42 seconds ScanBuild PASS 1141.33 seconds
https://github.com/bluez/bluez/pull/2520
---
Regards,
Linux Bluetooth
This is an automated email and please do not reply to this email.
Dear Submitter,
This series was picked up by the CI more than 2 weeks ago and the pull request created for it is still open, which means the series was never applied to the tree.
Series: Enable D-Bus activation of bluetooth.service
Pull Request: https://github.com/bluez/bluez/pull/2520
Created: 2026-09-11 23:16:16+00:00
The pull request has been closed and no further action is taken on this series.
If the change should still be considered, it must be resent to the Linux Bluetooth mailing list ([email protected]) so that it is picked up again.
---
Regards,
Linux Bluetooth