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?
Related
I have a really wired problem (or a bug) on vscode. I can "attach chrome" debugging totally fine usually,
but after some random time connecting to the chrome instance (may be a couple of hours or 8 hours, like I left it connected while I'm sleeping), it automatically disconnect the debugging,
then when I try to re-run attach chrome to reconnect it, for some weird reason it doesn't connect to the instance.
It's not a failed, it's not like "cannot connect to the port 9222", it's infinitely trying to connect showing the left up side blue indicator left to right.
This is my second time to encounter this weird problem. For the first time I even don't know how I solved the issue. maybe I just waited its reconnect for an hour or like that.
The first things I happened to think from the problem is simply its port conflict. So I checked vscode side's (I mean I use vscode in the remote ssh mode from Windows to Linux Ubuntu) port and process, used htop to filter port "9222" or process "chrome", but I didn't find anything stucking there. So I assume in the linux side the debugging process is exiting successfully.
So I did the same on the Windows side, I used resource monitor to check port "9222", no running process. If I re-open a 9222 debugging enable chrome, then it appears. closing, it disappears. It seems there is no problem here as well.
I then checked vscode's version. I was using vscode 1.64.2 so I side-installed 1.65.2 and 1.66.1 (the latest) and tested it. Doesn't work.
"refreshing the window" doesn't work. closing the window and re-open, doesn't work.
So what can I do?
Did you just install some new extensions in Visual Studio Code? I found that I had this exact same behaviour, "infinitely trying to connect showing the left up side blue indicator left to right", after I installed Karma Test Explorer and Test Explorer UI extensions. Once I uninstalled those extensions, debugging started working again.
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.
Lately, after I have been using VSCode for some time, opening and closing it repeatedly, I was surprised to see, in Process Explorer, a lot of wsl.exe processes. As it looks, 4 or 5 processes were started by VSCode each time I opened it, but were not terminating when I was closing VSCode, so I ended up with a lot of them (there are only 5 in the image, but actually there were several dozens).
I think this has something to do with the following dialog box I see (almost?) every time I open VSCode
(which I was just closing since I am not interested to install these extensions).
Does someone know how to disable the launching of these processes? I had a Docker extension which I uninstalled, but this behavior persists.
Ok, so the culprit is not this something which launches the dialog box (I still see it), but it appears to be the following setting (when checked)
After unchecking it, I don't see now any wsl.exe processes launched when I start VSCode.
There is problem in my Eclipse. There are two twin Error Log windows and I can not close either of them.
It completely makes trolling on my development windows. When I want to open a class the codes go under the windows.
I force shutdown my pc by holding down the power button till it went off. Just before it shutdown, I saw a netbeans pop-up just come up before the system went off. Before initializing the shutdown, I had closed netbeans, and I think that netbeans had not fully shutdown. The pop-up might have been the last procedure the IDE automatically does, like those that flash the cmd which almost immediately closes by itself.
The problem is that now netbeans won't start up. It only shows the blue window then dissapears, not to appear again, even in the task manager.
How can I fix this?