Comment 5 for bug 1449080

This seems to be related to the package sixad

When sixad is installed, it will autostart and it removes execution permissions on /usr/sbin/bluetoothd on start. This prevents bluetooth.service from starting.

-- Unit bluetooth.service has begun starting up.
jul 16 21:17:56 mainframe systemd[5337]: Failed at step EXEC spawning /usr/sbin/bluetoothd: Permission denied
-- Subject: Process /usr/sbin/bluetoothd could not be executed

johan@mainframe:~$ ls -la /usr/sbin/bluetoothd
-rw-r--r-- 1 root root 946920 apr 13 19:05 /usr/sbin/bluetoothd

If I manually set execute permissions on /usr/sbin/bluetoothd bluetooth.service will start properly but will fail at next reboot. I can start and stop the service as many times as I want to, but when I start sixad (sixad --start) it will remove execution permission on /usr/sbin/bluetoothd causing bluetooth.service to fail.

I have not yet found a solution to this.