This was fixed in intrepid in version 0.5.11-4ubuntu1.
** Changed in: hal (Ubuntu)
Status: In Progress = Fix Released
--
[regression] hald ignores changes to files in /usr/share/hal/fdi and
/etc/hal/fdi
https://bugs.launchpad.net/bugs/304793
You received this bug notification because
** Changed in: hal (Ubuntu)
Importance: Undecided = High
Status: New = In Progress
--
[regression] hald ignores changes to files in /usr/share/hal/fdi and
/etc/hal/fdi
https://bugs.launchpad.net/bugs/304793
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/20180433/Dependencies.txt
--
[regression] hald ignores changes to files in /usr/share/hal/fdi and
/etc/hal/fdi
https://bugs.launchpad.net/bugs/304793
You received this bug notification because you are a member of Ubuntu
The root of the problem was a future timestamp of the fdi-cache:
-rw-r--r-- 1 root root 1039604 2024-07-20 02:45 fdi-cache
after deleting it, everything works fine again. The future time probably
came from a PM_TRACE, which I have activated, since the S2Mem is f*ing
instable since intrepid ...
** Changed in: hal (Ubuntu)
Assignee: (unassigned) = Martin Pitt (pitti)
--
[regression] hald ignores changes to files in /usr/share/hal/fdi and
/etc/hal/fdi
https://bugs.launchpad.net/bugs/304793
You received this bug notification because you are a member of Ubuntu
Bugs, which is
