Mouse stopped clicking in CentOS running in Virtual Box - centos

I have an CentOS 7 VM in the VirtualBox 6 running on Windows. I have just installed it and immediately updated whole system (sudo yum update), as result kernel version 3.10.0-957.1.3.el7 was installed.
After I rebooted and logged in into the system, mouse started working strange. Mouse can be moved, application menu can be opened, but inside it no reaction in mouse movements. Also most of UI doesn't react to mouse clicks. I've searched internet and tried various ways, but nothing helps.
It is fresh install, I don't have VirtualBox guest additions installed yet. But right after installation everything worked and stopped to work after update. Does anyone know what may be the reason and how to solve this?
Rebooting with previous kernel doesn't help. Maybe something with X.org? It was updated too. But I don't see any error in the /var/log/Xorg.0.log
Update #1: This https://www.quora.com/Why-can-I-move-my-mouse-but-cannot-click-in-a-VirtualBox-with-Ubuntu recipe have helped. I have create mouse configuration file /etc/X11/xorg.conf.d/01-mouse.conf with content like this
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/event3"
Option "ZAxisMapping" "6 7"
EndSection
Actual mouse device path (/dev/input/event3) was taken from the latest /var/log/Xorg.0.log -- look for "VirtualBox mouse integration".
Update #2: I have found that if you log in first time, then somehow run console, and restart desktop manager service (sudo service gdm restart) - it will get you back to login screen - then everything works good on the second time login, even without such file. Can't explain myself what can be the reason.
Update #3: RH acknowledged the issue and works on the fix.
https://access.redhat.com/solutions/3893421
Update #4: After today's update problem has gone.
Now I'm having:
Linux centos7 3.10.0-957.10.1.el7.x86_64 #1 SMP Mon Mar 18 15:06:45 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

I have the similar issue with Centos 7.4 on VirtualBox 5 recently.
Once I left-click and start working on an application, I could not left-click on any other part nor applications to switch the focus.
My work-around is to right click the mouse on the stuck application twice. A context menu will pop up and go away. Then I can left-click any other parts of the desktop. Of course, doing this every time when one wants to switch the focus is still annoying but at least workable.

After a more recent update problem goes away. First known by me kernel version where the problem has gone:
Linux centos7 3.10.0-957.10.1.el7.x86_64 #1 SMP Mon Mar 18 15:06:45 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Related

How do I stop VSCode from starting up maximized?

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.

clion autocomplete keeps processing forever

I am using clion latest version 2020.2
Build #CL-202.6397.106, built on July 28, 2020
Autocomplete suddenly stopped working even though clion can build and complie my code just fine.
To make sure the issue is not project dependent, I started a new project. However, the problem still presists. As you can see in the attached image below. Whenever I explicity press (ctrl+space) I get this empty suggestion dropdown and the icon keeps rotating forever. (Note: If I don't press ctrl+space, the dropdown menu never shows up)
I made sure that PowerSaveMode is disabled.
I also tried File->Invalidate Cache/Restart->Invalidate and Restart
Did anyone face a similar issue? Any suggestions to what could be the cause of this problem?
Additonal information
gcc version: gcc (Ubuntu 4.8.5-4ubuntu8) 4.8.5
g++ version: g++ (Ubuntu 4.8.5-4ubuntu8) 4.8.5
I am posting this answer in case someone comes across this issue in the future.
The issue was definitly caused by the new update to clion. So I installed an older version. There is a tool named "JetBrains Toolbox" which is very convient when it comes managing multiple versions of any JetBrains software (clion in my case).
An additional note, if you want to run clion (or any other solution) as a superuser do not do that through the JetBrains toolbox. The toolbox will have the installtion location for each installed version, use it to run as a superuser from the terminal.

Ubuntu unity cannot work, reinstall didn't fix

I am using OdroidXu4 armv7 board, ubuntu 16.04. Dont know why my all menu disappear, but the files on desktop can still be operated.
I followed https://itsfoss.com/how-to-fix-no-unity-no-launcher-no-dash-in-ubuntu-12-10-quick-tip/ to reinstall ubuntu-destop or unity, but it didn't work.
Then I used the command below
dconf reset -f /org/compiz
setsid unity
The menu flashed a while then disappeared again, returned error:
file /dev/mali0 is not of a compatible version (user 10.6, kernel 10.1)
ERROR: The DDK is not compatible with any of the Mali GPUs on the system.
The DDK was built for 0x620 r0p1 status range [0..15], but none of the GPUs
matched:
file /dev/mali0 is not of a compatible version (user 9.0, kernel 8.0)
I was confused with the "GPUs", because I didn't have any GPU.
How to fix the problem, thanks for your help
I was using Ubuntu 16.04.In my case unity, launcher and even terminal is not working.I followed the steps as described in https://www.itsmearunchandel.co.in/linux/ubuntu/how-to-reset-ubuntu-desktop.html .
1. Go to command line mode, press Ctrl+Alt+F1
2. Give username and password.
3. Run the commands as described in the link.
This way my issue was resolved.

Linux Mint 17.1 Cinnamon 2.4 mouse cursor disappear at top of the screen

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.

How can I dump the entire Web DOM in its current state in Chrome?

I want to dump the current DOM to a file and be able to view it offline. Essentially, I have an outdated version of a page that I would like to keep around for comparison. As soon as I close my browser, I'm going to lose it so I would like to save the DOM exactly as it is.
There is already an answer for doing this in Firefox but how do I do it in Chrome?
Using the Web Inspector (F12), go to the Elements tab, right click on the <html> tag in your code and select Copy->Copy outerHTML. Then paste that into a new file and save.
In Chrome Dev Tools Console, type document.documentElement.outerHTML (use the tab button for autocomplete to save keystrokes) and hit Enter to see the DOM text displayed. To copy it to your clipboard and paste it elsewhere, use copy(document.documentElement.outerHTML) instead.
Damon's answer is also good (in Dev Tools, click Elements, right click <html>, click Copy > Copy outerHTML), but I find the Console command easier.
Command line solution
This is easy to do with newer releases of Chrome:
google-chrome --headless --dump-dom 'http://www.yahoo.com'
(The OP may not have been looking for a command line solution but this search result appears high when searching so others might find it useful)
Original answer 2017
My favorite way to do this is:
docker run -it --rm --name chrome --shm-size=1024m --cap-add=SYS_ADMIN --entrypoint=/usr/bin/google-chrome-unstable yukinying/chrome-headless-browser --headless --disable-gpu --dump-dom https://www.facebook.com
If you're not familiar with how Docker works, be patient - the first time will be slow but subsequent invocations will be quick.
Other information
Tested on
Ubuntu 16
Linux intel-nuc 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Docker version:
Docker version 1.10.3, build 20f81dd
Mac OS X Sierra
Darwin MacBook-Pro.local 16.7.0 Darwin Kernel Version 16.7.0: Thu Jun 15 17:36:27 PDT 2017; root:xnu-3789.70.16~2/RELEASE_X86_64 x86_64 i386 MacBookPro14,3 Darwin
Docker version:
Docker version 17.06.1-ce, build 874a737
If you install tidy you can indent the HTML too.
I am currently using version 53.0.2785.113 m of Chrome. The other answers no longer appear to be valid. To properly copy all child/descendant elements the user now has to right click on <html> then click "Expand All" before copying. Other wise you will not recursively copy all elements. A normal Ctrl+C will copy everything one <html> has been expanded.