Bug#820473: console-setup-linux: keyboard-setup.sh calls tools from /usr filesystem which isn't mounted yet
Package: console-setup-linux Version: 1.141 Severity: important Dear Maintainer, After latest system update (can't say for sure console-setup-linux or console-tools package was updated or both) keyboard-setup.sh started to fail at boot time. The point is that the script calls /etc/console-setup/cached_setup_keyboard.sh which in turn calls kbd_mode (utility from console-tools package) located in /usr/bin directory. The /usr filesystem isn't available at that stage as keyboard-setup.sh runs before mountall.sh. I believe that tools required at boot time must be within the rootfs (/bin or /sbin directories) or order of the init scripts must be changed. Thank you in advance, Andriy Martynets -- System Information: Debian Release: stretch/sid APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.4.0 (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 Init: sysvinit (via /sbin/init) Versions of packages console-setup-linux depends on: ii console-tools 1:0.2.3dbs-70 ii init-system-helpers 1.29 ii initscripts 2.88dsf-59.3 ii keyboard-configuration 1.141 console-setup-linux recommends no packages. Versions of packages console-setup-linux suggests: ii console-setup 1.141 Versions of packages keyboard-configuration depends on: ii debconf 1.5.59 ii liblocale-gettext-perl 1.07-1+b1 Versions of packages console-setup depends on: ii debconf 1.5.59 ii keyboard-configuration 1.141 ii xkb-data2.17-1 Versions of packages console-setup suggests: ii locales 2.22-5 ii lsb-base 9.20160110 Versions of packages console-setup-linux is related to: pn console-common pn console-data ii console-tools 1:0.2.3dbs-70 pn gnome-control-center pn kbd ii systemd 229-3 -- debconf information: console-setup/use_system_font: * keyboard-configuration/layoutcode: us,ua * keyboard-configuration/toggle: Control+Shift console-setup/fontsize: 8x16 * keyboard-configuration/store_defaults_in_debconf_db: true * keyboard-configuration/layout: * keyboard-configuration/other: console-setup/charmap47: UTF-8 console-setup/codeset47: # Latin1 and Latin5 - western Europe and Turkic languages * keyboard-configuration/variant: Ukrainian * keyboard-configuration/switch: No temporary switch console-setup/store_defaults_in_debconf_db: true * keyboard-configuration/altgr: The default for the keyboard layout * keyboard-configuration/xkb-keymap: ua debian-installer/console-setup-udeb/title: * keyboard-configuration/compose: No compose key console-setup/fontface47: Fixed keyboard-configuration/ctrl_alt_bksp: false console-setup/framebuffer_only: keyboard-configuration/unsupported_options: true console-setup/fontsize-fb47: 8x16 * keyboard-configuration/modelcode: pc105 keyboard-configuration/unsupported_config_layout: true * keyboard-configuration/optionscode: grp:ctrl_shift_toggle,grp_led:scroll keyboard-configuration/unsupported_layout: true console-setup/fontsize-text47: 8x16 console-setup/codesetcode: Lat15 keyboard-configuration/unsupported_config_options: true * keyboard-configuration/model: Generic 105-key (Intl) PC * keyboard-configuration/variantcode: , console-setup/guess_font:
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
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: 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
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*
