Bug 6356

Summary: No bluetooth device created
Product: Mageia Reporter: Guillaume Rousse <guillomovitch>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED INVALID QA Contact:
Severity: normal    
Priority: Normal    
Version: Cauldron   
Target Milestone: ---   
Hardware: i586   
OS: Linux   
Whiteboard:
Source RPM: bluez, systemd or dbus CVE:
Status comment:

Description Guillaume Rousse 2012-06-06 20:33:29 CEST
I'm unable to use bluetooth for anything. It seems the device file itself is missing:

[root@beria guillaume]# hcitool scan 
Device is not available: No such device

Using systemd bluetooth service is useless:
[root@beria guillaume]# systemctl status  bluetooth.service
bluetooth.service - Bluetooth Manager
	  Loaded: loaded (/lib/systemd/system/bluetooth.service; disabled)
	  Active: inactive (dead)
	  CGroup: name=systemd:/system/bluetooth.service

[root@beria guillaume]# systemctl start  bluetooth.service
[root@beria guillaume]# systemctl status  bluetooth.service
bluetooth.service - Bluetooth Manager
	  Loaded: loaded (/lib/systemd/system/bluetooth.service; disabled)
	  Active: active (running) since Wed, 06 Jun 2012 20:25:46 +0200; 1s ago
	Main PID: 3841 (bluetoothd)
	  CGroup: name=systemd:/system/bluetooth.service
		  รข 3841 /usr/sbin/bluetoothd -n

Jun 06 20:25:45 beria bluetoothd[3841]: Bluetooth daemon 4.99
Jun 06 20:25:46 beria bluetoothd[3841]: Starting SDP server
[root@beria guillaume]# hcitool scan 
Device is not available: No such device

systemd complains about a missing dbus-org.bluez.service:
Jun  6 20:25:26 localhost dbus-daemon[1949]: dbus[1949]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details.

[root@beria guillaume]# systemctl status dbus-org.bluez.servicedbus-org.bluez.service
	  Loaded: error (Reason: No such file or directory)
	  Active: inactive (dead)

This service is defined in /usr/share/dbus-1/system-services/org.bluez.service file:
[D-BUS Service]
Name=org.bluez
Exec=/bin/false
User=root
SystemdService=dbus-org.bluez.service

