[tor-bugs] #10500 [Tor Launcher]: new torbutton 1.6.5.2 says Tor is down when accessing remote 'tor' relay daemon

[Tor Bug Tracker & Wiki]

#10500: new torbutton 1.6.5.2 says Tor is down when accessing remote 'tor' relay
daemon
------------------------------+-------------------
     Reporter:  starlight     |      Owner:  brade
         Type:  defect        |     Status:  new
     Priority:  normal        |  Milestone:
    Component:  Tor Launcher  |    Version:
   Resolution:                |   Keywords:
Actual Points:                |  Parent ID:
       Points:                |
------------------------------+-------------------

Comment (by starlight):

 Thank you for the help and information!

 The config here didn't have the last two "network.proxy" lines
 and port is 9150 instead of 9050, but I don't believe
 this was an issue--made no difference.

 However, I did find that when following the procedure
 to produce the trace the TorButton icon magically
 went green.  Well not so magically.  What appears to
 have been the problem is I was starting my little
 'go_tff' script (attached) from the "Run" dialog in
 KDE rather than from a console window.  So it appears
 that whatever KDE does for stdin/stdout/stderr is
 causing TorButton grief of some kind.  Possibly this
 should be addressed as it does not seem an unusual
 idea to run directly from KDE.

 I'm also attaching the trace output, though it
 shows a successful start.

 Once question I have now is that the "New Identity"
 option on TorButton is greyed out.  Am I stuck
 stop/starting Firefox now?  Before I would run
 "New Identity" and then separately issue the
 new identity action in the relay by invoking
 "New Identity" from Vidalia running on a different
 machine.  I suppose I can put the FF run in a loop
 so that it will restart immediately whenever exited.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/10500#comment:8>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online