I have recently installed Mobaxterm on my Window's 10 machine after I removed the "Ubuntu" sub system.
And then I re-installed Mobaxterm using scoop but it does not work properly.If I open any session/terminal it just closed immediately and never opens up. Any suggestion are welcome.
Related
This is a strange one, I've had it occur a few too many times and it's difficult to give a title to, but recently on a number of occasions when I try to open one of my existing sessions (VM or Server doesn't matter) the session doesn't open, it's just a black terminal screen with nothing on it, but my Windows task bar disappears, sometimes it ends up in the MobaXterm terminal window sometimes it doesn't. But if I then try to close the MobaXterm window I get a pop up on my PC for a shutdown, and the only way to close this window is to shut down my PC.
I am running a windows 11 PC, with MobaXterm Home Edition 22.2, and have seen this in 22.1 also. Not sure which earlier versions I was running before I encountered this problem or which version it started with.
Is this a known bug, another of my colleagues has encountered this also? Is there some setup I'm missing that could prevent this?
I am using MobaXterm Personal Edition v21.2 Build 4642 to access a remote workbench for educational purposes. The workbench has a Linux machine, and I run STM32CubeIDE to program a development board connected to the remote machine. When I create a new project, the wizard works OK, until it tries to open the ".ioc" file. A "progress information" (thi sis the window bar title) shows up, saying "Initializing Device Configuration Tool...". The progress bar keeps moving back and forth, but then the program looks like if it is stuck at this point.
If I kill the process and restart the IDE, I can see that the ".ioc" file is created. It means that the wizard is working. Then, if I try to open this file, I get stuck in the same way.
When I logged in locally at the workbench machine and used the IDE, it worked without problems. I also connected remotely to the workbench using another linux machine and "pure" (command prompt) ssh. The IDE also worked nicely, which gives me a hint that the problem happens when MobaXterm has to close that "progress information" window and open the "Device configuration tool" window.
Any hints on how to fix this problem?
Thanks in advance.
EDIT: I forgot to mention, the remote machine runs Linux Ubuntu 20.04 with Gnome GUI.
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 running this on Windows 7 SP1 with most (if not all) current patches. I have administrative permissions on this machine.
The first time I ran VSCodeSetup.exe, it ran the installer for several minutes then launched the actual application.
I got called into a surprise meeting, so I closed it thinking I'd look at it again later.
However, when I returned to my computer and tried to launch it, I found no evidence that it was actually installed... no desktop icon, no entry in the start menu, no Explorer integration...
I tried running VSCodeSetup.exe again, but all it does it show the installer screen for a split second, which then vanishes.
Since then, I've tried the suggestions outlined in VSCode Installation Failed - Failed to extract installer to install the application, even going so far as to run Update.exe --uninstall followed by running VSCodeSetup.exe again, but nothing has worked.
I even tried disabling my antivirus software and running the installer again, to no avail.
Does anyone know what I can do to get VSCode working again?
According to the comments and answers to Install VSCode in a specific folder, Visual Studio Code installs itself to %LOCALAPPDATA%\Code on Windows.
While I'm not sure why it didn't register itself with Explorer, I can at least create a shortcut to %LOCALAPPDATA%\Code\bin\code.cmd (with icon %LOCALAPPDATA%\Code\app.ico) to get it working again.
Or remove the directory entirely and run VSCodeSetup.exe to install it again, which still doesn't add Explorer integration... but this time at least the PATH now has code in it.
On windows VSCode is installed as Code.exe and its located in your
C:\Users\<windows-user>\AppData\Local\Code\app-<version-number>\Code.exe
or
C:\Users\John\AppData\Local\Code\app-0.5.0\Code.exe
I'm running Eclipse Indigo on Windows XP & Cygwin using the Subclipse plugin with our corporation SVN repository.
Overall it works just fine, however whenever I click on a file in the remote SVN repository a half dozen cmd windows open for the various ssh processes Subclipse spawns using Cygwin's ssh executable. This is very annoying since they pop up directly in front of what I'm working on and steal the cursor focus.
Could anyone tell me how I can insure that when these windows are spawned they're minimized so that they don't interfere?
The best way to do this is to use a GUI SSH client like TortoisePlink which comes with TortoiseSVN. I believe the other option would be to start Eclipse from your Cygwin Terminal. I believe the SSH client will then be connected with that Terminal and not spawn any additional windows.