Unfortunately a bluetooth-66serv service file doesn't exist yet. Although I don't have experience with it myself, I tried once doing something with an old phone and bt dongle and failed. see if bluetoothctl --help will help you. Sort of running the service manually without 66 supervising the service.

Otherwise be patient for a more knowledgeable person to offer a solution, or write up a service file for it.

Hi udo and welcome.

Thx for the report. The service has not been updated to the testing repository. It will be available in few hours.

bluetoothd-66serv is available in observice-testing repository.

pacman -Sy bluetoothd-66serv

I do not have any bluetooth devices to test if everything works as expected, plz report a problem in the Bug report section of the forum.

Thx

I just noticed that bluetoothd-66serv-0.1.2-1-x86_64.pkg.tar.xz is obsolete because it did not track changes made by the update of bluez-5.50-7-x86_64.pkg.tar.xz (/usr/lib/bluetooth/bluetoothd) to bluez-5.51-3-x86_64.pkg.tar.xz (/usr/libexec/bluetooth/bluetoothd). Besides, I think the new version of the package should include starting obexd, as was the case with bluetoothd-s6serv-0.2-1-x86_64.pkg.tar.xz, which worked properly. Thanks.

I think, before anyone else verifies, you can copy
# cp /usr/lib/66/service/bluetoothd /etc/66/service/
# $edit (nano/vi/..etc) /etc/66/service/bluetoothd

and go to the execute line and switch
/usr/lib/bluetooth/bluetoothd to /usr/libexec/bluetooth/bluetoothd

then 66-enable the bluetoothd service
If you have done it already and it didn't run, disable it from the tree and enable it again, or use the -c option and -S to start it again.
Use the -v3 option and then run # 66-inservice -p30 to see its log

Edit: I don't have a bt thingy here to test if it works

I already tried that, it not worked ... if it would be of a help, this was thrown ...

 ~ % sudo 66-inservice bluetoothd
Name               : bluetoothd
In tree            : root
Status             : enabled, down (exitcode 1) 0 seconds, normally up, want up, ready 0 seconds
Type               : classic
Description        : bluetooth daemon
Source             : /etc/66/service/bluetoothd
Live               : /run/66/scandir/0/bluetoothd
Depends on         : bluetoothd-log
Start script       : 
                      execl-cmdline -s { /usr/libexec/bluetooth/bluetoothd ${cmd_args} -f ${conf_dir}/${conf_file} } 
Stop script        : nothing to display
Environment source : /etc/66/conf/bluetoothd
Environment file   : cmd_args=!-n
                     conf_dir=!/etc/bluetooth
                     conf_file=!main.conf
Log name           : bluetoothd-log
Log destination    : /var/log/66/bluetoothd
Log file           :
@ 400000005dd56f6612a90e56 bluetoothd[3042]: Unable to get on D-Bus
@ 400000005dd56f671279459c bluetoothd[3053]: Bluetooth daemon 5.52
@ 400000005dd56f6712b07ebb D-Bus setup failed: Connection ":1.269" is not allowed to own the service "org.bluez" due to security policies in the configuration file

dumb question: Is dbus running in a root tree?
because I run /usr/libexec/bluetooth/bluetoothd -n and I get the same error because I don't use dbus, haven't for a long while :)
But have no bluez device but that would be an error of further than dbus
# 66-enable -S dbus

... obviously ... yes

 ~ % sudo 66-intree root
Name        : root
Initialized : yes
Enabled     : yes
Current     : yes
Contents    : crond-log  connmand-log  dbus-log  dbus  connmand  tty@ tty1
              openntpd-log  openntpd  wpa_supplicant-log  wpa_supplicant  crond
              tty@ tty2  bluetoothd-log  bluetoothd

Many thanks for the report
Please sync and update. Also bluetoothd-66serv contain now obexd as user service.

... thanks, but still there is problem with starting bluetooth daemon ... obexd is up, though

 ~ % sudo 66-inservice bluetoothd
Name               : bluetoothd
In tree            : root
Status             : enabled, down (exitcode 1) 0 seconds, normally up, want up, ready 0 seconds
Type               : classic
Description        : bluetooth daemon
Source             : /usr/lib/66/service/bluetoothd
Live               : /run/66/scandir/0/bluetoothd
Depends on         : bluetoothd-log
Start script       : 
                      execl-cmdline -s { /usr/libexec/bluetooth/bluetoothd ${cmd_args} -f ${conf_dir}/${conf_file} } 
Stop script        : nothing to display
Environment source : /etc/66/conf/bluetoothd
Environment file   : cmd_args=!-n
                     conf_dir=!/etc/bluetooth
                     conf_file=!main.conf
