Bug 901805
| Summary: | Package bluez depends on gnome-bluetooth | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Syam <get.sonic> | ||||
| Component: | bluez | Assignee: | Don Zickus <dzickus> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 18 | CC: | beland, bnocera, dwmw2, marcel, sanjay.ankur, williams.jerry20 | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-02-05 15:18:41 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
Syam
2013-01-19 11:30:35 UTC
I was wondering the same thing. Neither should bluez depend on or require gnome-bluetooth nor should gnome-bluetooth depend or require bluez. The communications between bluez and gnome-bluetooth happens via D-Bus and thus the existence of org.bluez (provided by bluetoothd from bluez) is a runtime dependency. It should be possible to de-install bluez package without de-installing gnome-shell. The trigger for starting bluetoothd should not be gnome-shell or gnome-bluetooth. It should be triggered by udev and bluetooth.target unit. bluez-4.101-6.fc18.x86_64 actually depends on: dependency: dbus-bluez-pin-helper provider: gnome-bluetooth.x86_64 1:3.6.1-2.fc18 provider: blueman.x86_64 1.23-5.fc18 provider: bluedevil.x86_64 1.3-1.fc18 provider: bluedevil.i686 1.3-1.fc18 This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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. Created attachment 845734 [details]
bluetooth
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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. |