I had already forgotten about this bug since the problem it caused me
was fixed elsewhere. But yes, it still exists in the current version of
hal in hardy. The following fdi file shows the problem. Needs to be put
into /etc/hal/fdi/information:
<?xml version="1.0" encoding="UTF-8"?>
<deviceinfo version="0.2">
<device>
<match key="@info.parent:storage.cdrom.cdr" bool="true">
<match key="block.is_volume" bool="true">
<merge key="foo" type="string">foo</merge>
<merge key="bar" type="uint64">12345</merge>
</match>
</match>
</device>
</deviceinfo>
In this form the file is completely ignored. Once you remove (or comment
out) the line <merge key="bar" type="uint64">12345</merge> the property
foo appears in the volume properties when you insert a cdrom. This is
independent of the name or value of the key. I remember that other types
such as int continued working. Also in the current hal documentation the
type is still present with the exact same name and some properties like
volume.size of block devices still use it.
--
hal ignores fdi files containing uint64 merges
https://bugs.launchpad.net/bugs/116264
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
