Package: bluez Version: 4.101-2+b1 Followup-For: Bug #596795 Hi
Found this old bug when I wanted to report the same problem. This is totally unrelated to #588034. The problem is that bluetoothd is stopped in the prerm script of the currently installed package and only started again in the postinst script of the newly installed package. On upgrades with many packages this leads to a quite long period without bluetooth which is AFAIK not necessary. You should use the "--restart-after-upgrade" option to dh_installinit in your debian/rules file, unless there is an important reason for completely stopping bluetooth during an upgrade. Gaudenz -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (800, 'testing'), (700, 'unstable'), (50, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-2-amd64 (SMP w/2 CPU cores) Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages bluez depends on: ii dbus 1.6.14-1 ii kmod 9-3 ii libc6 2.17-92+b1 ii libdbus-1-3 1.6.14-1 ii libglib2.0-0 2.36.4-1 ii libreadline6 6.2+dfsg-0.1 ii libudev1 204-4 ii libusb-0.1-4 2:0.1.12-23.2 ii lsb-base 4.1+Debian12 ii python-dbus 1.2.0-2+b1 ii python-gi 3.8.2-1 ii udev 204-4 bluez recommends no packages. bluez suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
