Bug 634205
| Summary: | Bluetooth always disabled on startup. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Steven Haigh <netwiz> |
| Component: | bluez | Assignee: | Bastien Nocera <bnocera> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 14 | CC: | awilliam, bnocera, ceski, dwmw2, marcel, notting, plautrba |
| Target Milestone: | --- | Keywords: | CommonBugs, Reopened |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | https://fedoraproject.org/wiki/Common_F14_bugs#bluetooth_disabled | ||
| Fixed In Version: | bluez-4.71-5.fc14 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-10-01 12:23:28 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 538277 | ||
|
Description
Steven Haigh
2010-09-15 14:01:47 UTC
proposing for f14beta blocker discussion, as it's a regression associated with the upstart reversion (it works with systemd) and could potentially affect network connectivity for some. I've actually had this not work *with* systemd. (where it starts up disabled, and needs a disable/enable cycle to enable itself.) It worked with systemd as of 4.71-2 (prior to that, it didn't work as you describe). I confirm the regression from 4.71-2+systemd (where it works fine) to 4.71-2+upstart or 4.71-3+upstart (doesn't work, even with a cycle). Bastien let me know privately that he is will not be able to work on this bug today. http://koji.fedoraproject.org/koji/taskinfo?taskID=2469704 may or may not work. That one doesn't work on boot, but does come up after a disable/enable cycle (which would be good enough for this to definitely not be a beta blocker, imo). can you submit -4 as an update? it seems to be better than -3, at least. i expect we'd probably reject this as a blocker but take it as a nth, if I gaze into my crystal ball; i really just added it to the blocker list to make sure we tracked it. in fact, i'm gonna move it to nth, the blocker justification is tenuous. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers bluez-4.71-4.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/bluez-4.71-4.fc14 This doesn't seem to have been pushed yet... Are we waiting on anything at all? Also: I installed 4.71-4 via the download link on admin.fedoraproject.org - however this does not fix this bug. Bluetooth still remains disabled on boot. It is however a slight improvement on -2 as you can disable / enable BT to make it work again. Yeah, I had the same experience. The package is waiting because we're in Beta freeze and I guess it didn't get pulled for RC1 (my fault, I didn't quite get to talk to releng about the NTH blocker thing yet). bluez-4.71-4.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update bluez'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/bluez-4.71-4.fc14 bluez-4.71-4.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report. This bug still remains with 4.71-4. Indeed: -4 makes it work after a disable/enable in the applet, but it's still disabled on startup, which needs fixing. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers bluez-4.71-5.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/bluez-4.71-5.fc14 bluez-4.71-5.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update bluez'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/bluez-4.71-5.fc14 I can confirm this is fixed in -5. ok to close IMHO. this is a final blocker, as it's a part of the default panel configuration which doesn't work right. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers bluez-4.71-5.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report. |