Kwin wayland is takng 97% of cpu and my whole laptop is lagging

i have tried every possible method that i found on internet and it didnt worked

i have intel i7 intel core cpu and a nvidia 4090 rtx gpu

im new to it, so i added garuda in my computer by

1)booting live usb
2)choosing drive D as partition to replace with size of 543gb
3)installed
4)in bios set hard drive to garuda instead of windows 11 boot manager

? :heart::heart::heart::heart:j

Please post your garuda-inxi and describe what you have tried already if you want meaningful advice.

3 Likes

i have updated tried to disable heavy animations of kwin wayland to reduce usage, i also tried refreshing it lot of time

ps garuda is too laggy rn because of cpu usage that i cant open anything in it, or even move the mouse or type something in it

so i cant open terminal

i am facing these issues on garuda mokka

Could you boot into a live image of a lighter DE (Cinnamon or Xfce) and open a terminal there to post your inxi?

It could be anything from Plasma’s file indexing to Nvidia drivers not installed properly. It’s a shot in the dark without more info

4 Likes

have you tried installing Garuda in open source instead of nvidia drivers? i got a 4080 and at time have been forced to do that.

Have you tried an older version of the Garuda iso than June 25? Such may also make a difference.

If you are successful with the non nvidia drivers answer yes to install the nvidia drivers after first run update watching the installation of the nvidia dkms modules. If they compile rightly all is well if not try the code below uninstalling any conflicting packages, and reinstalling them after a successful install of the nvidia drivers.

sudo pacman -S nvidia-open-dkms egl-wayland lib32-nvidia-utils lib32-opencl-nvidia nvidia-settings opencl-nvidia nvidia-utils

if that does not work i have final code that might help and this is using the nvidia-all drivers. The developers do not like them, but in the past they have rescued me often.

#first uninstall conflicting packages

sudo pacman -R garuda-nvidia-config
sudo pacman -R lib32-nvidia-utils
sudo pacman -R nvidia-settings
sudo pacman -R gwe
sudo pacman -R python-py3nvml
sudo pacman -R nvidia-dkms
sudo pacman -R nvidia-utils
sudo pacman -R egl-x11

#downloading and installing the nvidia-all package interface

rmdir --ignore-fail-on-non-empty $HOME"/nvidia-all";
git clone GitHub - Frogging-Family/nvidia-all: Nvidia driver latest to 396 series AIO installer
cd nvidia-all
makepkg -si

#reinstalling conflicting packages after successful install of a nvidia driver version.

sudo pacman -S garuda-nvidia-config gwe lib32-nvidia-utils nvidia-settings python-py3nvml nvidia-utils egl-x11

Owning a nvidia graphic card can be a real challenge at times.

Best of luck

EDIT:

Oh i saw no garuda-inxi! So i do not know if your bios is up to date. However i had to update my bios to get the installer to recognise my graphic card correctly, it may benefit you as well.

1 Like

BTW, @Jeshu for correct Markdown and terminal format just use

2 Likes

I would suggest either booting directly into a TTY, or trying to switch to a TTY from your KDE session.

Once at the TTY there are many things you can try. Others will I’m sure post suggestions for you once you can access a TTY terminal.

If you search the terms regarding a TTY online you should easily find directions for accessing a TTY in Linux.

3 Likes

Once you have access to a TTY terminal run:

sudo pacman -S plasma-x11-session

Once you have plasma-x11-session installed you can to login with an X11 session rather than Wayland. Look at the bottom left of the login screen, you can alter your session type there. Hopefully using X11 will correct your problem.

1 Like

it helped, thanks

2 Likes

i will also make sure to put garuda inxi in every forum by now

2 Likes

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.