Package upgrade of bluetooth disables the bluez daemon, causing keyboard, mouse and audio (all bluetooth)
to stop working for as long as the complete upgrade process takes, this can easily take up to 20 minutes.

Since the bluetooth devices are the only input devices on a lot of my desktop systems, the devices get useless.

When doing an unattended update on the client systems this is a major issues, users believe there system broke
and try to turn the system on and off.

Bluetooth should not be disabled for longer then a few seconds during a package upgrade.

Hi,

Thanks for your report.

It is thought that this problem is the same as #588034.
This is revised with 4.66-3 or 4.82.
Would you confirm it?

Best regards,
  Nobuhiro

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