Log name           : bluetoothd-log
Log destination    : /var/log/66/bluetoothd
Log file           :
@ 400000005dd64f7a36f4ee86 bluetoothd[1884]: Unable to get on D-Bus
@ 400000005dd64f7b36dfa8d8 bluetoothd[1894]: Bluetooth daemon 5.52
@ 400000005dd64f7b36f85e8d D-Bus setup failed: Connection ":1.161" is not allowed to own the service "org.bluez" due to security policies in the configuration file

 ~ % 66-inservice obexd
Name               : obexd
In tree            : graphics
Status             : enabled, up (pid 1028) 8 seconds
Type               : classic
Description        : obex daemon
Source             : /usr/lib/66/service/obexd
Live               : /run/66/scandir/1000/obexd
Depends on         : obexd-log
Start script       : 
                      execl-cmdline -s { /usr/libexec/bluetooth/obexd ${cmd_args} } 
Stop script        : nothing to display
Environment source : /home/qwe/.66/conf/obexd
Environment file   : cmd_args=!-n
Log name           : obexd-log
Log destination    : /home/qwe/.66/log/obexd
Log file           :
@ 400000005dd64f453459170f obexd[899]: OBEX daemon 5.52
@ 400000005dd64f4534592589 Failed to connect to socket /run/user/1000/dbus: No such file or directory
@ 400000005dd64f45345928e6 obexd[899]: manager_init failed

have you udpated the bluez package?
Anyway be sure to have /usr/share/dbus-1/system.d/{bluetooth,bluetooth-mesh}.conf file. The previous packages installed those files at the wrong place meaning /usr/share/dbus-1/dbus-1/system.d/{bluetooth,bluetooth-mesh}.conf.

Please check it out.

Can you give this guy a hand on how to create his own service file for tlp (next thread on 66)

Fungal, I suppose that was once a link to another post?

I'm back with more Bluetooth fun...
I'm currently back at my mexican workstation. My NIC is an Intel Dual AC wireless 7260 mini-PCIe. These intel combined cards are sort of notorious for having issues over several generations. I've never had the need to use Bluetooth on this machine before so I didn't bother. I bought myself some bluetooth speakers though and would like to use them with my Obarun.

So what's the exact problem?
The bluetooth portion of the card is simply not recognized in Obarun. Also Plasma shows no available devices in its settings.

What packages are installed, what services running?
bluez, bluez-libs, bluez-utils, bluez-qt, bluedevil (plasma), qt5-connectivity (optional[?])
bluetoothd-66serv is enabled and running in a root user tree but actually bails in the log:

marian@ obarun [111] ~ % sudo 66-inservice bluetoothd
Name                  : bluetoothd
Version               : 0.2.1
In tree               : desktop
Status                : enabled, down (exitcode 127) 0 seconds, normally up, want up, ready 0 seconds
Type                  : classic
Description           : bluetooth daemon
Source                : /usr/lib/66/service/bluetoothd
Live                  : /run/66/scandir/0/bluetoothd
Dependencies          : bluetoothd-log
External dependencies : None
Optional dependencies : None
Start script          :  execl-cmdline -s { /usr/lib/bluetooth/bluetoothd ${cmd_args} -f ${conf_file} } 
Stop script           : None
Environment source    : /etc/66/conf/bluetoothd
Environment file      : cmd_args=!-n
                        conf_file=!/etc/bluetooth/main.conf
