Bug#734548: [Pkg-systemd-maintainers] Bug#734548: unable to start bluetooth service during boot
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/pci:00/: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/pci:00/:00:1a.0/usb1/1-1/1-1:1.0/bluetooth/hci0 P: /devices/pci:00/:00:1a.0/usb1/1-1/1-1:1.0/bluetooth/hci0 E: DEVPATH=/devices/pci:00/: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@savannah:~$ bt [sudo] password for pravi: [ ok ] Restarting bluetooth (via systemctl): bluetooth.service. pravi@savannah:~$ udevadm info --query=all --path=/sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1:1.0/bluetooth/hci0 P: /devices/pci:00/:00:1a.0/usb1/1-1/1-1:1.0/bluetooth/hci0 E: DEVPATH=/devices/pci:00/: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? signature.asc Description: OpenPGP digital signature
Bug#734548: [Pkg-systemd-maintainers] Bug#734548: unable to start bluetooth service during boot
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
--
-- Unit bluetooth.target has begun starting up.
Jan 08 08:51:48 savannah systemd[1]: Reached target Bluetooth.
-- Subject: Unit bluetooth.target has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit bluetooth.target has finished starting up.
So, bluetooth.target seems to be started properly. It's a target which
is activated whenever a bluetooth device is added and triggered via
/lib/udev/rules.d/99-systemd.rules:
SUBSYSTEM==bluetooth, TAG+=systemd,
ENV{SYSTEMD_WANTS}+=bluetooth.target
Yet bluetooth.service is *not* started apparently.
Can you post the output of
# ls -al /etc/systemd/system/bluetooth.target.wants/
It should look like:
lrwxrwxrwx. 1 root root 37 Feb 18 2013 bluetooth.service -
/lib/systemd/system/bluetooth.service
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
Bug#734548: [Pkg-systemd-maintainers] Bug#734548: unable to start bluetooth service during boot
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/pci:00/: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. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#734548: [Pkg-systemd-maintainers] Bug#734548: unable to start bluetooth service during boot
On Saturday 11 January 2014 12:39 AM, Michael Biebl wrote: Can you post the output of # ls -al /etc/systemd/system/bluetooth.target.wants/ It is same. ~$ ls -al /etc/systemd/system/bluetooth.target.wants/ total 8 drwxr-xr-x 2 root root 4096 Jun 15 2013 . drwxr-xr-x 8 root root 4096 Jan 10 00:29 .. lrwxrwxrwx 1 root root 37 Jun 15 2013 bluetooth.service - /lib/systemd/system/bluetooth.service signature.asc Description: OpenPGP digital signature
Bug#734548: [Pkg-systemd-maintainers] Bug#734548: unable to start bluetooth service during boot
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/pci:00/: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/pci:00/:00:1a.0/usb1/1-1/1-1:1.0/bluetooth/hci0 P: /devices/pci:00/:00:1a.0/usb1/1-1/1-1:1.0/bluetooth/hci0 E: DEVPATH=/devices/pci:00/: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@savannah:~$ bt [sudo] password for pravi: [ ok ] Restarting bluetooth (via systemctl): bluetooth.service. pravi@savannah:~$ udevadm info --query=all --path=/sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1:1.0/bluetooth/hci0 P: /devices/pci:00/:00:1a.0/usb1/1-1/1-1:1.0/bluetooth/hci0 E: DEVPATH=/devices/pci:00/: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@savannah:~$ ~$ cat ~/bin/bt sudo /etc/init.d/bluetooth restart signature.asc Description: OpenPGP digital signature
Bug#734548: unable to start bluetooth service during boot
On Wednesday 08 January 2014 03:55 PM, Michael Biebl wrote: reassign 734548 bluetooth forcemerge 729808 734548 affects 729808 + systemd thanks 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. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729808#10 ~$ sudo systemctl status bluetooth.service [sudo] password for pravi: bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled) Active: inactive (dead) pravi@savannah:~$ it is still not starting, service is enabled. I still have to manually start it. signature.asc Description: OpenPGP digital signature
Bug#734548: unable to start bluetooth service during boot
Am 09.01.2014 20:56, schrieb Pirate Praveen: On Wednesday 08 January 2014 03:55 PM, Michael Biebl wrote: reassign 734548 bluetooth forcemerge 729808 734548 affects 729808 + systemd thanks 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. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729808#10 ~$ sudo systemctl status bluetooth.service [sudo] password for pravi: bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled) Active: inactive (dead) pravi@savannah:~$ it is still not starting, service is enabled. I still have to manually start it. What's the output of systemctl | grep blue ? what kind of bluetooth hardware do you have? In my case it looks like this: $ systemctl --all| grep blue sys-devi...oth-hci0.device loaded active plugged /sys/devices/pci:00/:00:1a.0/usb3/3-1/3-1.4/3-1.4:1.0/bluetooth/hci0 sys-subs...ces-hci0.device loaded active plugged /sys/subsystem/bluetooth/devices/hci0 bluetooth.service loaded active running Bluetooth service bluetooth.target loaded active activeBluetooth -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#734548: unable to start bluetooth service during boot
On Friday 10 January 2014 06:21 AM, Michael Biebl wrote: Am 09.01.2014 20:56, schrieb Pirate Praveen: On Wednesday 08 January 2014 03:55 PM, Michael Biebl wrote: reassign 734548 bluetooth forcemerge 729808 734548 affects 729808 + systemd thanks 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. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729808#10 ~$ sudo systemctl status bluetooth.service [sudo] password for pravi: bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled) Active: inactive (dead) pravi@savannah:~$ it is still not starting, service is enabled. I still have to manually start it. What's the output of systemctl | grep blue ? what kind of bluetooth hardware do you have? Jan 10 08:37:07 savannah kernel: toshiba_bluetooth: Detected Toshiba ACPI Bluetooth device - installing RFKill handler Jan 10 08:37:07 savannah kernel: toshiba_bluetooth: Re-enabling Toshiba Bluetooth In my case it looks like this: $ systemctl --all| grep blue sys-devi...oth-hci0.device loaded active plugged /sys/devices/pci:00/:00:1a.0/usb3/3-1/3-1.4/3-1.4:1.0/bluetooth/hci0 sys-subs...ces-hci0.device loaded active plugged /sys/subsystem/bluetooth/devices/hci0 bluetooth.service loaded active running Bluetooth service bluetooth.target loaded active activeBluetooth $ systemctl |grep blue sys-devi...ooth-hci0.device loaded active plugged /sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1:1.0/bluetooth/hci0 sys-subs...ices-hci0.device loaded active plugged /sys/subsystem/bluetooth/devices/hci0 signature.asc Description: OpenPGP digital signature
Bug#734548: unable to start bluetooth service during boot
reassign 734548 bluetooth forcemerge 729808 734548 affects 729808 + systemd thanks 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. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729808#10 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
