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
