sys-apps/hal-0.5.11-r6 fails to start Reproducible: Always Steps to Reproduce: 1. start hal manually or via init.d 2. FAIL Actual Results: Jan 28 16:38:48 uptempo hald[19254]: 16:38:48.565 [I] hald.c:669: hal 0.5.11 Jan 28 16:38:48 uptempo hald[19254]: 16:38:48.565 [I] hald.c:678: Will daemonize Jan 28 16:38:48 uptempo hald[19254]: 16:38:48.565 [I] hald.c:679: Becoming a daemon Jan 28 16:38:48 uptempo hald[19255]: 16:38:48.566 [I] hald_dbus.c:5381: local server is listening at unix:abstract=/var/run/hald/dbus-KRYXbDZJ68,guid=f6344da5b92decafb4b17fc949807c08 Jan 28 16:38:48 uptempo hald[19255]: 16:38:48.604 [I] hald_runner.c:301: Runner has pid 19256 Jan 28 16:38:48 uptempo hald[19255]: 16:38:48.604 [I] hald_runner.c:182: runner connection is 0x832d7d8 Jan 28 16:38:48 uptempo hald[19255]: 16:38:48.605 [W] osspec.c:373: Unable to open /proc/mdstat: No such file or directory Jan 28 16:38:48 uptempo hald[19255]: 16:38:48.609 [I] mmap_cache.c:126: Regenerating fdi cache.. Jan 28 16:38:48 uptempo hald[19255]: 16:38:48.631 [I] mmap_cache.c:104: In regen_cache_cb exit_type=0, return_code=1 Jan 28 16:38:48 uptempo hald[19255]: 16:38:48.631 [E] mmap_cache.c:153: fdi cache regeneration failed! Jan 28 16:38:48 uptempo hald[19255]: 16:38:48.632 [I] mmap_cache.c:156: fdi cache generation done Jan 28 16:38:48 uptempo hald[19255]: 16:38:48.632 [I] mmap_cache.c:274: cache mtime is 1233087203 Jan 28 16:38:48 uptempo /etc/init.d/hald[18379]: ERROR: hald failed to start Expected Results: hal should start There is only one empy policy file in the polices folder (without it it fails the same way) Actually this bug should have severity critical since when one updates and reboots (with an automatically started login manager) X inputs dont work and since X grabs keyboard and mouse you need to hardreset which may lead to data loss.
Maybe it's due a missing or with wrong permissions /var/cache/hald directory Please look to bug 178526
please also paste emerge --info.
Creating /var/cache/haldaemon with haldaemon:haldaemon as owner:group solved the problem. hal does work as intended now. I'm adding a depend on #178526 since this both is because the hal ebuild does not create some directories.
Oh, it is /var/cache/hald not /var/cache/haldaemon - however the other bug has problems with /var/lib/cache/hald
emerge --info was requested and hasn't been provided.