So I don't use the linux desktop. I ssh into the box and run code there but the display is on my windows box. If something happens to the windows machine (example forced update and reboot) when I log back into the Linux machine, code is still running. How do I retrieve/restore the gui?
Related
i'm using remote-ssh VSC extension to run python files from windows on remote Ubuntu VPS
The problem is, i cant run code with tinkter or some commands like xeyes
They seems running, but there is no window displaying the result appearing.
What should i look at Local and server sides to fix this?
Got it. I need to run Xming on local machine in parallel with vscode. This way xming open window with graphic content in it
I'm working on some tutorials and trying to do something, but no idea if it can be done. I am using windows terminal in Windows 10. I have an Ubuntu virtual machine running.
I'd like to:
Open Windows terminal
SSH into the Linux Virtual Machine
Type in the code . command and have it open a version of VS Code on my Windows PC that is working on the folder in the Ubuntu VM.
I tried install code locally and on the command line in the other machine, but it doesn't work. I am sure there are other ways to do this but wanted to explain how I was doing it to show I at least tried something. Thanks for your help.
It's not quite as easy as the code . technique you get with the Remote - WSL extension, but Microsoft also provides a Remote - SSH extension that can be used to directly access the remote machine (without requiring WSL in-the-middle).
Once the Remote - SSH extension is installed in VSCode (and it may have already been installed in an extension pack with the WSL extension), and you have installed an OpenSSH client in Windows, there are several ways to access files on the remote host through SSH:
From the Command Palette (Ctrl+Shift+P), type Remote SSH to filter on those commands. From Connect to Host, you can add a new configuration, etc.
From the Activity Bar on the left, select the Remote Explorer icon, then in the dropdown at the top, select SSH Targets. You can add hosts here through the + icon.
There's a direct shortcut to Open a Remote Window at the far left of the status bar. This will give you similar filter options on the Command Palette as above.
Once a host is configured, you can browse it just as (well, almost) if it were local, open files, edit, etc. The one thing you can't do (as far as I'm aware) is any type of sudo/su editing on files that you don't have permissions to directly.
Full details in the VSCode docs here.
I installed VS Code in windows, but it comes up as running under WSL Ubuntu 18.04.
I don't want to run in the linux subsystem, but in windows proper.
Uninstalling and reinstalling does not change this.
Uninstalling and deleting all vscode file and folders in /users does not change this.
Try going to the bottom left of your window and press on the WSL: Ubuntu-18.04 button.
After pressing the button, go to the top center of the window and choose Close Remote Connection.
After that, VS Code should stop auto-connecting to the WSL Ubuntu system every time when you open it (I tested myself and it worked on my computer).
I'm Installing oracle Solaris 86x64 operating system in my PC. it was complete installation without any errors. In the final step of the installation the GUI window is not opening. If I restart the PC it is booting and Not able to go beyond the black screen. But, I can ping the system from another Command prompt. Is there drivers to be install ? Because of this I'm not able go into the system.
Yesterday I installed Teamviewer 7 on my Centos 5.8 desktop. After a reboot, am not able to see the login screen. Only a blue color screen is visible.
I read https://superuser.com/questions/403548/os-x-stuck-at-blue-screen-after-installing-teamviewer-host-and-rebooting?rq=1
But how do I do that on Centos?
I know that to login to Single User Mode, we need to press a key while the os boots up. And then type single in the cmd. And then?
Once in Single User Mode, you can try to remove TeamViewer from your system.
For example, if you have installed TeamViewer by running the rpm -ivh teamviewer_linux.rpm command, you can run the rpm -e teamviewer_linux command to uninstall it.
I don't think that the Mac OS link you've referred to can be very useful in your case.
If you peek into the teamviewer_linux.rpm (for example by running the command rpm -qpl teamviewer_linux.rpm) you won't find any "Launch Agents and Daemons", since on CentOS TeamViewer is wrapped around a Windows Emulator (wine).
By default the TeamViewer files gets installed in the /opt/teamviewer folder; the only exception is the startup script /usr/bin/teamviewer7.
Finally, the rpm post-installation script does nothing more and nothing less than create a desktop icon and add a menu entry, so I can't really understand how the TeamViewer installation could have broken your system.