The latest update made my system laggy and glitchy

Just updated to:

KDE Plasma Version: 6.4.2
KDE Frameworks Version: 6.16.0
Qt Version: 6.9.1
Kernel Version: 6.11.0-29-generic (64-bit)

with my system

Operating System: KDE neon User Edition
Graphics Platform: Wayland
Processors: 6 × Intel® Core™ i5-9600K CPU @ 3.70GHz
Memory: 32 GiB of RAM (31.3 GiB usable)
Graphics Processor: NVIDIA GeForce GTX 1650 SUPER
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: Z370M DS3H

made my system laggy and glitchy. Application startup times have increased, window resizing stutters, and even htop is now consuming 10–15% CPU - something I’ve never seen go above 2%. The Meta+T shortcut to open the Tiling Editor sometimes works and sometimes doesn’t. Overall, the responsiveness has noticeably degraded."

Has anyone else experienced this? Any idea what might be causing it?

htop uses up to 15% cpu? It can be. But on my laptop, which is very old, mobile processor with 1,3GHz @ 2 cores. So I can’t imagine so high cpu payload onto modern and powerful desktop processors like yours.

I’ve already upgraded to latest kde neon (“user edition” I’ve use), every day I’ve installing new and new updates when Discover proposes them, and I don’t notice any degrades. So, your situation looks like gpu or cpu driver related problem (imho).

Did you receive updates to your video card? The driver may malfunction. If so, try another driver if available.

inxi -Ga

interestingly this abnormal htop load


occurs only when kde/plasma is loaded. When i enter my system via SSH before login to user session then it works as usual - <2%.

it looks to me that i have normally working and up to date graphic driver and it didn’t updated recently:

yurin@halo:~$ inxi -Ga
Graphics:
  Device-1: NVIDIA TU116 [GeForce GTX 1650 SUPER] vendor: ASUSTeK
    driver: nvidia v: 575.57.08 alternate: nvidiafb,nouveau,nvidia_drm
    non-free: 550.xx+ status: current (as of 2024-04; EOL~2026-12-xx)
    arch: Turing code: TUxxx process: TSMC 12nm FF built: 2018-2022 pcie:
    gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 3 speed: 8 GT/s ports:
    active: none off: HDMI-A-1 empty: DP-1,DVI-D-1 bus-ID: 01:00.0
    chip-ID: 10de:2187 class-ID: 0300
  Display: wayland server: X.org v: 1.21.1.11 with: Xwayland v: 24.1.6
    compositor: kwin_wayland driver: X: loaded: nvidia
    unloaded: fbdev,modesetting,nouveau,vesa gpu: nvidia display-ID: 0
  Monitor-1: HDMI-A-1 res: 3840x1600 size: N/A modes: N/A
  API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
    drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia wayland: drv: nvidia
    x11: drv: nvidia inactive: device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 575.57.08
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce GTX 1650
    SUPER/PCIe/SSE2 memory: 3.91 GiB display-ID: :1.0
  API: Vulkan v: 1.3.275 layers: 5 device: 0 type: discrete-gpu name: NVIDIA
    GeForce GTX 1650 SUPER driver: N/A device-ID: 10de:2187
    surfaces: xcb,xlib,wayland device: 1 type: cpu name: llvmpipe (LLVM
    19.1.1 256 bits) driver: N/A device-ID: 10005:0000
    surfaces: xcb,xlib,wayland

so it has something to do with plasma or/and QT-update, not to mention glitch Meta+T shortcut it hardly can be related to graphic driver in my view…

Intersting. I’ve not seen anything like that. Hmmmm. Out of curiousity have you tried to create a temp account and see if that account is having the same issue?

I tried creating a new user, but it had no effect. However, I discovered that the abnormal CPU load in htop is related to the option ‘Highlight out-dated/removed programs (red) / libraries (yellow)’. Once this option is disabled, htop’s CPU usage drops to a normal level -below 2%. Could my system wide performance degradation issue be linked to outdated or improperly removed packages left over from my recent system update? Could Discover have messed up my update?

I believe this means things that have been updated on-disk but the current version is still loaded in ram — aka restart/reload the app/service or logout as appropriate.

I restarted my system multiple times, no effect. Once i am logging in, i see that plasam is laggy, resizing windows stutters, Meta+T in most of the time is not working, and htop abnormal load… i am running out of ideas what it can be, thinking about to reinstall OS, again.

I just updated my another KDE neon system - no issues at all. So it’s either a hardware issue specific to my PC (just a coincidence with update), or something went wrong during the update that damaged some packages or configuration files. I have no idea what exactly got broken, so I’ll probably just reinstall the operating system and see if that resolves the issue.

Does the other system have the same Nvidia graphics?

Recent updates do include Ubuntu kernel and driver updates, and borked Nvidia can show the sorts of symptoms you are seeing.

This might be relevant:

The current, and I think only, version of the Nvidia driver at the moment in Ubuntu 24.04 is 575.64.03, unless you are using the server version (xserver-xorg-video-nvidia-575-server), which is using the slightly older release. I have no idea what the difference would be between the ‘server’ driver and the normal one.

In fact, both systems use version 575.57.08. Moreover, I’ve tried completely purging it, but that didn’t resolve any of the aforementioned issues. For example, Meta+T still only works occasionally, and htop continues to show abnormal CPU usage. Something is clearly broken - either some KDE/Plasma/Qt packages are misbehaving (and i don’t know how to narrow them down), or there’s a hardware issue.

Here is a thought. Have you tried running x11 VS Wayland and see if they are behaving the same?

Yes, I’ve already tried that, but the issues remain. It looks like my CPU is either underperforming or not being used efficiently. But still it does not explain Meta+T glitch… It might be wise to maintain two separate system disks with KDE Neon and clone the primary one before applying updates.

Just wanted to let you know that I reinstalled KDE Neon, and it fixed all forementioned issues. Whatever the problem was, remained unknown.