Thanks for filing a new bug.
So previously we were solving this problem by a pm-utils hack to run hid2hci on
resume from S3. Can't do that anymore with the udev rules dynamically filling
in the data. So we either needto:
1) prod the killswitch in the kernel
2) prod the killswitch in userspace
3) find a way to have the kernel replay the plugin event.
I think the root of the problem is that the kernel thinks that the
device was plugged in throughout the entire suspend, but it really
wasn't. (I may be wrong here).
** Changed in: bluez (Ubuntu)
Status: New => Confirmed
--
Dell Bluetooth 370 does not work after resume from suspend
https://bugs.launchpad.net/bugs/385934
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
