Bug 239953 - irda init script status not shown properly
Summary: irda init script status not shown properly
Alias: None
Product: Fedora
Classification: Fedora
Component: irda-utils   
(Show other bugs)
Version: 6
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Karsten Hopp
QA Contact:
Whiteboard: bzcl34nup
Depends On:
TreeView+ depends on / blocked
Reported: 2007-05-13 10:27 UTC by Jan ONDREJ
Modified: 2008-08-02 23:40 UTC (History)
1 user (show)

Fixed In Version: F-8
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-04-07 08:08:38 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Jan ONDREJ 2007-05-13 10:27:05 UTC
Description of problem:

Version-Release number of selected component (if applicable):
irda-utils-0.9.17-2.fc6 and I think also for Fedora 7 development

How reproducible:
sometimes (aprox every 5th try for me)

Steps to Reproduce:
1. service irda restart
2. service irda restart
3. ...
Actual results:

Expected results:

Additional info:
This script checks irattach status before it can write it. Please add an "sleep
0.1s" between these lines in your init script:

        daemon /usr/sbin/irattach ${DEVICE} ${ARGS}
        [ -f /var/run/irattach.pid ] && success $"irattach startup" || failure $
"irattach startup"

Working code looks like this:

        daemon /usr/sbin/irattach ${DEVICE} ${ARGS}
        sleep 0.1s
        [ -f /var/run/irattach.pid ] && success $"irattach startup" || failure $
"irattach startup"

May be it is wrong only for my USB irda dongle.
I am using irda DISCOVERY=yes in my sysconfig/irda config.

Comment 1 Bug Zapper 2008-04-04 07:14:19 UTC
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers

Comment 2 Jan ONDREJ 2008-04-07 05:41:12 UTC
I am not using IR connection over years and my IR receiver hardware is not
functional with my current hardware. I am unable to test this now.

Because this is not a critical bug and may be this was fixed in any later
fedora, I think this can be closed now.

Comment 3 Karsten Hopp 2008-04-07 08:08:38 UTC
ok, thanks for taking the time to answer. I'm closing this

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