Bug 239212 - typo in ide-drives.fdi
Summary: typo in ide-drives.fdi
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: hal   
(Show other bugs)
Version: 4.4
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Richard Hughes
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-05-06 06:02 UTC by John Newbigin
Modified: 2012-06-20 15:59 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-06-20 15:59:24 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description John Newbigin 2007-05-06 06:02:25 UTC
Description of problem:
hald --verbose=yes reports:
15:50:28.722 [I] device_info.c:1160: scan_fdi_files: Processing file
'ide-drives.fdi'
15:50:28.722 [E] device_info.c:803:
/usr/share/hal/fdi/20freedesktop/ide-drives.fdi:50:2: Element <device> can only
be inside <deviceinfo>
15:50:28.722 [E] device_info.c:711: Aborting parsing of document
15:50:28.722 [E] device_info.c:1091: Error parsing XML document
/usr/share/hal/fdi/20freedesktop/ide-drives.fdi at line 51, column 2 :
mismatched tag


Version-Release number of selected component (if applicable):
hal-0.4.2-4.EL4

How reproducible:
Every time

Steps to Reproduce:
1. hald --verbose=yes --daemon=no 2>&1 | grep Error
2.
3.
  
Actual results:


Expected results:


Additional info:

Line 51 has
<device>
but should have
</device>

Comment 1 Jiri Pallich 2012-06-20 15:59:24 UTC
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.


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