Found a rouge service (not from the ubuntu distro but instead my custom
nvidia tegra BSP) that had the `/usr/lib/bluetooth/bluetoothd` path in
it.
Closing as removing or altering that service fixes it.
** Changed in: bluez (Ubuntu)
Status: New => Invalid
--
You received this bug
Perhaps try a recursive grep for '/usr/lib/bluetooth/bluetoothd'
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2049708
Title:
bluez bluetoothd unable to locate executable
You are not.
I have rebooted multiple times and continue to get this message in journalctl
(yes it's a new entry on each boot).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
Am I correct in assuming the problem goes away after a reboot?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2049708
Title:
bluez bluetoothd unable to locate executable
5.71-1ubuntu3:
Binary: /usr/libexec/bluetooth/bluetoothd
SystemD: system/bluetooth.service:ExecStart=/usr/libexec/bluetooth/bluetoothd
So that's consistent, but it sounds like you might have encountered an
upgrade bug and your systemd was looking in the old path? I'm guessing
there should be a
** Description changed:
Release: Ubuntu Noble Dev Branch
the location of bluetoothd was just changed to
/usr/libexec/bluetooth/bluetoothd
this causes bluetooth to fail to start since something is still looking
for the old location
Jan 17 21:23:26 switch systemd[1]: Starting
6 matches
Mail list logo