Log name              : bluetoothd-log
Log destination       : /var/log/66/bluetoothd
Log file              : 
2020-06-02 14:22:40.518863630  execl-cmdline: fatal: unable to exec /usr/lib/bluetooth/bluetoothd: No such file or directory
2020-06-02 14:22:41.519596540  execl-cmdline: fatal: unable to exec /usr/lib/bluetooth/bluetoothd: No such file or directory
2020-06-02 14:22:42.518570036  execl-cmdline: fatal: unable to exec /usr/lib/bluetooth/bluetoothd: No such file or directory
2020-06-02 14:22:43.522248264  execl-cmdline: fatal: unable to exec /usr/lib/bluetooth/bluetoothd: No such file or directory
2020-06-02 14:22:44.522330128  execl-cmdline: fatal: unable to exec /usr/lib/bluetooth/bluetoothd: No such file or directory
2020-06-02 14:22:45.522682920  execl-cmdline: fatal: unable to exec /usr/lib/bluetooth/bluetoothd: No such file or directory
2020-06-02 14:22:46.523987885  execl-cmdline: fatal: unable to exec /usr/lib/bluetooth/bluetoothd: No such file or directory
2020-06-02 14:22:47.525272197  execl-cmdline: fatal: unable to exec /usr/lib/bluetooth/bluetoothd: No such file or directory
2020-06-02 14:22:48.526387686  execl-cmdline: fatal: unable to exec /usr/lib/bluetooth/bluetoothd: No such file or directory
2020-06-02 14:22:49.528144026  execl-cmdline: fatal: unable to exec /usr/lib/bluetooth/bluetoothd: No such file or directory
2020-06-02 14:22:50.528217514  execl-cmdline: fatal: unable to exec /usr/lib/bluetooth/bluetoothd: No such file or directory
2020-06-02 14:22:51.529249478  execl-cmdline: fatal: unable to exec /usr/lib/bluetooth/bluetoothd: No such file or directory
2020-06-02 14:22:52.529177465  execl-cmdline: fatal: unable to exec /usr/lib/bluetooth/bluetoothd: No such file or directory
2020-06-02 14:22:53.532769161  execl-cmdline: fatal: unable to exec /usr/lib/bluetooth/bluetoothd: No such file or directory
2020-06-02 14:22:54.533084767  execl-cmdline: fatal: unable to exec /usr/lib/bluetooth/bluetoothd: No such file or directory
2020-06-02 14:22:55.536031566  execl-cmdline: fatal: unable to exec /usr/lib/bluetooth/bluetoothd: No such file or directory
2020-06-02 14:22:56.537250929  execl-cmdline: fatal: unable to exec /usr/lib/bluetooth/bluetoothd: No such file or directory
2020-06-02 14:22:57.536417413  execl-cmdline: fatal: unable to exec /usr/lib/bluetooth/bluetoothd: No such file or directory

Ok. That's pretty clear. But WHY?
I indeed miss this path completely. There's not even any /usr/lib/bluetooth parent directory on my install. Furthermore the only entries in /usr/lib regarding Bluetooth is the libbluetooth.so.3.19.2* socket and it's corresponding symbolic links. I can install the mentioned packages any times I want. It won't get created either.

rfkill recognizes the device:

marian@ obarun ~ % rfkill
ID TYPE      DEVICE      SOFT      HARD
 0 wlan      phy0   unblocked unblocked
 1 bluetooth hci0   unblocked unblocked

so does the kernel apparently:

marian@ obarun [127] ~ % dmesg | grep Bluetooth
[    6.824423] Bluetooth: Core ver 2.22
[    6.824531] Bluetooth: HCI device and connection manager initialized
[    6.824535] Bluetooth: HCI socket layer initialized
[    6.824536] Bluetooth: L2CAP socket layer initialized
[    6.824539] Bluetooth: SCO socket layer initialized
[    6.853569] Bluetooth: hci0: read Intel version: 3707100180012d0d2a
[    6.853570] Bluetooth: hci0: Intel device is already patched. patch num: 2a

so does bluez-utils:

marian@ obarun ~ % btmgmt
[mgmt]# info
Index list with 1 item
hci0:   Primary controller
        addr 7C:5C:F8:6E:50:AE version 6 manufacturer 2 class 0x000000
        supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr hs le advertising secure-conn debug-keys privacy configuration static-addr 
        current settings: br/edr 
        name Bluemoon Universal Bluetooth Host Controller
        short name 
hci0:   Configuration options
        supported options: public-address 
        missing options:

Necessary kernel modules seem to be loaded:

marian@ obarun ~ % lsmod | grep blue           
bluetooth             696320  5 btrtl,btintel,btbcm,btusb
ecdh_generic           16384  1 bluetooth
rfkill                 28672  6 bluetooth,cfg80211
crc16                  16384  2 bluetooth,ext4

(Although it sort of throws me off that bluetooth says "btintel". Intel states that iwlwifi is the driver responsible for these cards?)

When I issue "bluetoothctl" from bluez-utils the command will indefinitely try to connect to bluetoothd (surprise surprise, no bluetoothd there to begin with...)

I'm currently dual booting with Windows and have read concerns that Windows can sort of kidnap the MAC of a hardware device. But from all the output I seriously doubt that is the case here. The issue seems to be the missing /usr/lib/bluetooth directory. Also many people advice to disable co-existence of Bluetooth and WIFI on these cards with a iwlwifi module option which didn't work either.
On YouTube people mask out(!) between one and three pins on the NIC itself to get it discovered...(although several of those have this issue even on Windows and my Windows installation detects the card fine and works out of the box.)


Any idea why /usr/lib/bluetooth might be missing? Am I missing packages? I've read that people of similar Intel cards install bluez-utils-compat from AUR instead of bluez-utils from official repos to get it to work, but that has a systemd dependency...

Any idea why /usr/lib/bluetooth might be missing?

just because the dev is a stupid guy :p.

