Bug 210868 - Error in udev rule
Error in udev rule
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: openct (Show other bugs)
rawhide
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ville Skyttä
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2006-10-16 08:52 EDT by Torsten Rausche
Modified: 2009-06-27 11:42 EDT (History)
2 users (show)

See Also:
Fixed In Version: 0.6.9-3
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-10-16 14:26:16 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Torsten Rausche 2006-10-16 08:52:33 EDT
Description of problem:
Udev is moaning while loading openct's rule. The line mentioned in the output is
related to PCMCIA. I do not have PCMCIA hardware and therefore I have no
corresponding packages installed.

udevd: add_to_rules: invalid BUS operation
udevd: add_to_rules: invalid rule '/etc/udev/rules.d/60-openct.rules:49'


Version-Release number of selected component (if applicable):
openct 0.6.9-2.fc6
udev   095-14


How reproducible:
Always.


Steps to Reproduce:
1. Setup a system without PCMCIA.
2. Look at the screen ouput while booting.

  
Actual results:
Udev shows error messages related to openct.


Expected results:
No error messages.
Comment 1 Ville Skyttä 2006-10-16 13:35:44 EDT
Hm, I have a similar system (without PCMCIA), but it's a FC5 with udev 084 and 
that udev doesn't seem to mind it.  I have no FC6testX system available at the 
moment to test with.

Anyway, looks like the culprit line 49 in /etc/udev/rules.d/60-openct.rules 
may have a simple bug: does changing 'BUS=' to 'BUS==' in it help?
Comment 2 Torsten Rausche 2006-10-16 14:03:19 EDT
Yes, this seems to fix it.
Comment 3 Ville Skyttä 2006-10-16 14:26:16 EDT
Fixed in 0.6.9-3.fc6 which will hit the repository soonish.

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