Bug 1715302
| Summary: | Bluetooth stopped working with kernel update 5.0.16-100 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | konrad.mrozek |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 30 | CC: | airlied, alexander, alex.go4more, bskeggs, didierg-divers, extras-qa, hdegoede, ichavero, itamar, jarodwilson, jeremy, jglisse, john.j5live, jonathan, josef, kernel-maint, konrad.mrozek, linville, mchehab, mjg59, nyh, pbrobinson, sacntct, steved, urilabob |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1711468 | Environment: | |
| Last Closed: | 2019-08-21 08:06:08 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
konrad.mrozek
2019-05-30 04:31:21 UTC
This bug was originated on Fedora 28 but I definitely exists on Fedora 30 (and probably on Fedora 29 too). It's fixed with 5.1.5: https://bodhi.fedoraproject.org/updates/FEDORA-2019-e96e0ce38b I can confirm it's fixed in version 5.1.5. No, Will version 5.1.5 be available for Fedora29 as well? Hi, Will version 5.1.5 be available for Fedora29 too? I'm sorry, but 5.1.5 in Fedora30 appears to give only a partial fix. Yes, it is possible now to pair the mouse, unlike in 5.0.16. However now, if the mouse is left untouched for a period of five minutes or so, it becomes disconnected and will not reconnect (the gnome-settings panel shows it as disconnected, every now and then it flashes the message, but it never reconnects). I assume it results from the mouse sleeping; it happens independent of whether or not the computer sleeps, for example if I am typing without using the mouse. The only way I have found to get the mouse working again is to delete the mouse connection entirely, and re-pair, which is a pretty painful way of working. I realise that this is a _behaviour_ that has other similar reports, but they must nevertheless be for a different bug, since they were raised for pre-5.0.13 kernels. This mouse worked perfectly under 5.0.13 on Fedora28 (an additional complication is that in the meantime, I had to upgrade from Fedora28 to Fedora30 to get the 5.1.5 fix. So it could be a regression in Fedora30 as against Fedora28, I guess). Practically, I'm not sure whether this should be raised as a separate bug, though I believe it is likely to be a regression in the 5.1.5 fix. Any advice? Apologies, please ignore my previous comment (I was inadvertently running 5.0.16 while thinking I was running 5.1.5) *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 30 kernel bugs. Fedora 30 has now been rebased to 5.2.9-200.fc30. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 31, and are still experiencing this issue, please change the version to Fedora 31. If you experience different issues, please open a new bug report for those. The bug was fixed in 5.1.5, as reported above. It hasn't reappeared. It needs to be marked as FIXED, but I don't think I as the originator have the ability to do this. For the reasons described in my original post, I don't have the ability to test it in 5.2.9-200.fc30, but there is no reason to anticipate a regression. |