#11606: An issue after new scheduler merging -----------------------------+---------------------------- Reporter: Giova84 | Owner: nobody Type: bug | Status: assigned Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1/Development Resolution: | Keywords: Blocked By: | Blocking: Has a Patch: 0 | Platform: All -----------------------------+---------------------------- Comment (by Giova84): Ok, I've built Tor as you suggested. But now I am totally unable to use Tor. I try to explain the new behaviour: I launch this new compiled Tor (with libposix_error_mapper flags) and when I launch Tor i got: {{{ Dec 13 21:16:51.502 [warn] Directory /boot/home/.tor cannot be read: No such file or directory Dec 13 21:16:51.502 [warn] Failed to parse/validate config: Couldn't access/create private data directory "/boot/home/.tor" }}} But in the torrc config file the datadir is set as "DataDirectory /boot/home/.tor". Well, so I make the .tor directory and now: {{{ Dec 13 21:17:15.419 [warn] Fixing permissions on directory /boot/home/.tor Dec 13 21:17:15.000 [warn] State file "/boot/home/.tor/state" is not a file? Failing. Dec 13 21:17:15.000 [err] set_options(): Bug: Acting on config options left us in a broken state. Dying. }}} But there is no "state" file inside that directory. So I've tried to put, inside the .tor directory, the "state" file from my backup, and now tor correctly starts, but it stucks at {{{ Bootstrapped 5%: Connecting to directory server }}} Note: I've also attempt to build Tor using the --with-tor-user=username --with-tor-group=groupname but these issues are always here. I've also tried to launch tor using the "--user" flags, but this doesn't help. All works fine (as before) if I use the old Tor binary (without the libposix_error_mapper flags) In anyway I've saved a debug report, which I attach to this ticket: hope this help you to figure out the issue. -- Ticket URL: <https://dev.haiku-os.org/ticket/11606#comment:8> Haiku <https://dev.haiku-os.org> Haiku - the operating system.