This worked for me, too, but I have no idea why it's necessary. I've heard of some Broadcom chips not starting in the right mode, so maybe that's my problem. lsusb -v stanza for my little nugget/dongle is "0a5c:2039 Broadcom Corp. Bluetooth Device". I'd add something to the bluetooth init script by hand if I thought it wouldn't get overwritten.
samad909: come back to the fold! -- Bluetooth Error in Feisty Fawn https://bugs.launchpad.net/bugs/121421 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
