# initctl reload-configuration # start bluetooth start: Job failed to start
> A simple reload of the Upstart config isn't enough. Upstart should do this anyway as it gets notified via inotify. # find /etc/init | xargs grep bluetooth -sl /etc/init/bluetooth.conf > No Upstart jobs that use 'starting bluetooth' and that could fail # ps auxw | grep -v grep | grep bluetoothd root 622 0.0 0.0 21192 872 ? Ss Apr03 0:00 /usr/sbin/bluetoothd # killall bluetoothd # ps auxw | grep -v grep | grep bluetoothd root 24675 0.0 0.1 19296 1700 ? Ss 09:39 0:00 /usr/sbin/bluetoothd > bluetoothd is up and running and can be (re)started # ls -la /usr/sbin/hciattach -rwxr-xr-x 1 root root 100736 Dec 20 03:43 /usr/sbin/hciattach # ls -la /etc/bluetooth/uart ls: cannot access /etc/bluetooth/uart: No such file or directory > hciattach won't be called # ls -la /usr/bin/rfcomm -rwxr-xr-x 1 root root 87288 Dec 20 03:43 /usr/bin/rfcomm # ls -la /etc/bluetooth/rfcomm.conf -rw-r--r-- 1 root root 297 Mar 21 2012 /etc/bluetooth/rfcomm.conf # sh -c "/usr/bin/rfcomm -f /etc/bluetooth/rfcomm.conf bind all ; echo exit code: $?" exit code: 0 > I don't see any obvious issue with the bluetooth Upstart job configuration -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1301962 Title: package update of bluez 4.98-2ubuntu7 (Precise) to 4.101-0ubuntu10 (Trusty) fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1301962/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
