[Pkg-bluetooth-maintainers] Bug#734548: [Pkg-systemd-maintainers] Bug#734548: unable to start bluetooth service during boot

[Michael Biebl]

Am 11.01.2014 05:32, schrieb Pirate Praveen:
> On Saturday 11 January 2014 12:49 AM, Michael Biebl wrote:
>> Am 10.01.2014 20:09, schrieb Michael Biebl:
>>> Am 08.01.2014 04:34, schrieb Pirate Praveen:
>>>> package: systemd
>>>> version: 204-5
>>>> severity: important
>>>>
>>>> bluetooth service fails to start during boot. Manually starting it after
>>>> boot is working. Attaching journalctl -xb output.
>>>>
>>>> bluetooth service is turned on,
>>>>
>>>> $ sudo chkconfig --list bluetooth
>>>> bluetooth                 0:off  1:off  2:on   3:on   4:on   5:on   6:off
>>>>
>>>> I have only bluetooth keyboard working and every time I have to use
>>>> onscreen keyboard to start bluetooth service.
>>>
>>> Your log file is interesting:
>>>
>>> Jan 08 08:51:48 savannah systemd[1]: Starting Bluetooth.
>>> -- Subject: Unit bluetooth.target has begun with start-up
>>> -- Defined-By: systemd
>>> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
>>>
>>
>> Please also attach the output of
>>
>> udevadm info --query=all
>> --path=/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1:1.0/bluetooth/hci0
>>
>> (make sure it's the correct sysfs path and adjust accordingly)
>>
>> directly after boot when you have *not* run bluetooth service manually
>> and *after* you have (re)started bluetooth service.
>>
> 
> I don't see any difference in output
> 
> ~$ udevadm info --query=all
> --path=/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1:1.0/bluetooth/hci0
> P: /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1:1.0/bluetooth/hci0
> E: DEVPATH=/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1:1.0/bluetooth/hci0
> E: DEVTYPE=host
> E: SUBSYSTEM=bluetooth
> E: SYSTEMD_ALIAS=/sys/subsystem/bluetooth/devices/hci0
> E: SYSTEMD_WANTS=bluetooth.target
> E: TAGS=:systemd:
> E: USEC_INITIALIZED=962357
> 
> pravi at savannah:~$ bt
> [sudo] password for pravi:
> [ ok ] Restarting bluetooth (via systemctl): bluetooth.service.
> pravi at savannah:~$ udevadm info --query=all
> --path=/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1:1.0/bluetooth/hci0
> P: /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1:1.0/bluetooth/hci0
> E: DEVPATH=/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1:1.0/bluetooth/hci0
> E: DEVTYPE=host
> E: SUBSYSTEM=bluetooth
> E: SYSTEMD_ALIAS=/sys/subsystem/bluetooth/devices/hci0
> E: SYSTEMD_WANTS=bluetooth.target
> E: TAGS=:systemd:
> E: USEC_INITIALIZED=962357

This all looks fine, so far.

Could you please reboot the system and provide the output of
journalctl -xb and
systemctl status bluetooth.service bluetooth.target
systemctl show bluetooth.service bluetooth.target
*before* you manually (re)start the service.

This should give us a clue if bluetooth.service wasn't started at all or
if the service was started by bluetoohd died for some reason.



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 899 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-bluetooth-maintainers/attachments/20140112/d8ecf35d/attachment.sig>