Starting bluetooth service fails in 15.04

Bug #1449080 reported by Lance DuPre on 2015-04-27
32
This bug affects 7 people
Affects Status Importance Assigned to Milestone
Bluez Utilities
New
Undecided
Unassigned
QtSixA
Undecided
Unassigned
bluez (Ubuntu)
High
Unassigned

Bug Description

This is an upgrade from 14.10 to 15.04 on a laptop using a dell 370 bluetooth minicard. Starting the bluetooth service (4.101-0ubuntu25) produces this error: Job for bluetooth.service failed.

See "systemctl status bluetooth.service" and "journalctl -xe" for details. journalctl -xe shows:
systemd[1]: Unit bluetooth.service entered failed state.
systemd[1]: bluetooth.service failed.
systemd[1]: bluetooth.service holdoff time over, scheduling restart.
systemd[1]: start request repeated too quickly for bluetooth.service
systemd[1]: Failed to start Bluetooth service.

journalctl -u bluetooth shows:

systemd[1]: Starting Bluetooth service...
systemd[2561]: Failed at step EXEC spawning /usr/sbin/bluetoothd: Permission denied
systemd[1]: bluetooth.service: main process exited, code=exited, status=203/EXEC
systemd[1]: Failed to start Bluetooth service.
systemd[1]: UnitApr 27 10:18:10 mobile bluetooth.service entered failed state.
systemd[1]: bluetooth.service failed.

Bluetooth works when the laptop is booted into Windows and worked on 14.10.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: bluetooth 4.101-0ubuntu25
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
Date: Mon Apr 27 10:44:30 2015
InstallationDate: Installed on 2015-03-10 (47 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
InterestingModules: btusb bluetooth
MachineType: Dell Inc. Latitude E6400
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_US
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic root=UUID=dc3060f2-ea09-43a5-912a-45040afffd37 ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: Upgraded to vivid on 2015-04-26 (0 days ago)
dmi.bios.date: 06/04/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A34
dmi.board.name: 0U692R
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA34:bd06/04/2013:svnDellInc.:pnLatitudeE6400:pvr:rvnDellInc.:rn0U692R:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude E6400
dmi.sys.vendor: Dell Inc.
hciconfig:
 hci0: Type: BR/EDR Bus: USB
  BD Address: 70:1A:04:1D:D9:2F ACL MTU: 1021:8 SCO MTU: 64:8
  DOWN
  RX bytes:501 acl:0 sco:0 events:22 errors:0
  TX bytes:329 acl:0 sco:0 commands:22 errors:0

Lance DuPre (duprel1) wrote :
Sebastien Bacher (seb128) wrote :

thank you for your bug report, what's the output of "ls -l /usr/sbin/bluetoothd"?

Salohcin (npsomas) wrote :

Same problem here. Running "ls -l /usr/sbin/bluetoothhd" results in:

-rw-r--r-- 1 root root 946920 Apr 14 03:05 bluetoothd

Subsequently running "sudo chmod 755 /usr/sbin/bluetoothhd" fixes the problem.

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in bluez (Ubuntu):
status: New → Confirmed
Changed in bluez (Ubuntu):
importance: Undecided → High
jooiiee (jooiiee) wrote :

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.

Jeexzee (jeexzee) wrote :

I have found a way to manually start it by typing
sixad --stop
This automaticly started my Bluetooth and now when i type
sixad --start
It starts up and bluetooth stays on. So it might be so simple that sixad starts before the bluetooth service and "chrashes" the service. Someone please check that up.

Download full text (3.6 KiB)

I got it working with this script

sudo chmod +x /usr/sbin/bluetoothd
sudo systemctl start bluetooth.service
sixad --stop
sixad --start

On 1 August 2015 at 16:17, Jeexzee <email address hidden> wrote:

> I have found a way to manually start it by typing
> sixad --stop
> This automaticly started my Bluetooth and now when i type
> sixad --start
> It starts up and bluetooth stays on. So it might be so simple that sixad
> starts before the bluetooth service and "chrashes" the service. Someone
> please check that up.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1449080
>
> Title:
> Starting bluetooth service fails in 15.04
>
> Status in Bluez Utilities:
> New
> Status in QtSixA:
> New
> Status in bluez package in Ubuntu:
> Confirmed
>
> Bug description:
> This is an upgrade from 14.10 to 15.04 on a laptop using a dell 370
> bluetooth minicard. Starting the bluetooth service (4.101-0ubuntu25)
> produces this error: Job for bluetooth.service failed.
>
> See "systemctl status bluetooth.service" and "journalctl -xe" for
> details. journalctl -xe shows:
> systemd[1]: Unit bluetooth.service entered failed state.
> systemd[1]: bluetooth.service failed.
> systemd[1]: bluetooth.service holdoff time over, scheduling restart.
> systemd[1]: start request repeated too quickly for bluetooth.service
> systemd[1]: Failed to start Bluetooth service.
>
> journalctl -u bluetooth shows:
>
> systemd[1]: Starting Bluetooth service...
> systemd[2561]: Failed at step EXEC spawning /usr/sbin/bluetoothd:
> Permission denied
> systemd[1]: bluetooth.service: main process exited, code=exited,
> status=203/EXEC
> systemd[1]: Failed to start Bluetooth service.
> systemd[1]: UnitApr 27 10:18:10 mobile bluetooth.service entered failed
> state.
> systemd[1]: bluetooth.service failed.
>
> Bluetooth works when the laptop is booted into Windows and worked on
> 14.10.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 15.04
> Package: bluetooth 4.101-0ubuntu25
> ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
> Uname: Linux 3.19.0-15-generic x86_64
> NonfreeKernelModules: wl
> ApportVersion: 2.17.2-0ubuntu1
> Architecture: amd64
> Date: Mon Apr 27 10:44:30 2015
> InstallationDate: Installed on 2015-03-10 (47 days ago)
> InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64
> (20141022.1)
> InterestingModules: btusb bluetooth
> MachineType: Dell Inc. Latitude E6400
> PackageArchitecture: all
> ProcEnviron:
> LANGUAGE=en_US
> TERM=xterm
> PATH=(custom, no user)
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic
> root=UUID=dc3060f2-ea09-43a5-912a-45040afffd37 ro quiet splash vt.handoff=7
> SourcePackage: bluez
> UpgradeStatus: Upgraded to vivid on 2015-04-26 (0 days ago)
> dmi.bios.date: 06/04/2013
> dmi.bios.vendor: Dell Inc.
> dmi.bios.version: A34
> dmi.board.name: 0U692R
> dmi.board.vendor: Dell Inc.
> dmi.chassis.type: 8
> dmi.chassis.vendor: Dell Inc.
> dmi.modalias:
> dmi:bvnDellInc.:bvrA34:bd06/04/2013:svnDellInc.:pnLatitudeE6400:...

Read more...

Sebastien Bacher (seb128) wrote :

not a bluez issue if some other service change it to be -x

Changed in bluez (Ubuntu):
status: Confirmed → Invalid
Ville Ranki (ville-ranki) wrote :

Yep, i also had this problem and sixad installed. Workaround in #7 fixed the issue.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers