I just simply installed winginx on my windows 10 and memcached couldn't start(Stopped at wingginx panel) , i didn't change anything how do i fix that
Related
Recently uninstalled my old local cluster and reinstalled the new one (using Platform installer)
Every since then the manager doesnt respond to right clicks. (Normally a right click opens up a small menu with start, stop, reset etc). Sometimes it will open the window but it will be 30+ minutes later.
I know everything in the background is working as I'm able to still publish to my local 1 node but I cant use the GUI.
What I've tried:
Uninstall + reinstall
Killing the program via task manager and re opening
Question 1- How do I fix this so I can use the GUI?
Question 2- Where can I find the terminal commands to manage the cluster if the GUI doesnt work?
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.
On just one of my two Linux systems, Visual Studio Code always starts in a maximized window. It doesn't do it on the other one. Both systems are Pop!_OS 20.10, upgraded along the way from each Pop!_OS release from 18.04. VSCode is 1.51.1, and has been doing this since I started using it about 1.36 or so. I'm using the default Gnome Shell on each system. On the system where it doesn't start maximized, it remembers its previous size and placement. If I double-click on the window header on the failing system, it returns to its prior placement and size, but if I close it in that state, when I reopen it it's maximized again.
I'm guessing there's a settings file or something that's set to force it to be maximized, but I didn't explicitly set anything like that, and I wasn't able to find anything when searching that would have that effect.
The failing system is one I built up with a Ryzen 9 3900X, 64 GB RAM, 1 TB M.2 PCIe 4 SSD, and an RTX 2060. The working system is a System76 Oryx Pro v4 with 64 GB and an 8th gen Core i7. VSCode has done this on the failing system ever since I was running it on a dual-hex Mac Pro, and on a 1080p monitor; I'm now using a 3840x2160 monitor - but that's what the Oryx Pro has on it, too.
What am I missing?
Following works on ubuntu 20.10. Position VSCode window where you would like it to open next time. Then, hit <Ctrl><CloseXButton>
This will close your current session. Next time you open this project via code ., you should get VSCode to open in that last state you <Ctrl>-closed it in.
I don't know where this status is stored in the settings file.
Cursor of mouse disappear(at last pixels of screen).
For example. Now all ok.
And if I move mouse to the top of the monitor it disappear.
But at the same time I can click on buttons on top panel.
Any ideas how to fix it?
Verbatim copy (Mint commented by me) of Heath Jones (hjones014) post on launchpad which solved the issue:
I finally remedied the problem, using the xorg-edgers ppa. This is what I did -
sudo apt-add-repository ppa:xorg-edgers/ppa
sudo apt-get update
goto additional drivers (driver manager on Linux Mint) and select driver 349.16 (at the moment of writing is 355)
reboot
goto software/updates (Software Sources->PPAs on Mint) and goto the "Other Software" tab and UNCHECK the xorg-edgers ppa. I DID NOT PURGE THIS PPA.
The reason why I nixed this ppa is because after selecting driver 349, the software updater would try to pull in other updates from the xorg-edgers ppa which kept crashing my system. This allowed me to keep the driver 349 and not pull in any other updates. If you do a ppa-purge, it will also nix the driver, hence why i just unchecked it in the sources tab.
Adding the option
Option "hw_cursor" "off"
on the Device section of /etc/X11/xorg.conf solves this issue but creates other (more annoying) issues. [Disclaimer] messing with the xorg.conf can screw up your graphics and you'd be unable to log in. Proceed with caution, backup your xorg.conf and know how to log in to your system with a live CD/usb or drop to a shell that doesn't need the X server.
Also, switching to the nouveau driver solves it too.
None of the aforementioned solutions are acceptable for me. I'll keep digging and update the answer.
I use Windows 8 x64 and last eclipse: eclipse-java-juno-SR1.
At second monitor I move console and some android tools (logcat, devices). All worked ok. But I do not need see second monitor all time. And I switch off this monitor (by win + P). On next start I see windows from second monitor at primary monitor. Close. Open. And now see default perspective. Own perspectives, that I saved disappeared. And this repeat all time, if I disable second monitor.
Before I use eclipse-java-indigo-SR1 and do not have any problem.
Don't find solution. Now back to indigo (3.7.1).