I had several kernel panics or kde panics, hard to tell. My first suspicion was that I had a problem with my SSD, so I wanted to run smartctl to check it out:
>sudo smartctl -t short /dev/nvme0
To see the results:
>sudo smartctl -l selftest /dev/nvme0
To see full summary of disk usage:
>sudo smartctl -x /dev/nvme0
Then I had to check out the logs from journalctl for the X and the kernel.
>journalctl -xb
>journalctl -xe
(with -k you can see kernel drama from the previous boot (see manual)
>journalctl -kb
Then I checked dmesg
>dmesg|grep error
Also the state of the sensors (they were ok)
>sensors
The systemctl log for failed processes:>systemctl --user --failed
And finally, by suggestion of a forum, the core dumps.
>coredumpctl list
I saw a problem with the following service (appimagelauncherd) that was spamming my core dumps with tons of errors and at some point it seemed that the space for dumps ended and the computer crashed. Basically I got 1000 variations of the following error all over the logs:
" traps: appimagelaunche[1232] general protection fault ip:7f2d012ca394
sp:7ffc8910b128 error:0 in libstdc++.so.6.0.32[7f2d0129c000+137000]"
I tried to stop it the right way as above, but it gave me errors.
>systemctl --user status appimagelauncherd.service
>systemctl --user disable --now appimagelauncherd.service
>systemctl --user status appimagelauncherd.service
In the end, I got annoyed and I removed it in the most brutal way:
cd /usr/lib/systemd/user/
sudo mv appimagelauncherd.service ~/scripts
cd ~/.config/systemd/user/default.target.wants/
sudo mv appimagelauncherd.service ~/scripts
Note, this thing has also settings: AppImageLauncherSettings (where you can click that it stops relaunching after you kill it, but I didn't do it at the time), so maybe that could have stopped it without manually removing the service but I discovered it afterwards. Right now the computer has been working for 5 days and it works ok. I don't know if this solved my problem, but for now at least it doesn't crash every 5 minutes.
P.S. Another error I saw in dmesg and tried to fx is about the bt_coex_acitve, so I did the following (but I'm not srue the driver for the wifi accepted it (link)):
sudo modprobe -r iwlmvm
sudo modprobe iwlmvm bt_coex_active=N
Another error I was getting was:
"kwin_core: XCB error: 152 (BadDamage), sequence: 10052, resource id: 16910493, major code: 143 (DAMAGE), minor code: 3 (Subtract)"
which according to Manjaro forum can be removed with editing "~/.bash_profile" to include:
# suppress QT logging
QT_LOGGING_RULES='*=false'
export QT_LOGGING_RULES
Finaly, I was getting an error from Akonadi
akonadiserver[1706]: org.kde.pim.akonadiserver: arguments:
("--defaults-file=~/.local/share/akonadi/mysql.conf", "-
-datadir=~/.local/share/akonadi/db_data/",
"--socket=/run/user/1000/akonadi/mysql.socket", "--pid-file=/run/user/
1000/akonadi/mysql.pid")
and I did as advised in Manjaro forum:
mv ~/.local/share/akonadi/db_data/ibdata1 ~/.local/share/akonadi/db_data/ibdata1.old
akonadictl start
It took a while to restart akonadictl but it finished.
Also to limit the space that journalctl takes:
journalctl --vacuum-time=2weeks
