Can't edit torrc from within Vidalias' interface

A user reports for: Tor Browser Bundle (2.2.37-1)

Any attempt at editing and saving the torrc file via Vidalias' interface:

_Settings-->Advanced-->Edit current torrc-->OK_

fails with the popup message:

Error at line 1: ""

This happens even without editing the file.

I can reproduce this error on Windows 7 (64bit). You can edit the file manually with your favorite notepad. Tor accepts the changes, so I assume that the bug is within Vidalia.

added component::archived/vidalia easy owner::chiiph priority::medium resolution::fixed status::closed type::defect version::vidalia 0.2.19 labels

Removing the first two commented lines will allow you to save the file.

This is also present for tor-browser-gnu-linux-i686-2.2.37-1-dev-en-US

Replying to cypherpunks:

Removing the first two commented lines will allow you to save the file.

This is also present for tor-browser-gnu-linux-i686-2.2.37-1-dev-en-US

Any commented lines will result in the Error message

Trac:
Username: karulis

vidalia-torrc.patch

patch

Trac:
Username: karulis

Now when parsing we skip lines that are commentaries or empty.

Trac:
Username: karulis
Cc: N/A to karulis@wp.pl
Status: new to needs_review

This is obviously present in Vidalia 0.2.20, which is included in the browser bundles, bridge and relay bundles.

My torrc files contained comments all the time and Vidalia never cared, I wonder what has changed so it "cares" about them.

(I wanted to add myself as CC, too)

Trac:
Cc: karulis@wp.pl to karulis@wp.pl, bastik.public@gmx-topmail.de

Any update on this? Patch looks okay to me.

The patch looks also good to me and resolves the issue which is still present in the master branch (0.2.21).

Trac:
Username: onizuka
Cc: karulis@wp.pl, bastik.public@gmx-topmail.de to karulis@wp.pl, bastik.public@gmx-topmail.de, onizuka.xxxx@gmail.com
Keywords: N/A deleted, easy added

Trac:
Cc: karulis@wp.pl, bastik.public@gmx-topmail.de, onizuka.xxxx@gmail.com to karulis@wp.pl, bastik.public@gmx-topmail.de, onizuka.xxxx@gmail.com, erinn

Trac:
Username: meitar
Cc: karulis@wp.pl, bastik.public@gmx-topmail.de, onizuka.xxxx@gmail.com, erinn to karulis@wp.pl, bastik.public@gmx-topmail.de, onizuka.xxxx@gmail.com, erinn, meitarm+torproject.H6tsywSw7GkG1Mem@gmail.com

This has been merged to master. Sorry for the delay

Trac:
Resolution: N/A to fixed
Status: needs_review to closed

This is still an issue (TBB 2.3.25-5-osx-x86_64-en_US).

Trac:
Status: closed to reopened
Resolution: fixed to N/A

chiiph says this has been fixed in the code, but there is no release of Vidalia with the fix in it. He says he's not sure when there will be a new release.

I am on mac 10.6.8, and having the same error with line 1 problem while using the latest version of the tor browser bundle. How I can I fix this? Thanks

Trac:
Username: anic92

Replying to anic92:

I am on mac 10.6.8, and having the same error with line 1 problem while using the latest version of the tor browser bundle. How I can I fix this? Thanks

Take out the commented lines, I believe its the top two. This happens on some versions of vidalia. Let me know if this fixes it for you.

Trac:
Username: lance

Trac:
Username: lance
Status: reopened to needs_information

Why did you change the state to "needs_information"? "needs_information" reflects that the bug cannot be assessed without additional information about the bug (from the reporter[s]). This bug has been fixed in the code base, but it does not look like there will be a new release of Vidalia in the near future that contains the fix. As such, I'd say the bug is "fixed", although the fix is not readily available. Which is very sad.

You can either remove the commented lines, or select only the lines with changes and tick "apply only selected lines" (or whatever it's called in Vidalia).

The soon-to-be stable Tor Browser Bundle v3 will not have Vidalia any more.

Trac:
Status: needs_information to closed
Resolution: N/A to fixed

closed

mentioned in issue #7299 (closed)

mentioned in issue #7600 (moved)

mentioned in issue #7636 (closed)

mentioned in issue #7719 (closed)

mentioned in issue #8898 (closed)