Comment 27 for bug 1575467

Thanks Tim, good to see other people have the same problem as usually that means this is a bug that will get fixed quickly. And good to see that there is a potential workaround to potentially solve the problem. But isn't the "fix released" status meant for developers to mark? Meaning that code has actually been changed in an upstream package and future update? If your not a developer then i'm not sure the "fix released" status is appropriate as it probably means no one will no longer look at this bug because they think someone else already fixed it.

In the past i may have ventured to go fiddling around with grub or some other file (as i did in 14.04 with my non-working bluetooth), but for something like this i'm only going to wait for an official fix. And to me this is a pretty serious issue. If my understanding of how launchpad works, then just ignore my comments.

I am also using 16.04 64bit. (not sure if many people still use 32bit or if 32bit users are unaffected).