Description of problem: When you run vidalia & tor is connecting, tor won't be able to connect due to a permission-issue on /var/lib/tor Version-Release number of selected component (if applicable): 0.3.1 How reproducible: All the time from the moment that you first install vidalia & tor. Steps to Reproduce: 1. Open terminal-window. 2. Login as root (su-) 3. Install vidalia and tor. 4. Run vidalia from Program ->Internet ->Vidalia 5. As Vidalia tries to setup and connect it fails. A fix to this is to do: chmod a+x /var/lib/tor Now run vidalia again. Problem solved. Reproducible: Steps to Reproduce:
Priority: Normal => HighCC: (none) => kristoffer.grundstrom1983
Keywords: (none) => TriagedAssignee: bugsquad => juan.baptiste
Obviously this problem is caused by: a) the tor server being installed to run as user 'toruser' b) vidalia using the /etc/tor/torrc, even if running as a different user So IMHO, the permissions for /var/lib/tor are correct, but vidalia must not use /etc/tor/torrc, as this is for the server. Unfortunately, this seams not to supported by vidalia (see man-page).
CC: (none) => h.goebel
This problem still exists. Here's output from the log. jun 18 12:28:18.542 [Error] set_options(): Bug: Acting on config options left us in a broken state. Dying.
Mageia 3 changed to end-of-life (EOL) status 4 months ago. http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLD
Problem still persists.
Resolution: OLD => (none)Severity: minor => normalPriority: High => NormalStatus: RESOLVED => REOPENEDHardware: All => x86_64Version: 3 => 4
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 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 Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
Status: REOPENED => RESOLVEDResolution: (none) => OLD
Any chance of getting this fixed in the next stable version? It still isn't fixed.
Assignee: juan.baptiste => jani.valimaa
Reopening as per comment 7 (assuming it was tested in Mageia 5).
Resolution: OLD => (none)Version: 4 => 5Status: RESOLVED => REOPENED
(In reply to Rémi Verschelde from comment #8) > Reopening as per comment 7 (assuming it was tested in Mageia 5). Affirmative.
Summary: /var/lib/tor has gotten the wrong priveligies so vidalia doesn't connect => /var/lib/tor is assigned to be runned as toruser so this prevents so vidalia to connect during start-up
Summary: /var/lib/tor is assigned to be runned as toruser so this prevents so vidalia to connect during start-up => /var/lib/tor is assigned to be runned as toruser so this prevents vidalia to connect during start-up
It's already fixed in mga5 [1]. Closing as FIXED. [1] http://svnweb.mageia.org/packages?view=revision&revision=793921
Status: REOPENED => RESOLVEDResolution: (none) => FIXED
Actually, I'll reopen this again and will push a new release which fixes the default configuration file (see comment 1).
Resolution: FIXED => (none)Status: RESOLVED => REOPENED
Pushed new release to core/updates_testing. Please test that it works. Event log will show after startup which port to use as SOCKS5 proxy. In previous release Vidalia shows in event log, that it can't write new settings to /etc/tor/torrc after modifying and saving. RPM/SRPM: vidalia-0.3.1-7.1.mga5 Suggested advisory: #### New vidalia release fixes default data directory and Tor config file location. New data directory location is $HOME/.vidalia/ and default Tor configuration file is $HOME/.vidalia/torrc. ####
Assignee: jani.valimaa => qa-bugsCC: (none) => jani.valimaaHardware: x86_64 => All
https://check.torproject.org/ shows if Vidalia + Tor is working correctly.
Awaiting your tests Kristopher
I don't know if it matters that I tested this in a VM of Mageia 5, but the issue seems to be fixed. Can you push the update to Core Updates? Closing as RESOLVED FIXED. If someone should encounter this problem again, please feel free to reopen this report again with an added comment.
Resolution: (none) => FIXEDStatus: REOPENED => RESOLVED
Thanks but reopening. It won't be fixed until it's been pushed to updates from updates testing. Which arch did you test btw i586 or x86_64?
Status: RESOLVED => REOPENEDResolution: FIXED => (none)
(In reply to claire robinson from comment #16) > Which arch did you test btw i586 or x86_64? x86_64
Trying Mageia 5 x64 real hardware. Following Comment 0 to set things up, I urpmi'd vidalia which pulled in:- $MIRRORLIST: media/core/release/tsocks-1.8-0.beta5.15.mga5.x86_64.rpm $MIRRORLIST: media/core/release/lib64tsocks1-1.8-0.beta5.15.mga5.x86_64.rpm $MIRRORLIST: media/core/release/vidalia-0.3.1-7.mga5.x86_64.rpm $MIRRORLIST: media/core/release/tor-0.2.5.12-1.mga5.x86_64.rpm the essential being 'vidalia-0.3.1-7.mga5'. 4. Run vidalia from Program ->Internet ->Vidalia 5. As Vidalia tries to setup and connect it fails. Except it did not... The little Status display of Vidalia showed after initialisation: "Connected to the Tor network. We were able to successfully establish a connection to the Tor network. You can now configure your applications to use the Internet anonymously. The Tor Software is running. You are currently running version ... 0.2.5.12 of the Tor software". The Message Log ended: "[Notice] Bootstrapped 90%: Establishing a Tor circuit [Notice] Tor has successfully opened a circuit. Looks like client functionality is working. [Notice] Bootstrapped 100%: Done" But trying the link given in Comment 13: https://check.torproject.org/ from 2 different browsers yielded a page "Sorry. You are not using Tor." I seem to remember you have to fiddle something in browser preferences to get them to work with Tor. Back after researching that.
CC: (none) => lewyssmith
set browser to user a socks5 proxy on localhost with port 3128 (IIRC)
The Tor site offers a page of heavy advice: https://trac.torproject.org/projects/tor/wiki/doc/TorifyHOWTO/WebBrowsers After "Tor has successfully opened a circuit. Looks like client functionality is working" from Vidalia, I tried manually configuring Firefox (Preferences-Advanced-Network-Configuration-Proxy configuration by hand)) in all sorts of ways: HTTP proxy localhost/8118; use this for all protocols; localhost/8118 for SSL/FTP, localhost/9050 for SOCKS v5; SOCKS v5 alone localhost/3128 or 8118 or 9050; all these variations with 127.0.0.1 . Using the Tor test URL, all led to "The proxy server is refusing connections". Cancelling proxy definitions yielded the "Sorry. You are not using Tor." page. Since Vidalia seems to be starting OK (despite the bug), is that sufficient for testing the update? I would prefer a successful Tor browser connection, though.
In the absence of a response to my last question (above)... Testing Mageia 5 x64 (continued) Updated from Updates Testing to: vidalia-0.3.1-7.1.mga5 Run vidalia from Program ->Internet ->Vidalia Starts fine. Status window ends "Connected to the Tor Network. We were able to successfully establish a connection to the Tor network. You can now configure your applications to use the Internet anonymously". Message log ends "Bootstrapped 80%: Connecting to the Tor network. Bootstrapped 90%: Establishing a Tor circuit. Tor has successfully opened a circuit. Looks like client functionality is working. Bootstrapped 100%: Done" Note that the Message Log early on contained: Warning Fixing permissions on directory /home/lewis/.vidalia I cannot recall whether this happened before the update, but looks to be part of it. IMPORTANT INFORMATION FOR FOLLOWERS I also noticed at the start of the Message Log two lines which look important for configuring (say) Firefox: Opening Socks listener on 127.0.0.1:0 Socks listener listening on port 54456 So back to configuring Firefox: Preferences->Advanced->Network->Connection->Configuration-Proxy configuration by hand and configuring *just* the SOCKS v5 line with 127.0.0.1 port 54456 the test URL https://check.torproject.org/ *worked*: "Congratulations. This browser is configured to use Tor." Maybe this information was evident in the log before the update; note it well. And be careful not to confuse it with the following Control listener port (I did initially, and the test URL landed up on the Tor failure page after a *very* long wait. But at least the 'proxy server refusing connections' issue vanished). So the update is OK.
Whiteboard: (none) => MGA5-64-OK
Well done Lewis. Validating.
Keywords: (none) => validated_updateWhiteboard: MGA5-64-OK => has_procedure MGA5-64-OKCC: (none) => sysadmin-bugs
CC: (none) => davidwhodginsWhiteboard: has_procedure MGA5-64-OK => has_procedure MGA5-64-OK advisory
An update for this issue has been pushed to Mageia Updates repository. http://advisories.mageia.org/MGAA-2015-0178.html