Description of problem: | # fstab-sync | error: libhal_ctx_init_direct: (null): (null) 'strace' does not tell something suspicious: | set_thread_area({entry_number:-1 -> 6, base_addr:0xb7fba6c0, limit:1048575, seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1, seg_not_present:0, useable:1}) = 0 | mprotect(0x4d81e000, 8192, PROT_READ) = 0 | mprotect(0x4efe7000, 4096, PROT_READ) = 0 | mprotect(0x4d6f7000, 4096, PROT_READ) = 0 | munmap(0xb7fbc000, 129544) = 0 | getpid() = 4005 | brk(0) = 0x8050000 | brk(0x8071000) = 0x8071000 | write(2, "error: libhal_ctx_init_direct: ("..., 46error: libhal_ctx_init_direct: (null): (null) | ) = 46 | exit_group(0) = ? Happens both with and without a running messagebus daemon and as you can see in the strace above, local configuration will not be read. Version-Release number of selected component (if applicable): hal-0.5.5.1-2.1 hal-0.5.2-2 How reproducible: 100%
Not a bug. You can't run fstab-sync from the command line since it requires env variables set up by hal to talk to hal directly (perhaps upstream should fix that error message).