Bug 1338081
| Summary: | Updating to blueman 2.0.4-2 breaks bluetooth | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | seeker_moc | ||||
| Component: | blueman | Assignee: | Pete Walter <walter.pete> | ||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 24 | CC: | fedora, lgalosha, mjd+redhat | ||||
| 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: | Environment: | ||||||
| Last Closed: | 2017-08-08 14:36:28 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
seeker_moc
2016-05-21 14:43:05 UTC
Running "sudo hciconfig hci0 up" restores bluetooth functionality with this version on Blueman. However, even with BT working, blueman still reports BT as being turned off, and shows the red "X" on the tray icon. Can confirm that the test build blueman-2.1-0.9.git3 fixes this bug for me. This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. Could someone please re-post the .rpm for blueman-2.1-0.9.git3? I did a dnf distro-sync when the F24 RPMFusion repos came out, and it downgraded my Blueman back to a faulty version. I can no longer find ver 2.1 on koji anywhere, and without it my bluetooth doesn't work. Thanks. (In reply to seeker_moc from comment #5) > Could someone please re-post the .rpm for blueman-2.1-0.9.git3? There was never a build for 2.1-0.9 on koji, as it seems. But you can find 2.1-0.8 (latest for 2.1 series). http://koji.fedoraproject.org/koji/buildinfo?buildID=716747 Thanks. Can confirm that 2.1-0.8 also fixes this bug for me. Is there a way we can get Blueman 2.1 series into the repos? For whatever reason every time I update dnf wants to move me from 2.1 back to 2.0.4, making updates a pain. There have been some complaints about API incompatibilities between bluez and blueman, that was the reason blueman-2.1 got reverted. But I don't know what's the current state. With blueman 2.0.4-4.fc25, and bluez 5.43-1.fc25 bluetooth would not turn on. Downgraded bluez to 5.42-2.fc25 and bluetooth works fine. It seems I spoke too soon. Although I can now turn bluetooth on/off and my adapter sees various devices (cellphones) none of my devices see the adapter using either temporary or permanent visibility. This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |