I used Timeshift to backup the system. I have tried older kernels (boot with shift key down) and have the same results.
Interesting. How do I determine if that is what is going on? If it is, how do I reschedule it for a more convenient time?
By looking at your process list and seeing what’s consuming CPU cycles. 
But you can rest assured that it’ll probably be that. You’re not the first one to report this sort of thing.
By modifying the cron jobs and/or the systemd timers. But if you have to ask, then it’s not for you.
Some “light” reading on scheduling… 
man crontab
For example with htop you could see what your PC is doing
pamac install htop
https://wiki.archlinux.org/title/List_of_applications/Utilities
Additional information: I don’t know what desktop environment you’re using ─ you didn’t tell us ─ but if you’re running Plasma, then chances are that it’s just Baloo indexing your files.
You can disable Baloo, or tell it to only index the files but not their content, and/or exclude certain directories from being indexed.
I am using xcfe
Well, it was a possibility. But what I said earlier still stands, though. It’s just that if you’re using Plasma, then Baloo exacerbates the problem.
I have been told to emphasize that my problem started just after the update of Quonos, it was not happening prior to that. And that the system is locking up. Also that I have an M.2 NVME SSD with two partions, the first of which is where booting into Manjaro takes place. And that I have an Intel 10600K Processor which is pretty fast.
You have also been advised ─ by two people on this thread ─ to look at the list of processes in order to see which process is eating up your CPU cycles.
Beating around the bush isn’t going to help you, nor anyone else here who might be having the same problem as you. If you want this resolved, then you’re going to have to provide us with data we can use.
I switched to the kernel labelled 5.10.83-1 LTS and for several hours my problem did not recur.
Eventually I switched back to the kernel labelled 5.15.6-2 and the problem soon appeared.
With Htop I was able to see some processes each using over 70% of the CPU:
Simplenote - this went away if I quit the program.
Vivaldi enable-crashpad - this did not go away if I quit the program but eventually stopped requiring as much CPU.
Later I saw tracker-miner-fs-3 using large cpu.
Some useful information at the link below on how to tweak that.
Thank you. I now have done this and will monitor.
I tried this but the tracker came back.
Disabling tracker for your user only
Enter the directory ~/.config/autostart, create it if it does not exist
Create a file named trackerd.desktop
Paste the following into the file, save and exit:
[Desktop Entry]
Encoding=UTF-8
Name=Tracker
Hidden=true
So I have now tried it and will see if that helps.
I wouldnt do it that way…
But also that service comes from tracker3-miners package, which is from Gnome DE while you use XFCE … so why do you have it?
pactree -r tracker3-miners
I guess something I installed used it. Maybe Gnome Calendar. Not sure.
Sorry but what does your command do?
Terminal responded: tracker3-miners
It should show anything that requires it … like this example:
pactree -r mhwd-nvidia
mhwd-nvidia
└─mhwd-db
└─mhwd
If yours returns nothing … then you have that for no reason and you can safely remove it if you dont use its functions.
Thank you
Disabling the autostart worked. I have now removed the program. Thank you to all for the help!
1 Like
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.