Bug 711420

Summary: Bug: config.c:2721: config_dump: Assertion 0 failed; aborting.
Product: [Fedora] Fedora Reporter: Christoph A. <casmls>
Component: torAssignee: Enrico Scholz <rh-bugzilla>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: cassmodiah, erik, lmacken, rh-bugzilla
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-16 13:11:02 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Christoph A. 2011-06-07 13:12:17 UTC
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.

Comment 1 Erik Terwan 2011-08-01 19:46:33 UTC
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.

Comment 2 Christoph A. 2011-08-01 20:30:33 UTC
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.

Comment 3 Fedora End Of Life 2012-08-16 13:11:05 UTC
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