Arch Linux

cosmicqueenmari

Member

Registered: 2026-05-17

Posts: 2

org.bluez activation request failed

Hello.
I installed this program: https://johnoberhauser.github.io/OkShell/
when I try to start it in the terminal by typing okshell, this is the result.

2026-05-17T16:54:16.348040Z  INFO okshell_core: Welcome to OkShell!
2026-05-17T16:54:16.348109Z  INFO okshell_config::config_manager: Creating new ConfigManager
2026-05-17T16:54:16.350203Z  INFO okshell_services: Initializing services...
Error: dbus error: org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer 'org.bluez': activation request failed: unknown unit

Caused by:
    org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer 'org.bluez': activation request failed: unknown unit

Does anyone know how to solve this?
Thank you in advance

5hridhyan

Member

Registered: 2025-12-25

Posts: 792

Re: org.bluez activation request failed

BlueZ/Bluetooth not running/installed?
try installing https://archlinux.org/packages/extra/x86_64/bluez/ providing the Bluetooth protocol stack and *if you want, install  https://archlinux.org/packages/extra/x8 … uez-utils/ package, which provides the bluetoothctl utility.

And start/enable the services

Last edited by 5hridhyan (2026-05-17 17:11:59)

cosmicqueenmari

Member

Registered: 2026-05-17

Posts: 2

Re: org.bluez activation request failed

Your solution worked to get rid of that error, thank you. Now when i try to start okshell again, this is what i get. should i make a new post for this error?

2026-05-17T17:15:54.652261Z  INFO okshell_core: Welcome to OkShell!
2026-05-17T17:15:54.652369Z  INFO okshell_config::config_manager: Creating new ConfigManager
2026-05-17T17:15:54.656549Z  INFO okshell_services: Initializing services...
Error: cannot initialize notification service: cannot acquire D-Bus name 'org.freedesktop.Notifications': name already taken on the bus

5hridhyan

Member

Registered: 2025-12-25

Posts: 792

Re: org.bluez activation request failed

should i make a new post for this error?

No, this is still related. You can update the thread title if needed.

about the error, it just means a notification daemon is already running and owns org.freedesktop.Notifications, so OkShell can’t start its own
You can either:
- disable/stop your current notification daemon, or
- check if OkShell has an option to disable its notification service in it's *config

Edit:
also please use [code][/code] tags, and edit your posts in this regard

Last edited by 5hridhyan (2026-05-17 17:33:46)