Well Arch push libexec stuff to /usr/lib which is clearly a bad behavior. libexec thing should be on, well, /usr/libexec. So, when i found some stuff like this, i change the path to the correct one. So, on Obarun, bluez package install obexd,bluetoothd,bluetooth-meshd at /usr/libexec/bluetooth directory.
Ok, but when i did the service, i used the /usr/lib path instead of /usr/libexec lol.

So, just synchronize the observice repo, install the new version of bleutoothd-66serv(0.2.2-1) and enable it again.

Fabulous! Works.
Thank you very much for another explanation and quick fix!

Hello Eric,

Ever since the instalation of bluetooth-66serv 0.1.3 ( now 0.2.1 in charge , didn't update to 0.2.2, yet ), everything works flawlessly, despite obvious errors in packages 0.2.0 and 0.2.1, which I didn't noticed.

[main]
@ type = classic
@ version = 0.2.1
@ description = "bluetooth daemon"
@ user = ( root )
@ options = ( log env )

[start]
@ build = auto
@ execute = ( execl-cmdline -s { /usr/lib/bluetooth/bluetoothd ${cmd_args} -f ${conf_file} } )

[environment]
cmd_args=!-n
conf_file=!/etc/bluetooth/main.conf

... using bluetoothd service file, 66 produce this ...

~ % sudo 66-inservice bluetoothd
Name                  : bluetoothd
Version               : None
In tree               : root
Status                : enabled, up (pid 873) 139 seconds
Type                  : classic
Description           : bluetooth daemon
Source                : /usr/lib/66/service/bluetoothd
Live                  : /run/66/scandir/0/bluetoothd
Dependencies          : bluetoothd-log
External dependencies : None
Optional dependencies : None
Start script          : 
                         execl-cmdline -s { /usr/libexec/bluetooth/bluetoothd ${cmd_args} -f ${conf_dir}/${conf_file} } 
Stop script           : None
Environment source    : /etc/66/conf/bluetoothd
Environment file      : cmd_args=!-n
                        conf_dir=!/etc/bluetooth
                        conf_file=!main.conf
Log name              : bluetoothd-log
Log destination       : /var/log/66/bluetoothd
Log file              : 
2020-06-03 19:46:41.033882558  bluetoothd[806]: Unable to get on D-Bus
2020-06-03 19:46:41.998008139  bluetoothd[857]: Bluetooth daemon 5.54
2020-06-03 19:46:42.004368463  bluetoothd[857]: Starting SDP server
2020-06-03 19:46:42.013141031  bluetoothd[857]: Bluetooth management interface 1.15 initialized
2020-06-03 20:11:59.614700843  bluetoothd[857]: Unable to get io data for Object Push: getpeername: Transport endpoint is not connected (107)
2020-06-03 20:31:42.085234096  bluetoothd[857]: Unable to get io data for Object Push: getpeername: Transport endpoint is not connected (107)
2020-06-03 21:51:52.257271347  bluetoothd[857]: Disconnected from D-Bus. Exiting.
2020-06-03 21:51:52.270763633  bluetoothd[857]: Stopping SDP server
2020-06-03 21:51:52.270876448  bluetoothd[857]: Exit
2020-06-03 21:51:52.391631171  bluetoothd[11110]: Bluetooth daemon 5.54
2020-06-03 21:51:52.395117429  D-Bus setup failed: Failed to connect to socket /run/dbus/system_bus_socket: Connection refused
2020-06-03 21:51:52.395294706  bluetoothd[11110]: Unable to get on D-Bus
2020-06-04 05:58:13.232062913  bluetoothd[826]: Bluetooth daemon 5.54
2020-06-04 05:58:13.235627394  D-Bus setup failed: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
2020-06-04 05:58:13.235634402  bluetoothd[826]: Unable to get on D-Bus
2020-06-04 05:58:14.199702727  bluetoothd[873]: Bluetooth daemon 5.54
2020-06-04 05:58:14.206018873  bluetoothd[873]: Starting SDP server
2020-06-04 05:58:14.215080803  bluetoothd[873]: Bluetooth management interface 1.15 initialized

The only explanation that came to my mind is that changes didn't touched database, which still keep correct start script from package 0.1.3.

Could you, please, help me to fix it, even it is not broken ... and bring it in expected state, when it will be broken.

P.S. Note that instead of package version number it show: None

installing the service doesn't mean that you running service is changed. The installation just overwrite the corresponding frontend file at /usr/lib/66/service. But if you don't enable again the service you still use the version that you used previously. 66 will not take policies decision for you and it will not do "magical stuff" for you. We are not on systemd here :).

So, install the last version of bluetoothd-66serv package then update your service:

# 66-enable -F -t root bluetoothd

finally reload it in memory

# 66-start -R -t root bluetoothd

it should be ok.