I have issue with latest version of vscode==1.75.1.
I'm ussing Microsoft Dev Containers extension, and inside dev container I cannot run termminal .
Error is: The connection to the terminal's pty host process is unresponsive, the terminals may stop working.
I'm traying to find any olution for this problem.
I done uninstall, remove all filles related to vscode, install agan with yay -S visual-studio-code-bin and still have issue.
I want to install specific version of visual-studio-code-bin==1.74.3, how to install with yay -S?
p.s. This was after I updated system.
Thanks!
Related
I wanted to update my Visual code studio theme I've created when I went to my terminal to update my theme. I put in the words. Yo code is showed an error that it couldn't be installed or found. I have installed the generator a few weeks ago. When I tried to reinstall it it told me to install it as an administrator, I did that when the process is complete I entered the same word. Yo code did not work so I decided to delete it all together, then reinstall it, but it didn't work. I have node installed and MPM I did the procedures correctly, but the generator does not work at all.
I tried reinstalling the generator, through node and NPM both as an administrator, but it did not work at all. I did a lot of research regarding that is shell, but there is no solution that kind of fix that issue I'm having.
I am trying to install some packages using Bun, but I am running into trouble:
$ bun install
error: Failed to initialize network thread: SystemOutdated.
HTTP requests will not work. Please file an issue and run strace().
Is there any known fix to this problem?
Bun leverages some network features which are only available on newer versions of WSL. You can usually fix these issues by updating your WSL version:
wsl --update
And restart your WSL VM:
wsl --shutdown
Also note that Bun only supports WSL2, so you would need to upgrade your WSL version to 2. See the Microsoft guide on updating from WSL1 to WSL2.
Furthermore, if you are getting an error for NotSameFileSystem, then you need to defer to using a different style for installations. This can be done by adding the --backend=copyfile to the end of your commands.
Running Windows 11, WSL2, Ubuntu 20.04. Been developing with VSCode over a year. I regularly run apt update and apt upgrade without any problem. Today after running apt upgrade I can no longer open VSCode. I get the following error
node:internal/modules/cjs/loader:990
throw err;
^
Error: Cannot find module '\wsl.localhost\Ubuntu-20.04\mnt\c\Users\JimD\AppData\Local\Programs\Microsoft VS Code\Code.exe'
at Function.Module._resolveFilename (node:internal/modules/cjs/loader:987:15)
at Module._load (node:internal/modules/cjs/loader:832:27)
at Function.c._load (node:electron/js2c/asar_bundle:5:13343)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
at node:internal/main/run_main_module:17:47 {
code: 'MODULE_NOT_FOUND',
requireStack: []
That is the correct path to the VSCode exe, but I am not sure about the \wsl.localhost\Ubuntu-20.04 part
I rolled back my wsl to an month old backup and confirmed VSCode ran fine. Ran apt update and upgrade on that and get the same error.
Does anyone know how to fix this?
Starting from a functioning backup of the WSL image, I manually installed each packaged listed from apt list --upgradable. Turns out it is the upgrade from systemd-genie 2.3 to 2.4 that is causing the problem.
If I upgrade every other package, VSCode still loads. When I upgrade systemd-genie to 2.4 and restart my laptop, VSCode will not load giving the error in the original post.
edit /usr/lib/binfmt.d/WSLInterop.conf, change flag PF to F, reboot wsl seems able to let you run code again, but not sure whether any other side-effects exists.
My final solution was to just not use systemd. With the release of Windows 11, a new feature has been added to WSL to runs scripts on WSL startup. This feature is now also available to Windows 10 users if you install WSL from the Microsoft Store (requires KB5020030, which should be available under Optional Updates).
create the file /etc/wsl.conf and the following
[boot]
command = bash /etc/[path to startup script]
in my case I used the path "/etc/wsl-services-start.sh" This shell script contains only
service apache2 start
service mysql start
Starting apache2 and mysql was the only thing I needed systemd for, so this works fine for me.
I've been trying to set up the vscode code . shortcut to work in WSL. Following the instructions from the vscode website, I reinstalled vscode in windows, reinstalled the Remote-Wsl extension, made sure it was in my System Path, and tried running code . in the WSL linux distro terminal. I get the message instructing me to install it on the windows side, and asking me if I want to continue. I hit yes, but it doesn't create the code server folder in my home directory. Typing code . again does the same thing.
Does anyone know why this may be?
This is the output text:
To use Visual Studio Code with the Windows Subsystem for Linux, please install Visual Studio Code in Windows and uninstall the Linux version in WSL. You can then use the code command in a WSL terminal just as you would in a normal command prompt.
Do you want to continue anyway? [y/N]
The error message isn't just pointing out that you need to install the Windows version, but it indicates that you have the Linux version installed in WSL and should remove it.
From that, it sounds like at some point you may have installed the Linux version of VSCode in WSL, and that one is taking priority. You'll need to uninstall it in order to run the Windows version of VSCode with the "Remote - WSL" extension.
You don't mention what distribution you are running, but if it is Ubuntu, try:
sudo apt remove code # or
sudo apt remove code-insiders
Also see the uninstall doc from Microsoft.
I am in the process of setting up a Linux Based AMPPS LAMP box for local web development needs before the projects go live. I have been following this installation guide for AMPPS website, on a fresh install of CentOS: https://www.ampps.com/wiki/Installing_AMPPS_on_Linux#Important_Locations
The following is stated in the instructions:
First Run of AMPPS When you run AMPPS for the first time make sure your Internet connection is active. Note: AMPPS doesn't support proxy
yet. So you must have a Direct Internet Connection.
Now open /usr/local/ampps/Ampps from Explorer, this will take some
time as it is setting up AMPPS for your Linux. If you are using Ubuntu
OS then you have to start Ampps from terminal with sudo privilege.
cd /usr/local/ampps
sudo ./Ampps
Upon entering ./Ampps in as root, the terminal returns the following:
./Ampps: error while loading shared libraries: libXrender.so.1: cannot open shared object file: no such file or directory
I have done a little of a search and turned up basic fixes, such as:
yum install libXrender.so.1
Even with the libraries installed it throwing the same error.
Any help would be great,
Sorry if my post lacks anything its my first :)
Thanks in advance,
Jon
This seemed to do the trick guys, Thanks anyways :D
$ yum groupinstall "X Window System" "Desktop" "Desktop Platform" "Fonts"