This seems a lot like a user space race. bluez is trying to do stuff with the driver before the firmware is loaded. Is there a way to construct the udev rule such that bluez doesn't get started until after the firmware load is done ?
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1221618 Title: Bluetooth doesn't work after S3/S4 or after turning bluetooth on/off several times by toggle key To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1221618/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
