Public bug reported:

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 bluetooth.service - Bluetooth 
service...
░░ Subject: A start job for unit bluetooth.service has begun execution
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit bluetooth.service has begun execution.
░░
░░ The job identifier is 2843.
Jan 17 21:23:26 switch (uetoothd)[3245]: ConfigurationDirectory 'bluetooth' 
already exists but the mode is different. (File system: 755 ConfigurationDire>
Jan 17 21:23:26 switch (uetoothd)[3245]: bluetooth.service: Failed to locate 
executable /usr/lib/bluetooth/bluetoothd: No such file or directory
░░ Subject: Process /usr/lib/bluetooth/bluetoothd could not be executed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The process /usr/lib/bluetooth/bluetoothd could not be executed and failed.
░░
░░ The error number returned by this process is ERRNO.
Jan 17 21:23:26 switch (uetoothd)[3245]: bluetooth.service: Failed at step EXEC 
spawning /usr/lib/bluetooth/bluetoothd: No such file or directory

the system service ExecStart location was correctly updated so not sure
what still has the old location

cat /lib/systemd/system/bluetooth.service
[Unit]
Description=Bluetooth service
Documentation=man:bluetoothd(8)
ConditionPathIsDirectory=/sys/class/bluetooth

[Service]
Type=dbus
BusName=org.bluez
ExecStart=/usr/libexec/bluetooth/bluetoothd

** Affects: bluez (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2049708

Title:
  bluez bluetoothd unable to locate executable

Status in bluez package in Ubuntu:
  New

Bug description:
  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 bluetooth.service - Bluetooth 
service...
  ░░ Subject: A start job for unit bluetooth.service has begun execution
  ░░ Defined-By: systemd
  ░░ Support: http://www.ubuntu.com/support
  ░░
  ░░ A start job for unit bluetooth.service has begun execution.
  ░░
  ░░ The job identifier is 2843.
  Jan 17 21:23:26 switch (uetoothd)[3245]: ConfigurationDirectory 'bluetooth' 
already exists but the mode is different. (File system: 755 ConfigurationDire>
  Jan 17 21:23:26 switch (uetoothd)[3245]: bluetooth.service: Failed to locate 
executable /usr/lib/bluetooth/bluetoothd: No such file or directory
  ░░ Subject: Process /usr/lib/bluetooth/bluetoothd could not be executed
  ░░ Defined-By: systemd
  ░░ Support: http://www.ubuntu.com/support
  ░░
  ░░ The process /usr/lib/bluetooth/bluetoothd could not be executed and failed.
  ░░
  ░░ The error number returned by this process is ERRNO.
  Jan 17 21:23:26 switch (uetoothd)[3245]: bluetooth.service: Failed at step 
EXEC spawning /usr/lib/bluetooth/bluetoothd: No such file or directory

  the system service ExecStart location was correctly updated so not
  sure what still has the old location

  cat /lib/systemd/system/bluetooth.service
  [Unit]
  Description=Bluetooth service
  Documentation=man:bluetoothd(8)
  ConditionPathIsDirectory=/sys/class/bluetooth

  [Service]
  Type=dbus
  BusName=org.bluez
  ExecStart=/usr/libexec/bluetooth/bluetoothd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2049708/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to