rofl0r / rofl0r/proxychains-ng
VSCode failed to launch with proxychains after upgrading to 1.49
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 10.7k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
OS: Debian Sid
proxychains version: 4.14
VSCode version: 1.49.1
A few days ago I did a system-wide package upgrading and since then Joplin (a note application, with no proxy support) could not open VSCode as external editor. Then I tried run VSCode with proxychains directly and it failed to launch.
On another machine running Ubuntu 20.04, VSCode 1.47 worked fine with proxychains 4.14, but after upgrading to 1.49 it could not launch any more.
Update: I've downgraded to VSCode 1.48.2 and it works fine on both machines.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the launch failure with proxychains 4.14 and VSCode 1.49.1 on Debian Sid or Ubuntu 20.04, then compare it with the reported-working VSCode 1.48.2. Done means identifying and fixing the compatibility regression so VSCode launches through proxychains again.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, debian, vscode
- Domain
- operating-systems, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100