Bug 151467 - hidd needs to be started in runlevels 3 and 5 (and not 6) for USB/Bluetooth mice and keyboards
Summary: hidd needs to be started in runlevels 3 and 5 (and not 6) for USB/Bluetooth m...
Keywords:
Status: CLOSED DUPLICATE of bug 155831
Alias: None
Product: Fedora
Classification: Fedora
Component: bluez-utils
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: David Woodhouse
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: FC4Target
TreeView+ depends on / blocked
 
Reported: 2005-03-18 10:28 UTC by Reuben Farrelly
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-05-02 14:52:04 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Reuben Farrelly 2005-03-18 10:28:22 UTC
I am using a Logitech MX900 USB/Bluetooth mouse, which unfortunately does not
work with X upon bootup.  I have to log in, alt-f2, launch a gnome-terminal and
then manually activate /etc/init.d/hidd .

Current init script looks like this:

# chkconfig:    - 26 89

This really should be:     - 235 89

Not too sure quite why one would want to run hidd in runlevel 6!

If a system has the bluez-utils package installed, it should at least start in a
runlevel where it's services are required.
This may also include runlevel 3 (such as when there is a USB/Bluetooth keyboard).

Current bluez-utils is 2.15-4.

Comment 1 Reuben Farrelly 2005-04-26 09:31:32 UTC
Oops.  Ok I got that a bit wrong...

But I still think the statement should be:

# chkconfig 5 26 89

at the very least.  If the user has a bluetooth mouse or keyboard and therefore
requires hidd, they are almost certainly going to want it to run under X
(runlevel 5).


Comment 2 Miloslav Trmač 2005-05-02 14:52:04 UTC

*** This bug has been marked as a duplicate of 155831 ***


Note You need to log in before you can comment on or make changes to this bug.