seems, this bug has been 'unfixed' in hal 0.5.11-4ubuntu4 I did report it in https://bugs.launchpad.net/ubuntu/+source/hal/+bug/304793
For me it seems, a dpkg trigger isn't the appropriate way, as a future timestamped fdi-cache would only be deleted on a package upgrade or by hand. The init script at least should check for 'uncommon' timestamp on fdi-cache and delete it in that case ... regards, tom -- After an upgrade to intrepid, HAL prefers old fdi-cache to new FDI files https://bugs.launchpad.net/bugs/275825 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
