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 ... nevertheless, I regard this behavior as a bug in hal. It is or has been discussed there for Debian and Ubuntu, so there should: http://www.mail-archive.com/[EMAIL PROTECTED]/msg572726.html http://groups.google.com/group/linux.debian.bugs.dist/browse_thread/thread/83d30ea7b629e4a4 and here you find a patch (which is secure, as it deletes the fdi-cache on every hal-start, but increases boot-time): http://groups.google.com/group/linux.debian.bugs.dist/attach/b524a9234fe6547d/hal .fdi-cache.debdiff?part=3 regards, tom -- [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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
