I had recently to erase “.cache” entirely otherwise #plasma couldn’t function. I checked the usual suspect under “.config/plasma-org.kde.plasma.desktop-appletsrc” but it seemed fine.
I’m sharing this here in case this type of bug reaches stable. If it is an isolated case, the fix is doable.
Kernel 5.15, 6.1 or 6.2 forces my PC (full AMD system) to shut down after waking up from sleep/suspend because the temperature is critical, but it is not true.
$ journalctl --no-pager -p 3 -b -1 --output=cat
thermal thermal_zone1: acpitz: critical temperature reached, shutting down
reboot: HARDWARE PROTECTION shutdown (Temperature too high)
reboot: Hardware protection timed-out. Trying forced poweroff
But I checked the temperature is actually not high. My guess is that the Kernel has this bug.
Can you confirm if you have the same problem when using AMD CPU and Kernel 6.1 or 6.2?
Solution:
My trick is to use kernel parameter thermal.crt=-1 to disable critical thermal. (But not recommend)
Lately I observe strange behaviour of energy profiles on my laptop, the respective Plasma widget fails to switch a profile to any other than Balanced. It’s been like this for a week or so. At first I thought it’s kernel 6.2 related but now the same is haunting me on 6.1, too. Anyone having the same?
After the last pamac update, I’m getting some strange behaviour between pamac and polkit1 in KDE. Even with a wrong password, pamac can install/remove/update packages when executed via the terminal. GUI doesn’t allow it without a valid password being entered. All is well with it in /etc/passwd
I just tried pamac upgrade used the wrong password and got the same message as you.I tried it again with the right password and it showed I needed updates.
driver / module was not loaded (probably r8169), you can try manually (# modprobe r8169 and watch journalctl) but the question remains why it didn’t on startup.
Same controller / kernel here, all is fine.
Found the issue! I missed an error on pamac stating “bad return status for module build on kernel: 6.2.6-1-MANJARO”. So I rebuild r8168-dkms and everything is back on track. Thanks, @dragan, for checking, it saved me some debugging.