There is nothing we can do from bluez side. If the kernel interface we
need to do *any* work is not available we can't do anything else but
fail. The "bluetooth" module needs to be loaded or the kernel compiled
with CONFIG_BT=y rather than CONFIG_BT=m.
Is there any reason not to compile bluetooth support directly into the
kernel? Any driver can still be loaded as module but the subsystem
should be always available.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags added: bluetooth
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1506774
Title:
package bluez 5.35-0ubuntu1 failed to install/upgrade: subprocess
installed post-installation script returned error exit status 1
(without linux-image-extra*)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1506774/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