With udev in debug mode, turning the hardware switch on doesn't show any trace of bluetooth device creation:
Jun  6 20:30:59 localhost udevd[6109]: seq 2088 running
Jun  6 20:30:59 localhost udevd[6109]: device 0x21ac5c0 has devpath '/devices/pci0000:00/0000:00:1a.0/usb1/1-2'
Jun  6 20:30:59 localhost udevd[6109]: no db file to read /run/udev/data/c189:4: No such file or directory
Jun  6 20:30:59 localhost udevd[6109]: IMPORT builtin 'usb_id' /lib/udev/rules.d/40-libgphoto2.rules:11
Jun  6 20:30:59 localhost kernel: [  420.985183] hub 1-2:1.0: USB hub found
Jun  6 20:30:59 localhost udevd[332]: seq 2089 queued, 'add' 'usb'
Jun  6 20:30:59 localhost kernel: [  420.987109] hub 1-2:1.0: 3 ports detected
Jun  6 20:30:59 localhost udevd[6109]: ID_VENDOR=Broadcom
Jun  6 20:30:59 localhost udevd[6109]: ID_VENDOR_ENC=Broadcom
Jun  6 20:30:59 localhost udevd[6109]: ID_VENDOR_ID=0a5c
Jun  6 20:30:59 localhost udevd[6109]: ID_MODEL=BCM2046B1
Jun  6 20:30:59 localhost udevd[6109]: ID_MODEL_ENC=BCM2046B1
Jun  6 20:30:59 localhost udevd[6109]: ID_MODEL_ID=4500
Jun  6 20:30:59 localhost udevd[6109]: ID_REVISION=0100
Jun  6 20:30:59 localhost udevd[6109]: ID_SERIAL=Broadcom_BCM2046B1
Jun  6 20:30:59 localhost udevd[6109]: ID_BUS=usb
Jun  6 20:30:59 localhost udevd[6109]: ID_USB_INTERFACES=:090000:
Jun  6 20:30:59 localhost udevd[6109]: device 0x21b43c0 has devpath '/devices/pci0000:00/0000:00:1a.0/usb1'
Jun  6 20:30:59 localhost udevd[6109]: device 0x21b1e80 has devpath '/devices/pci0000:00/0000:00:1a.0'
Jun  6 20:30:59 localhost udevd[6109]: device 0x21b25b0 has devpath '/devices/pci0000:00'
Jun  6 20:30:59 localhost udevd[6109]: MODE 0664 /lib/udev/rules.d/50-udev-default.rules:55
Jun  6 20:30:59 localhost udevd[6109]: IMPORT builtin skip 'usb_id' /lib/udev/rules.d/50-udev-default.rules:56
Jun  6 20:30:59 localhost udevd[6109]: IMPORT '/bin/bash -c '[ -f /dev/.in_sysinit ] && echo in_sysinit=1 || :'' /lib/udev/rules.d/65-md-incremental.rules:8
Jun  6 20:30:59 localhost udevd[6216]: starting '/bin/bash -c '[ -f /dev/.in_sysinit ] && echo in_sysinit=1 || :''
Jun  6 20:30:59 localhost udevd[6109]: '/bin/bash -c '[ -f /dev/.in_sysinit ] && echo in_sysinit=1 || :'' [6216] exit with return code 0
Jun  6 20:30:59 localhost udevd[6109]: IMPORT builtin 'path_id' /lib/udev/rules.d/71-seat.rules:22
Jun  6 20:30:59 localhost udevd[6109]: ID_PATH=pci-0000:00:1a.0-usb-0:2
Jun  6 20:30:59 localhost udevd[6109]: ID_PATH_TAG=pci-0000_00_1a_0-usb-0_2
Jun  6 20:30:59 localhost udevd[6109]: device 0x21b43c0 filled with db file data
Jun  6 20:30:59 localhost udevd[6109]: RUN '/usr/share/virtualbox/VBoxCreateUSBNode.sh $major $minor $attr{bDeviceClass} vboxusers' /etc/udev/rules.d/virtualbox.rules:3
Jun  6 20:30:59 localhost udevd[6109]: handling device node '/dev/bus/usb/001/005', devnum=c189:4, mode=0664, uid=0, gid=0
Jun  6 20:30:59 localhost udevd[6109]: set permissions /dev/bus/usb/001/005, 020664, uid=0, gid=0
Jun  6 20:30:59 localhost udevd[6109]: creating symlink '/dev/char/189:4' to '../bus/usb/001/005'
Jun  6 20:30:59 localhost udevd[6109]: created db file '/run/udev/data/c189:4' for '/devices/pci0000:00/0000:00:1a.0/usb1/1-2'
Jun  6 20:30:59 localhost udevd[6217]: starting '/usr/share/virtualbox/VBoxCreateUSBNode.sh 189 4 09 vboxusers'
Jun  6 20:30:59 localhost udevd[6109]: '/usr/share/virtualbox/VBoxCreateUSBNode.sh 189 4 09 vboxusers' [6217] exit with return code 0
Jun  6 20:30:59 localhost udevd[6109]: passed -1 bytes to netlink monitor 0x21c30a0
Jun  6 20:30:59 localhost udevd[6109]: seq 2088 processed with 0
Comment 1 Manuel Hiebel 2012-06-10 22:29:57 CEST
I have something similar to this bug, and if I install bluez-hid2hci it works
Comment 2 Guillaume Rousse 2012-06-11 19:47:23 CEST
Same for me. If this stuff is really needed to make any kind of bluetooth adapter works, its description ought to be a little more adapted, as it seems to be a keyboard/mouse stuff currently.
Comment 3 Guillaume Rousse 2013-02-07 23:24:15 CET
Indeed, bluez-hid2hci is needed for any kind of bluetooth usage. The package description, altough a bit technical, is correct here: default bluetooth access mode emulates an USB transparency layer for direct mouse/keyboard usage, and need to be switched back to HCI mode for any other usage.

Status: NEW => RESOLVED
Resolution: (none) => INVALID