Skip to content
This repository has been archived by the owner on Dec 11, 2019. It is now read-only.

Controlport blocks tor connection after browser restart #14503

Closed
srirambv opened this issue Jun 21, 2018 · 3 comments
Closed

Controlport blocks tor connection after browser restart #14503

srirambv opened this issue Jun 21, 2018 · 3 comments
Labels
bug feature/tor QA/checked-Linux QA/checked-macOS QA/checked-Win64 QA/test-plan-specified release-notes/exclude
Milestone
0.23.x (Release C...

Comments

@srirambv
Copy link
Collaborator

srirambv commented Jun 21, 2018 •
edited
Loading

Test Plan

  1. Clean install 0.23.x
  2. Ensure tor is connected upon first launch and doesn't show connection failed modal
  3. Relaunch the browser from console
  4. Ensure console doesn't log the following message
tor: control socket error: Error: connect ECONNREFUSED 127.0.0.1:51071
tor: control socket closed early

Description

Controlport blocks tor connection after browser restart

Steps to Reproduce

Actual result:
Doesn't connect to tor after browser restart
Expected result:
Should connect to tor after restart

Reproduces how often:

Brave Version

about:brave info:

Reproducible on current live release:

Additional Information
@srirambv srirambv added this to the 0.23.x (Beta Channel) milestone Jun 21, 2018
@riastradh-brave riastradh-brave mentioned this issue Jun 21, 2018
Merged
10 tasks
@srirambv srirambv changed the title Cookie control blocks tor connection after browser restart Controlport blocks tor connection after browser restart Jun 21, 2018
@diracdeltas
Copy link
Member

closed by #14502

@kjozwiak
Copy link
Member

@sri can you add the STR in the original issue and mark it as QA/test-plan-specified? I manually added this issue into our manual passes.

This was referenced Jun 22, 2018
Closed
Closed
Closed
@LaurenWags
Copy link
Member

LaurenWags commented Jun 22, 2018 •
edited by GeetaSarvadnya
Loading

Verified with macOS 10.12.6 using

  • 0.23.14 f4da855
  • Muon 7.1.1
  • libchromiumcontent 67.0.3396.87

Verified on Ubuntu 17.10 x64

  • 0.23.14 - f4da855
  • Muon - 7.1.1
  • libchromiumcontent - 67.0.3396.87

Verified on Windows 10 x64
• 0.23.16 2042c45
• Muon 7.1.1
• libchromiumcontent: 67.0.3396.87

@kjozwiak kjozwiak mentioned this issue Jun 25, 2018
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug feature/tor QA/checked-Linux QA/checked-macOS QA/checked-Win64 QA/test-plan-specified release-notes/exclude
Projects
None yet
Milestone
0.23.x (Release Channel)
Development

No branches or pull requests
6 participants
@diracdeltas @kjozwiak @srirambv @LaurenWags @btlechowski @GeetaSarvadnya