Bug 2397631
| Summary: | bluez 5.84 loses D-Bus connection and exits when connecting to headset | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Ben Boeckel <fedora> |
| Component: | bluez | Assignee: | Peter Robinson <pbrobinson> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 42 | CC: | dwmw2, lihis, michel, ngompa13, pbrobinson |
| Target Milestone: | --- | Keywords: | Desktop, Regression |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | bluez-5.84-2.fc42 bluez-5.84-2.fc43 bluez-5.84-2.fc41 | Doc Type: | --- |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2025-09-27 01:11:48 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
Ben Boeckel
2025-09-23 14:43:12 UTC
(In reply to Ben Boeckel from comment #0) > What details are necessary? The systemd logs are not all that enlightening. (In reply to Ben Boeckel from comment #0) > What details are necessary? The systemd logs are not all that enlightening. Lots. At least: * What version did you upgrade from * What bluetooth controller do you have * What headset do you have * What kernel * What linux-firmware * What else changed, did you upgrade the kernel when you updated bluez, if so from what to what. I was on 5.80. It broke right after I upgraded to 5.84 and is fixed after downgrading back to 5.80. I did reboot in between (while it was still 5.84) because I thought that could help, but it did not. Kernel is unchanged from the reboot: 6.16.7-200.fc42.x86_64 linux-firmware-20250808-1.fc42.noarch 00:14.7 Bluetooth: Intel Corporation Device a876 (rev 10) Headset is a Bose QC45. > I was on 5.80. It broke right after I upgraded to 5.84
It seems strange that you had none of the in between versions of bluez and just went straight from 5.80 to 5.84. Please test the inbetween versions:
bluez-5.81-2.fc42 f42-updates pbrobinson
bluez-5.83-1.fc42 f42-updates pbrobinson
bluez-5.83-2.fc42 f42-updates pbrobinson
bluez-5.84-1.fc42 f42-updates pbrobinson
> 00:14.7 Bluetooth: Intel Corporation Device a876 (rev 10)
Also what's the WiFi module?
00:14.3 Network controller: Intel Corporation BE201 320MHz (rev 10) Sorry, I looked at the `dnf` history more closely; 5.83 was what I had before it broke. Doing `dnf --disablerepo=updates distro-sync bluez bluez-obexd bluez-libs` put me back on 5.80 and it worked again. > Sorry, I looked at the `dnf` history more closely; 5.83 was what I had
> before it broke. Doing `dnf --disablerepo=updates distro-sync bluez
> bluez-obexd bluez-libs` put me back on 5.80 and it worked again.
That makes more sense as 5.80 is what was in GA, just to confirm 5.83 works?
It had been working, yes. I just grabbed the 5.83 packages from koji and they continue to work. FEDORA-2025-1c4ded4bf6 (bluez-5.84-2.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2025-1c4ded4bf6 FEDORA-2025-6305936bf0 (bluez-5.84-2.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-6305936bf0 FEDORA-2025-d7bf6d2fbe (bluez-5.84-2.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2025-d7bf6d2fbe FEDORA-2025-1c4ded4bf6 has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-1c4ded4bf6` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-1c4ded4bf6 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2025-6305936bf0 has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-6305936bf0` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-6305936bf0 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2025-d7bf6d2fbe has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-d7bf6d2fbe` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-d7bf6d2fbe See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2025-6305936bf0 (bluez-5.84-2.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2025-1c4ded4bf6 (bluez-5.84-2.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2025-d7bf6d2fbe (bluez-5.84-2.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report. |