Bug 286001

Summary:	Bluetooth and HIDD services need to be changed around in startup/shutdown order
Product:	[Fedora] Fedora	Reporter:	Paul D <anothersillyname>
Component:	bluez-utils	Assignee:	David Woodhouse <dwmw2>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	medium
Version:	7	CC:	triage
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-06-17 02:23:00 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 Paul D 2007-09-11 14:03:55 UTC

Hi 

I'm running Fedora 7 (22.4-65) both i386 and x86_64 on two different machines 
(a desktop and a laptop).

During services startup on a default build the bluetooth services are starting 
before HIDD services, this causes a communications channel conflict and HIDD 
will not start as a result.  This means any Bluetooth services also fail.

To fix the problem I've changed my bluetooth and HIDD startup scripts order in /
etc/rc.d/* so that HIDD now starts immediately before bluetooth.  This doesn't 
seem to have caused any ill effects on either machine and my bluetooth devices 
are now connected and bonded correctly during startup.  In fact on my desktop 
I'm now using a Microsoft Bluetooth kybd and mouse without any problems 
whatsoever.

I'm a little confused about the ownership of HIDD and bluetooth modules (do 
they have the same owner?) so I hope I've posted this in the correct location.

Regards

Comment 1 Bug Zapper 2008-05-14 14:19:39 UTC

This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. 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 '7'.

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 7's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 7 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 please change the 'version' of this bug. If you are unable to change the version, please add a comment here and someone will do it for you.

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. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists.

Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs:
http://docs.fedoraproject.org/release-notes/

The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Bug Zapper 2008-06-17 02:22:59 UTC

Fedora 7 changed to end-of-life (EOL) status on June 13, 2008. 
Fedora 7 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.

Thank you for reporting this bug and we are sorry it could not be fixed.