Bug#755274: [Pkg-bluetooth-maintainers] Bug#755274: bluez: BT adapter isn't powered on at boot
Dear Nobuhiro, Absolutely agree. Thank you! Best regards, Andriy On Mon, 28 Jul 2014 15:43:20 +0900 Nobuhiro Iwamatsu iwama...@nigauri.org wrote: Hi, 2014-07-26 22:10 GMT+09:00 Andriy Martynets martyn...@volia.ua: On Sat, 26 Jul 2014 04:52:49 +0900 Nobuhiro Iwamatsu iwama...@nigauri.org wrote: Dear Nobuhiro, Thanks! Using of the udev rule is reasonable as this activates any BT adapter as soon as it is plugged in. Maintaining this via an init script works fine in majority of cases but not in all. As the script runs once it will not cover cases when the adapter is hot plugged later. Reverting this back will solve the bug as will make the package working fine. To improve the package by adding the udev rule you have to make the hciconfig tool available from the rootfs. You can see if you get a look at the other mail of this bug, I have received other proposals from Michael. It is a proposal to move to / bin the hciconfig. I think that trying to adopt this proposal. Because hciconifg depends only on libraries of / lib, it can be moved. In addition, we can unify the initialization of hciX in systemd, sysvinit and other init system can be controlled by udev. Of course, this resolve problem of this BTS. This is reasonable, I think. Thank you again and best regards, Andriy Best regards, Nobuhiro -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755274: [Pkg-bluetooth-maintainers] Bug#755274: bluez: BT adapter isn't powered on at boot
Hi,
2014-07-26 22:10 GMT+09:00 Andriy Martynets martyn...@volia.ua:
On Sat, 26 Jul 2014 04:52:49 +0900
Nobuhiro Iwamatsu iwama...@nigauri.org wrote:
Dear Nobuhiro,
Thanks!
Using of the udev rule is reasonable as this activates any BT adapter
as soon as it is plugged in. Maintaining this via an init script works
fine in majority of cases but not in all. As the script runs once it
will not cover cases when the adapter is hot plugged later.
Reverting this back will solve the bug as will make the package working
fine.
To improve the package by adding the udev rule you have to make the
hciconfig tool available from the rootfs.
You can see if you get a look at the other mail of this bug, I have
received other proposals from Michael.
It is a proposal to move to / bin the hciconfig. I think that trying
to adopt this proposal.
Because hciconifg depends only on libraries of / lib, it can be moved.
In addition, we can unify the initialization of hciX in systemd,
sysvinit and other init system can be controlled
by udev. Of course, this resolve problem of this BTS. This is
reasonable, I think.
Thank you again and best regards,
Andriy
Best regards,
Nobuhiro
Hi,
Thanks for your report.
2014-07-19 22:20 GMT+09:00 Andriy Martynets martyn...@volia.ua:
Package: bluez
Version: 5.21-1
Severity: serious
Justification: Policy 9.1.1
Dear Maintainer,
The issue appeared after upgrade to version 5.21.
The udev rule 50-bluetooth-hci-auto-poweron.rules tries to
run /usr/bin/hciconfig tool. This rule is executed at early stage
of boot process (/etc/rcS.d/S02udev) when /usr is mounted later
(/etc/rcS.d/S09mountall.sh). In my understanding this tool must be
installed in /sbin directory as one needed at boot time.
Alternatively this must be managed somehow at later stage (e.g.
'udevadm trigger --verbose --action=add --subsystem-match=bluetooth
--sysname-match=hci*' command in /etc/init.d/bluetooth)
I see.
I enabled the hciX in bluetooth.init in earlier versions.
I will revert this and remove 50-bluetooth-hci-auto-poweron.rules
from bluez package
I tried the mentioned above udevadm command and it helped. See
modified file below. It also contains alterations to fix bug
#754830.
Best regards,
Andriy
Best regards,
Nobuhiro
--
Nobuhiro Iwamatsu
iwamatsu at {nigauri.org / debian.org}
GPG ID: 40AD1FA6
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755274: [Pkg-bluetooth-maintainers] Bug#755274: bluez: BT adapter isn't powered on at boot
On Sat, 26 Jul 2014 04:52:49 +0900 Nobuhiro Iwamatsu iwama...@nigauri.org wrote: Dear Nobuhiro, Thanks! Using of the udev rule is reasonable as this activates any BT adapter as soon as it is plugged in. Maintaining this via an init script works fine in majority of cases but not in all. As the script runs once it will not cover cases when the adapter is hot plugged later. Reverting this back will solve the bug as will make the package working fine. To improve the package by adding the udev rule you have to make the hciconfig tool available from the rootfs. Thank you again and best regards, Andriy Hi, Thanks for your report. 2014-07-19 22:20 GMT+09:00 Andriy Martynets martyn...@volia.ua: Package: bluez Version: 5.21-1 Severity: serious Justification: Policy 9.1.1 Dear Maintainer, The issue appeared after upgrade to version 5.21. The udev rule 50-bluetooth-hci-auto-poweron.rules tries to run /usr/bin/hciconfig tool. This rule is executed at early stage of boot process (/etc/rcS.d/S02udev) when /usr is mounted later (/etc/rcS.d/S09mountall.sh). In my understanding this tool must be installed in /sbin directory as one needed at boot time. Alternatively this must be managed somehow at later stage (e.g. 'udevadm trigger --verbose --action=add --subsystem-match=bluetooth --sysname-match=hci*' command in /etc/init.d/bluetooth) I see. I enabled the hciX in bluetooth.init in earlier versions. I will revert this and remove 50-bluetooth-hci-auto-poweron.rules from bluez package I tried the mentioned above udevadm command and it helped. See modified file below. It also contains alterations to fix bug #754830. Best regards, Andriy Best regards, Nobuhiro -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755274: [Pkg-bluetooth-maintainers] Bug#755274: bluez: BT adapter isn't powered on at boot
Hi,
Thanks for your report.
2014-07-19 22:20 GMT+09:00 Andriy Martynets martyn...@volia.ua:
Package: bluez
Version: 5.21-1
Severity: serious
Justification: Policy 9.1.1
Dear Maintainer,
The issue appeared after upgrade to version 5.21.
The udev rule 50-bluetooth-hci-auto-poweron.rules tries to run
/usr/bin/hciconfig tool.
This rule is executed at early stage of boot process (/etc/rcS.d/S02udev)
when /usr is mounted later (/etc/rcS.d/S09mountall.sh).
In my understanding this tool must be installed in /sbin directory as one
needed at boot time. Alternatively this must be managed somehow
at later stage (e.g. 'udevadm trigger --verbose --action=add
--subsystem-match=bluetooth --sysname-match=hci*' command in
/etc/init.d/bluetooth)
I see.
I enabled the hciX in bluetooth.init in earlier versions.
I will revert this and remove 50-bluetooth-hci-auto-poweron.rules
from bluez package
I tried the mentioned above udevadm command and it helped. See modified file
below. It also contains alterations to fix bug #754830.
Best regards,
Andriy
Best regards,
Nobuhiro
-- System Information:
Debian Release: jessie/sid
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'),
(500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.14.4 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages bluez depends on:
ii dbus 1.8.6-1
ii init-system-helpers 1.19
ii kmod 18-1
ii libc62.19-7
ii libdbus-1-3 1.8.6-1
ii libglib2.0-0 2.40.0-3
ii libreadline6 6.3-6
ii libudev1 208-6
ii lsb-base 4.1+Debian13
ii udev 208-6
bluez recommends no packages.
bluez suggests no packages.
-- Configuration Files:
/etc/init.d/bluetooth changed:
PATH=/sbin:/bin:/usr/sbin:/usr/bin
DESC=bluetooth
DAEMON=/usr/sbin/bluetoothd
HCIATTACH=/usr/sbin/hciattach
HID2HCI_ENABLED=1
HID2HCI_UNDO=1
UART_CONF=/etc/bluetooth/uart
RFCOMM_NAME=rfcomm
RFCOMM=/usr/bin/$RFCOMM_NAME
RFCOMM_CONF=/etc/bluetooth/$RFCOMM_NAME.conf
SDPTOOL=/usr/bin/sdptool
NOPLUGIN_OPTION=
SSD_OPTIONS=--oknodo --quiet --exec $DAEMON -- $NOPLUGIN_OPTION
test -f $DAEMON || exit 0
test -f /etc/default/bluetooth . /etc/default/bluetooth
test -f /etc/default/rcS . /etc/default/rcS
.. /lib/lsb/init-functions
set -e
run_sdptool()
{
# declaring IFS local in this function, removes the need to
# save/restore it
local IFS o
test -x $SDPTOOL || return 1
if ! test -z $SDPTOOL_OPTIONS ; then
IFS=;
for o in $SDPTOOL_OPTIONS ; do
#echo execing $SDPTOOL $o
IFS=
if [ $VERBOSE != no ]; then
$SDPTOOL $o
else
$SDPTOOL $o /dev/null 21
fi
done
fi
}
hci_input()
{
log_progress_msg switching to HID/HCI no longer done in init script, see
/usr/share/doc/bluez/NEWS.Debian.gz || :
}
alias enable_hci_input=hci_input
alias disable_hci_input=hci_input
start_uarts()
{
[ -f $HCIATTACH ] [ -f $UART_CONF ] || return
grep -v '^#' $UART_CONF | while read i; do
if [ $VERBOSE != no ]; then
$HCIATTACH $i
else
$HCIATTACH $i /dev/null 21
fi
done
}
stop_uarts()
{
killall ${HCIATTACH##*/} /dev/null 21 || :
}
start_rfcomm()
{
if [ -x $RFCOMM ] [ -f $RFCOMM_CONF ] ; then
# rfcomm must always succeed for now: users
# may not yet have an rfcomm-enabled kernel
if [ $VERBOSE != no ]; then
log_progress_msg ${RFCOMM##*/}
$RFCOMM bind all || :
else
$RFCOMM bind all /dev/null 21 || :
fi
fi
}
stop_rfcomm()
{
if [ -x $RFCOMM ] ; then
if [ $VERBOSE != no ]; then
log_progress_msg ${RFCOMM##*/}
$RFCOMM unbind all || :
else
$RFCOMM unbind all /dev/null 21 || :
fi
fi
}
restart_rfcomm()
{
if [ -x $RFCOMM ] [ -f $RFCOMM_CONF ] ; then
if [ $VERBOSE != no ]; then
log_progress_msg ${RFCOMM##*/}
$RFCOMM unbind all || :
$RFCOMM bind all || :
else
$RFCOMM unbind all /dev/null 21|| :
$RFCOMM bind all /dev/null 21 || :
fi
fi
}
case $1 in
start)
Bug#755274: [Pkg-bluetooth-maintainers] Bug#755274: bluez: BT adapter isn't powered on at boot
Hi, Michael.
Thanks for your infomation.
I enabled the hciX in bluetooth.init in previous versions.
I will revert this function and remove udev rules in next version.
For systemd , I will enable using the ExecStartPre in bluetooth UNIT.
Please let me know if there is a better way other.
Best regards,
Nobuhiro
2014-07-22 22:39 GMT+09:00 Michael Biebl bi...@debian.org:
Instead of having each udev rule having to work around this issue, it
would be much better to simply mount /usr via the initramfs and
discourage the use of a separate /usr partition.
dracut can already do that, for initramfs-tools there is [1].
As a reality check you might be interested in the attached list.
Cheers,
Michael
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652459
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
___
Pkg-bluetooth-maintainers mailing list
pkg-bluetooth-maintain...@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-bluetooth-maintainers
--
Nobuhiro Iwamatsu
iwamatsu at {nigauri.org / debian.org}
GPG ID: 40AD1FA6
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755274: [Pkg-bluetooth-maintainers] Bug#755274: bluez: BT adapter isn't powered on at boot
Am 25.07.2014 21:59, schrieb Nobuhiro Iwamatsu: Hi, Michael. Thanks for your infomation. I enabled the hciX in bluetooth.init in previous versions. I will revert this function and remove udev rules in next version. For systemd , I will enable using the ExecStartPre in bluetooth UNIT. Please let me know if there is a better way other. Well, you could just move hcitool to /bin. It seems all it's library dependencies are already in /lib. Are there any ressources hcitool needs from /usr? Fwiw, I don't think running udevadm trigger from the .service file (or sysvinit init script) is such a great idea. Even if it is limited to the bluetooth subsystem. -- 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#755274: [Pkg-bluetooth-maintainers] Bug#755274: bluez: BT adapter isn't powered on at boot
Hi, Michael.
Thanks for your comment.
2014-07-26 5:12 GMT+09:00 Michael Biebl bi...@debian.org:
Am 25.07.2014 21:59, schrieb Nobuhiro Iwamatsu:
Hi, Michael.
Thanks for your infomation.
I enabled the hciX in bluetooth.init in previous versions.
I will revert this function and remove udev rules in next version.
For systemd , I will enable using the ExecStartPre in bluetooth UNIT.
Please let me know if there is a better way other.
Well, you could just move hcitool to /bin. It seems all it's library
dependencies are already in /lib.
I see.
Are there any ressources hcitool needs from /usr?
No, there are any resources.
Fwiw, I don't think running udevadm trigger from the .service file (or
sysvinit init script) is such a great idea. Even if it is limited to the
bluetooth subsystem.
OK, I will think about move hcitool to /bin.
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
Thanks again.
Nobuhiro
--
Nobuhiro Iwamatsu
iwamatsu at {nigauri.org / debian.org}
GPG ID: 40AD1FA6
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755274: bluez: BT adapter isn't powered on at boot
On Tue, 22 Jul 2014 15:39:36 +0200 Michael Biebl bi...@debian.org wrote: Instead of having each udev rule having to work around this issue, it would be much better to simply mount /usr via the initramfs and discourage the use of a separate /usr partition. dracut can already do that, for initramfs-tools there is [1]. As a reality check you might be interested in the attached list. Cheers, Michael [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652459 Dear Michael, Many thanks for the info provided and one more idea on how to work around this bug. But this is not the solution. The solution is a change to the package after which end-user, once installed it on to the standard Debian system, will have to take zero steps to get it working. As the root cause of the issue is the policy violation I see the simplest and straight forward solution as to move file in question to standard location to comply with standards. From your message I can conclude that you are going to make the package dependent on new versions of initramfs-tools, sysvinit and util-linux packages which seem to be not available yet. Is this correct? Reading all these threads (bug #652459 and related) I thought that guys must have good reason to make simple things so complicated. I share believe that initramfs is to provide the kernel with the module to mount real rootfs. All the rest can be done by real init. Thanks to Robert Tracy I realized what is the reason. It's all about systemd! This answered all my questions... Best regards, Andriy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755274: bluez: BT adapter isn't powered on at boot
Instead of having each udev rule having to work around this issue, it
would be much better to simply mount /usr via the initramfs and
discourage the use of a separate /usr partition.
dracut can already do that, for initramfs-tools there is [1].
As a reality check you might be interested in the attached list.
Cheers,
Michael
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652459
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
alsa-utils/rules.d/90-alsa-restore.rules:ACTION==add, SUBSYSTEM==sound,
KERNEL==controlC*, KERNELS!=card*, TEST==/usr/sbin,
TEST==/usr/share/alsa, GOTO=alsa_restore_go
alsa-utils/rules.d/90-alsa-restore.rules:TEST!=/etc/alsa/state-daemon.conf,
RUN+=/usr/sbin/alsactl -E HOME=/var/run/alsa restore $attr{device/number}
alsa-utils/rules.d/90-alsa-restore.rules:TEST==/etc/alsa/state-daemon.conf,
RUN+=/usr/sbin/alsactl -E HOME=/var/run/alsa nrestore $attr{device/number}
barry-util/rules.d/10-blackberry.rules: RUN=/usr/sbin/bcharge -p %p
barry-util/rules.d/10-blackberry.rules: RUN=/usr/sbin/bcharge -d
barry-util/rules.d/10-blackberry.rules: RUN=/usr/sbin/bcharge -g -p %p
barry-util/rules.d/10-blackberry.rules: RUN=/usr/sbin/bcharge -g -p %p
barry-util/rules.d/10-blackberry.rules: RUN=/usr/sbin/bcharge -g -p %p
barry-util/rules.d/10-blackberry.rules: RUN=/usr/sbin/bcharge -p %p
bilibop-rules/rules.d/66-bilibop.rules:# you can run
/usr/share/bilibop/bilibop_rules_generator to create a
bluez/rules.d/50-bluetooth-hci-auto-poweron.rules:ACTION==add,
SUBSYSTEM==bluetooth, KERNEL==hci[0-9]*, RUN+=/usr/bin/hciconfig %k up
boinc-client/rules.d/60-boinc-client.rules:SUBSYSTEM==kernel,
DEVPATH==/kernel/uids/*, ACTION==add,
RUN+=/usr/share/boinc-client/udev-cpu_share
ceph/rules.d/95-ceph-osd.rules: RUN+=/usr/sbin/ceph-disk-activate /dev/$name
ceph/rules.d/95-ceph-osd.rules: RUN+=/usr/sbin/ceph-disk activate-journal
/dev/$name
ceph/rules.d/95-ceph-osd.rules: RUN+=/usr/sbin/ceph-disk-activate
/dev/mapper/$env{ID_PART_ENTRY_UUID}
dahdi-linux/rules.d/xpp.rules: RUN+=/usr/share/dahdi/xpp_fxloader udev
$env{PRODUCT}
dahdi-linux/rules.d/xpp.rules:# By default XPP_INIT_DIR=/usr/share/dahdi
dahdi/rules.d/60-dahdi.rules:SUBSYSTEM==dahdi_devices,
RUN=/usr/share/dahdi/handle_device
dahdi/rules.d/60-dahdi.rules:SUBSYSTEM==dahdi_spans,
RUN=/usr/share/dahdi/span_config
flashcache-utils/rules.d/84-flashcache.rules:,RUN+=/usr/bin/logger -t
flashcache Version mismatch between utilities and kernel module.\
flashcache-utils/rules.d/84-flashcache.rules:,RUN+=/usr/bin/logger -t
flashcache[/dev/%k] Loaded flashcache device. %c
hplip/rules.d/56-hpmud.rules:ENV{hp_test}==yes, PROGRAM=/bin/sh -c 'logger
-p user.info loading HP Device $env{BUSNUM} $env{DEVNUM}', RUN+=/bin/sh -c
'if [ -f /usr/bin/systemctl ]; then /usr/bin/systemctl --no-block start
hplip-printer@$env{BUSNUM}:$env{DEVNUM}.service; else /usr/bin/nohup
/usr/bin/python /usr/bin/hp-config_usb_printer $env{BUSNUM}:$env{DEVNUM} ; fi
'
irda-utils/rules.d/60-irda-utils.rules:SUBSYSTEM==net, SUBSYSTEMS==usb,
ACTION==add, ATTR{type}==783, RUN+=/sbin/start-stop-daemon --start --quiet
--pidfile /var/run/irattach.pid --startas /usr/sbin/irattach -- $env{INTERFACE}
-s
ir-keytable/rules.d/60-ir-keytable.rules:ACTION==add, SUBSYSTEM==rc,
RUN+=/usr/bin/ir-keytable -a /etc/rc_maps.cfg -s $name
isight-firmware-tools/rules.d/80_isight.rules:ACTION==add,
ATTRS{idVendor}==05ac, ATTRS{idProduct}==8300, RUN+=/usr/lib/udev/ift-load
--firmware /lib/firmware/isight.fw
kino/rules.d/60-kino.rules:RUN+=/usr/bin/killall --quiet -USR2 kino
kino/rules.d/60-kino.rules:RUN+=/usr/bin/killall --quiet -USR2 kino
libccid/rules.d/92-libccid.rules:#SUBSYSTEMS==pcmcia, DRIVERS==serial_cs,
ACTION==add, ATTRS{prod_id1}==Gemplus, ATTRS{prod_id2}==SerialPort,
ATTRS{prod_id3}==GemPC Card, RUN+=/usr/sbin/pcscd --hotplug
libccid/rules.d/92-libccid.rules:ATTRS{idVendor}==0d46,
ATTRS{idProduct}==4081, RUN+=/usr/sbin/Kobil_mIDentity_switch
libffado2/rules.d/60-ffado.rules:# Focusrite Audio Engineering Limited
libgnuradio-fcd3.7.3/rules.d/60-libgnuradio-fcd3.7.3.rules:ACTION==add,
BUS==usb, SYSFS{idVendor}==04d8, SYSFS{idProduct}==fb56, GROUP:=usrp,
MODE:=0660, SYMLINK+=FCD
libgnuradio-fcd3.7.3/rules.d/60-libgnuradio-fcd3.7.3.rules:SUBSYSTEMS==usb,
ATTRS{idVendor}==04d8, ATTRS{idProduct}==fb56,GROUP:=usrp, MODE:=0660,
SYMLINK+=FCD
libosinfo-bin/rules.d/95-osinfo.rules:
IMPORT{program}=/usr/bin/osinfo-detect -f env $tempnode
librbd1/rules.d/50-rbd.rules:KERNEL==rbd[0-9]*, ENV{DEVTYPE}==disk,
PROGRAM=/usr/bin/ceph-rbdnamer %k, SYMLINK+=rbd/%c{1}/%c{2}
librbd1/rules.d/50-rbd.rules:KERNEL==rbd[0-9]*, ENV{DEVTYPE}==partition,
PROGRAM=/usr/bin/ceph-rbdnamer %k, SYMLINK+=rbd/%c{1}/%c{2}-part%n
madfuload/rules.d/42-madfuload.rules:ACTION==add, SUBSYSTEM==usb,
ENV{DEVTYPE}==usb_device, ATTRS{idVendor}==0763, ATTRS{idProduct}==2803,
RUN+=/usr/sbin/madfuload -l -n -f
Bug#755274: bluez: BT adapter isn't powered on at boot
Package: bluez
Version: 5.21-1
Severity: serious
Justification: Policy 9.1.1
Dear Maintainer,
The issue appeared after upgrade to version 5.21.
The udev rule 50-bluetooth-hci-auto-poweron.rules tries to run
/usr/bin/hciconfig tool.
This rule is executed at early stage of boot process (/etc/rcS.d/S02udev) when
/usr is mounted later (/etc/rcS.d/S09mountall.sh).
In my understanding this tool must be installed in /sbin directory as one
needed at boot time. Alternatively this must be managed somehow
at later stage (e.g. 'udevadm trigger --verbose --action=add
--subsystem-match=bluetooth --sysname-match=hci*' command in
/etc/init.d/bluetooth)
I tried the mentioned above udevadm command and it helped. See modified file
below. It also contains alterations to fix bug #754830.
Best regards,
Andriy
-- System Information:
Debian Release: jessie/sid
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'),
(500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.14.4 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages bluez depends on:
ii dbus 1.8.6-1
ii init-system-helpers 1.19
ii kmod 18-1
ii libc62.19-7
ii libdbus-1-3 1.8.6-1
ii libglib2.0-0 2.40.0-3
ii libreadline6 6.3-6
ii libudev1 208-6
ii lsb-base 4.1+Debian13
ii udev 208-6
bluez recommends no packages.
bluez suggests no packages.
-- Configuration Files:
/etc/init.d/bluetooth changed:
PATH=/sbin:/bin:/usr/sbin:/usr/bin
DESC=bluetooth
DAEMON=/usr/sbin/bluetoothd
HCIATTACH=/usr/sbin/hciattach
HID2HCI_ENABLED=1
HID2HCI_UNDO=1
UART_CONF=/etc/bluetooth/uart
RFCOMM_NAME=rfcomm
RFCOMM=/usr/bin/$RFCOMM_NAME
RFCOMM_CONF=/etc/bluetooth/$RFCOMM_NAME.conf
SDPTOOL=/usr/bin/sdptool
NOPLUGIN_OPTION=
SSD_OPTIONS=--oknodo --quiet --exec $DAEMON -- $NOPLUGIN_OPTION
test -f $DAEMON || exit 0
test -f /etc/default/bluetooth . /etc/default/bluetooth
test -f /etc/default/rcS . /etc/default/rcS
.. /lib/lsb/init-functions
set -e
run_sdptool()
{
# declaring IFS local in this function, removes the need to
# save/restore it
local IFS o
test -x $SDPTOOL || return 1
if ! test -z $SDPTOOL_OPTIONS ; then
IFS=;
for o in $SDPTOOL_OPTIONS ; do
#echo execing $SDPTOOL $o
IFS=
if [ $VERBOSE != no ]; then
$SDPTOOL $o
else
$SDPTOOL $o /dev/null 21
fi
done
fi
}
hci_input()
{
log_progress_msg switching to HID/HCI no longer done in init script, see
/usr/share/doc/bluez/NEWS.Debian.gz || :
}
alias enable_hci_input=hci_input
alias disable_hci_input=hci_input
start_uarts()
{
[ -f $HCIATTACH ] [ -f $UART_CONF ] || return
grep -v '^#' $UART_CONF | while read i; do
if [ $VERBOSE != no ]; then
$HCIATTACH $i
else
$HCIATTACH $i /dev/null 21
fi
done
}
stop_uarts()
{
killall ${HCIATTACH##*/} /dev/null 21 || :
}
start_rfcomm()
{
if [ -x $RFCOMM ] [ -f $RFCOMM_CONF ] ; then
# rfcomm must always succeed for now: users
# may not yet have an rfcomm-enabled kernel
if [ $VERBOSE != no ]; then
log_progress_msg ${RFCOMM##*/}
$RFCOMM bind all || :
else
$RFCOMM bind all /dev/null 21 || :
fi
fi
}
stop_rfcomm()
{
if [ -x $RFCOMM ] ; then
if [ $VERBOSE != no ]; then
log_progress_msg ${RFCOMM##*/}
$RFCOMM unbind all || :
else
$RFCOMM unbind all /dev/null 21 || :
fi
fi
}
restart_rfcomm()
{
if [ -x $RFCOMM ] [ -f $RFCOMM_CONF ] ; then
if [ $VERBOSE != no ]; then
log_progress_msg ${RFCOMM##*/}
$RFCOMM unbind all || :
$RFCOMM bind all || :
else
$RFCOMM unbind all /dev/null 21|| :
$RFCOMM bind all /dev/null 21 || :
fi
fi
}
case $1 in
start)
log_daemon_msg Starting $DESC
if test $BLUETOOTH_ENABLED = 0; then
log_progress_msg disabled. see /etc/default/bluetooth
log_end_msg 0
exit 0
fi
start-stop-daemon --start --background $SSD_OPTIONS
log_progress_msg ${DAEMON##*/}
udevadm trigger --verbose --action=add --subsystem-match=bluetooth
--sysname-match=hci*
