Screen saver / screen lock causes high fan (and cpu?) after upgrade from 43 to 44

Ask Fedora
1

All;

I used these instructions to upgrade from Fedora 43 to Fedora 44

I am running on a Lenovo Legion 9 and Fedora 43 worked flawlessly. After the upgrade every time the system locks the screen the fan shoots up high and it seems like the cpu is pegged because when I try to unlock the screen the system is seriously sluggish, once I get logged back in all is fine and the fan speed goes back to normal

THanks in advance for any help

2

I forgot to mention I am running the KDE Plasma Desktop

3

Can you log in via SSH from another machine and have top running to see which process/thread is causing the high CPU load when locking the graphical session?

4 
top - 10:57:13 up  2:50,  3 users,  load average: 0.29, 0.55, 0.68
Tasks: 623 total, 1 running, 622 sleep, 0 d-sleep, 0 stopped, 0 zombie
%Cpu(s):  0.9 us,  0.4 sy,  0.0 ni, 98.4 id,  0.0 wa,  0.1 hi,  0.1 si,  0.0 st 
MiB Mem :  63990.4 total,  37169.3 free,  17158.0 used,  11435.6 buff/cache     
top - 11:08:55 up  3:02,  3 users,  load average: 2.64, 1.40, 0.95
Tasks: 629 total, 3 running, 626 sleep, 0 d-sleep, 0 stopped, 0 zombie
%Cpu(s):  3.6 us,  5.8 sy,  0.0 ni, 90.3 id,  0.0 wa,  0.1 hi,  0.1 si,  0.0 st 
MiB Mem :  63990.4 total,  36465.0 free,  17723.6 used,  11961.9 buff/cache     
MiB Swap:   8192.0 total,   8192.0 free,      0.0 used.  46266.8 avail Mem 

    PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND  
  26398 kevink    20   0 7973768 810068 234556 S  77.2   1.2   4:04.97 plasmas+ 
top - 11:08:55 up  3:02,  3 users,  load average: 2.64, 1.40, 0.95
Tasks: 629 total, 3 running, 626 sleep, 0 d-sleep, 0 stopped, 0 zombie
%Cpu(s):  3.6 us,  5.8 sy,  0.0 ni, 90.3 id,  0.0 wa,  0.1 hi,  0.1 si,  0.0 st 
MiB Mem :  63990.4 total,  36465.0 free,  17723.6 used,  11961.9 buff/cache     
MiB Swap:   8192.0 total,   8192.0 free,      0.0 used.  46266.8 avail Mem 

    PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND  
  26398 kevink    20   0 7973768 810068 234556 S  77.2   1.2   4:04.97 plasmas+ 
   2613 kevink    20   0 1019652  61912  53068 S  72.3   0.1   2:49.42 org_kde+ 
   2406 kevink    -2   0 4132272 461296 345852 R  67.5   0.7  31:14.67 kwin_wa+ 
  29823 kevink    20   0 9163888 401424 224328 R  53.1   0.6  44:40.07 amarok   
   8643 kevink    20   0 3368704 490924 120612 S   9.6   0.7   1:30.96 Isolate+ 
  43501 kevink    20   0 2960472 230400 125856 S   9.6   0.4   0:11.12 Isolate+ 
   2405 kevink     9 -11  346704  26504   9152 S   4.8   0.0   0:06.31 pipewire 
   4990 kevink    20   0   12.3g 929288 361292 S   4.8   1.4   5:04.92 firefox  
   7253 kevink    20   0   12.3g 950172 306176 S   4.8   1.5   2:49.75 firefox  
  49545 kevink    20   0  235800   5696   3484 R   4.8   0.0   0:00.01 top      
      1 root      20   0   44928  22932  11184 S   0.0   0.0   0:02.00 systemd  
      2 root      20   0       0      0      0 S   0.0   0.0   0:00.03 kthreadd 
      3 root      20   0       0      0      0 S   0.0   0.0   0:00.00 pool_wo+ 
      4 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker+ 
      5 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker+ 
      6 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker+ 
      7 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker+
5

Hmmm, I can’t read all the processes, but it appears to be plasmashell, kwin_wayland_wrapper, Amarok, and org_kde...?. Does it also happen if Amarok isn’t running?

6

I tried it without amarok running and it still happens, plasmashell is always at the top when this happens