Hello guys, I am experiencing a recurring bug in Zorin OS 18.1 Core where my mouse cursor completely stops responding whenever I right-click inside Google Chrome or Brave Browser.Hey is my specs
Hi and welcome.
Having used Brave A.I. search engine via Mojeek, it might be down to hardware acceleration settings in the browser/s (I used Ubuntu 24.04 in the search criteria as Zorin 18 is a fork of same):
"To resolve the freezing, try the following solutions derived from similar reports on Ubuntu 24.04 and Brave:
- Disable Hardware Acceleration : This is the most common fix for Chromium browser freezes on Linux.
- Launch Brave from the terminal with the command:
brave --disable-gpu - If this works, go to Settings > System in Brave and toggle off "Use hardware acceleration when available" .
- Restart Brave normally.
- Install xdg-desktop-portal : Some users on Ubuntu 22.04/24.04 resolved browser freezes by installing the GNOME desktop portal.
- Run:
sudo apt install xdg-desktop-portal-gnome - Restart your system.
- Check GPU Drivers : The MSI MS-7A15 typically supports AMD Ryzen CPUs and often paired with AMD or NVIDIA GPUs.
- If using an NVIDIA card, ensure you are using the proprietary drivers rather than the open-source
nouveaudriver, which can cause cursor glitches. - If using AMD, ensure your
amdgpudrivers are up to date viaubuntu-drivers autoinstall.
- Kill Frozen GPU Process : If the browser freezes but the system remains responsive, you can kill the specific frozen process without rebooting.
- Open a terminal and run:
pkill -f "brave --type=gpu-process" - Alternatively, use the keyboard shortcut
Ctrl + Alt + F1to switch to a TTY, log in, and restart the display manager or kill the process.
- Check for Disk Space : Ensure your root partition is not full, as zero disk space can cause Chromium processes to hang or fail to display correctly, even if they appear in the task manager.
AI-generated answer. Please verify critical facts."
I would suggest to try it with disabled Hardware Acceleration. You could also check if it behaves different in Firefox (no Chromium Browser) to see if it is maybe the Matter of the Chromium-Base.
1 Like
