Hide Forgot
Description of problem: tor coredumps when starting vidalia Version-Release number of selected component (if applicable): rpm -q tor tor-0.2.1.30-1400.fc14.x86_64 rpm -q vidalia vidalia-0.2.12-1.fc14.x86_64 same problem occurred with tor 0.2.1.29 How reproducible: always once: After tor crashes, I start it again with /etc/init.d/tor start -> start vidalia -> vidalia connects to tor -> works fine Steps to Reproduce: 1. configure tor to be started at bootup and have ControlPort + Password set 2. configure Vidalia to connect to tor using a password 3. boot your machine 4. start vidalia 5. tor crashes (core dump) Actual results: tor terminates Expected results: vidalia should connect to tor Additional info: Tor[9405]: Couldn't find $HOME environment variable while expanding "~/.tor" Tor[9405]: Failed to expand filename "~/.tor". Tor[9405]: config_dump(): Bug: Failed to validate default config. Tor[9405]: Bug: config.c:2721: config_dump: Assertion 0 failed; aborting.
Same problem here. Temporary fix: add export HOME=/var/lib/tor just before the line with start_daemon $prog --PIDFile "$pidfile" --RunAsDaemon 1 $TOR_OPTS in /etc/rc.d/init.d/tor.
using https://admin.fedoraproject.org/updates/policycoreutils-2.0.85-30.1.fc14 https://admin.fedoraproject.org/updates/policycoreutils-2.0.85-30.2.fc14 fixed this issue too, but these updates introduced other problems and were unpushed.
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping