You can correct the wrong topic title here if you want.
The Kernel log said these errors on sda1 your HDD, but there is no right answer without any testing tool results: Maybe the SATA cable is a problem? or RAM? or your mainboard bus?
Of course, test is stressful for beginners without technical knowledge.
However, you’re probably lucky that your system isn’t on sda1:
Try creating a new user on KDE if it’s ok.
This is normal because you do not have notification functionality when error messages appear in the log and Ext4 does not care about random bitrots of your data except system crashing or lagging.
If you need notification functionality, install journalctl-desktop-notification-git from AUR and run it manually. It will warn you if any error message appears.
I just checked using Wayland (before installing an entire DE) and I don’t have the problem with Wayland, I only have it with x11. And as I said, I didn’t have this problem before updating to Plasma 6. With Plasma 5 I didn’t have Wayland installed.
I think the problem really comes from the sda hard drive. I’ve had problems with him before. But it’s not the system disk, so I don’t think it’s coming from there. If I don’t find another solution, I’ll try to unplug the hard drive to test without it.
I created a new user and no lags ! So it’s coming from software on my user account.
PS : I don’t know how to edit the title. And I don’t know how to multiple reply in one message too, sorry.
So, your user configuration is the issue. It’s probably not any particular software.
Create a backup of your .config and .local folders. While you’re at it, you can do the same for .cache.
You can do this by copying and pasting the folders in your /home or by renaming them. If you go the copy and paste method, you’ll need to delete the original folders or move them to another directory.
After either method, reboot so that all those folders can be recreated with defaults. Keep the temporary user that you created so that it’s easy to make changes in case of a mistake. Either way, you can log in as root if necessary — but only if necessary.
Ok but I’m going to lose my configurations and everything I had set up so far. Isn’t there a way to find exactly where the problem is coming from, rather than resetting everything?
Yes. You can re-add (copy and replace) the configs folder-by-folder. Some of them will need to be checked first because they may refer to your old username.
Meld or your preferred DIFF program would be somewhat useful for this.
Because this is an issue which affects mouse performance, sorry to say, you may have to reboot a few times to check it properly. You could also just log out and back in, but it may not show any issues until a reboot.
I finally had time to take care of this. I started by removing applications that started automatically at startup and I did well to start there. I saw that I no longer had the problem. After 3 restarts (I had 3 applications that started automatically) I could see that it was Steam’s fault.
So it’s not the fault of EndeavorOS or Plasma! But it only appeared since my move to Plasma 6, that’s why I thought that.
I then found a reddit thread where someone had the same problem as me and the solution. Thanks to everyone for your help!