Hello, today I upgrade my system with ‘yay -Syu’ and on the end when wps office upgrade is almost done my system slows and everything works very very slow. I noticed that my system works slower from few weeks but today it’s unusable.
It stops on that, sometimes wifi connection drops.
Getting sources ...
-> Company wps-office_11.1.0.10702.XA_amd64.deb
==> Checking source files with sha1sums ...
wps-office_11.1.0.10702.XA_amd64.deb ... That's right
==> reference / directory $ srcd ...
==> Unpacking sources ...
-> Unpacking wps-offices_11.1.0.10702.XA_amd64.deb with bsdtar
==> Starting preparation () ...
==> Sources are ready.
==> Package creation: wps-office 11.1.0.10702-2 (Mon, Aug 30, 2021 09:38:14)
==> Checking needed to run ...
==> Ask for what you need to do ...
==> Liquidation: Tree liquidation $ s /
==> reference $ pkgd ...
==> Entering the fakeroot environment ...
==> Starting wps-office () ...
==> Preparing installation ...
-> empty directories ...
-> Methods of libtool files ...
-> methods of unwanted files ...
-> static methods of library files
-> Throwing unnecessary symbols into binary files and libraries
The first thought I have is that usable disk space might be compromised - the previous (lesser) loss of performance suggests it. Have you cleaned your cache in a while, for example? Try: sudo paccache -rk3
which will reduce you pacman cache to only 3 versions of a given package. Use -rk2 will save even more space. Further measures can be taken if needed - but this might make a difference on its own (if this is the partial cause of the slowdown).
I read that snaps can have some adverse effect on boot time since they all need to be mounted at boot but when your system is up and running, they shouldn’t be a problem I guess. I would keep an eye on the processor cycle. Also check the sanity of your disk perhaps.
If you can easily remove stuff from /home, I recommend that.
Not sure if it helps already now, but if the free space gets much smaller, more issues are ahead.
If you intend to kill a process, that’s not the proper way of doing it. chmod -x only will remove the execute bit from an executable file preventing it from running in the future. It has nothing to do with an already running process which refuse to stop.