At least once per day my system or KDE Plasma freezes, and I had to reboot a PC. Usually, it starts with some elements, like notifications and task bar not being active, and then soon the whole system, except for mouse is frozen. Yesterday I noticed an interesting detail: it happened, while I was playing a game, first my Firefox got frozen, and soon I couldn’t alt-tab or minimize a game window with win+d combination. But the game was still working fine. After reboot, the system clock are showing wrong time (time of crash) for a moment, but later fetch updated time from the internet (don’t know if it’s a helpful information).
The KSystemlog shows these warnings and errors right before the sddm-greeter (I guess, that’s the start of reboot):
|19.11.2022 22:17|kernel|amdgpu 0000:06:00.0: amdgpu: PSP runtime database doesn't exist|
|---|---|---|
|19.11.2022 22:17|kernel|amdgpu 0000:06:00.0: amdgpu: PSP runtime database doesn't exist|
|19.11.2022 22:17|kernel|ACPI Warning: \_SB.NPCF._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20220331/nsarguments-61)|
|19.11.2022 22:17|kernel|ACPI Warning: \_SB.PCI0.GPP0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20220331/nsarguments-61)|
|19.11.2022 22:17|systemd|ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)|
|19.11.2022 22:17|bluetoothd|profiles/audio/vcp.c:vcp_init() D-Bus experimental not enabled|
|19.11.2022 22:17|bluetoothd|src/plugin.c:plugin_init() Failed to init vcp plugin|
|19.11.2022 22:17|bluetoothd|profiles/audio/mcp.c:mcp_init() D-Bus experimental not enabled|
|19.11.2022 22:17|bluetoothd|src/plugin.c:plugin_init() Failed to init mcp plugin|
|19.11.2022 22:17|bluetoothd|profiles/audio/bap.c:bap_init() D-Bus experimental not enabled|
|19.11.2022 22:17|bluetoothd|src/plugin.c:plugin_init() Failed to init bap plugin|
|19.11.2022 22:17|kernel|amdgpu: SRAT table not found|
I don’t know if that output means anything, perhaps someone does. However, could you please provide the output of the following:
journalctl --boot=-1 --priority=3
Where:
The --boot=-1 parameter is the number of boots ago this happened, so -1 for the previous boot, -2 for the one before it, and so on, and so forth.
The--priority=3arguments just limits the output to only warnings and errors.
While I might not be able to help, this side of the world it’s time to start the end of the day, this information will help anyone trying to be of assistance.
Thank you for your answer. Yes, indeed, it seems more like a usual boot stuff. Here’s the last and the only one close message in log with the command, you’ve provided:
That happened for me on default 6.0 and xanmod 6.0.
Btw, that’s exactly what happens to notifications before whole system freezes: KDE sometimes freeze after recent stable updates
Looks like a KDE bug after all