[Stable Update] 2026-05-02 - Kernels, Plasma, GNOME, Mesa, Systemd, VirtualBox, LibreOffice

Announcements Stable Updates
150

After update all games start slower, even Balatro is starting noticeably slower. From 1-2 seconds to 6-10. Maybe Steam updated as well. Also it doesn’t matter whether it runs native or with proton.
And haptic feedback along with basic vibrations is broken with Dual Sense.
Plasma desktop
Kernel: 7.0.3-1-MANJARO
AMD Ryzen 7 7700
Radeon RX 9070 XT

Does anyone have similar problems?

<< EDIT >>

Ok, it seems i’ve found the culprit after digging for a while. I’ve had the rule for wireplumber and after update it started to effect game’s start up time. It also effected the speaker on Dual Sense.

Here’s a rule in question:

monitor.alsa.rules = [
  {
    matches = [ { api.alsa.use-acp = true } ]
    actions = {
      update-props = {
        api.acp.auto-profile = true
        api.acp.auto-port = true
      }
    }
  }
]
151

SDDM is not a KDE product.

152

2 posts were split to a new topic: Issues mounting an NTFS disk

154

Creating an issue report here :point_down: might be a good start.

1 Like
155

But SDDM is integrated into KDE, so the issue could still related to the latest Plasma changes or not?

156

Primarily there’s a chain of command when it comes to these things. If the problem is occurring with SDDM you report it there first (unless you have evidence showing it is somewhere else).

But also, SDDM is not incorporated by KDE, distributions package it alongside KDE to facilitate login. They could package a number of other login managers instead.

Could it be this bug? Keypress that wakes greeter from DPMS off / reveals hidden password field is passed through as input · Issue #2170 · sddm/sddm · GitHub

2 Likes
161

No, it’s been replaced with Plasma Login Manager, an actual KDE project.

163

Is Plasma Login Manager now officially ready for live use, or is it still considered beta?

164

Personally I’ve considered it ready for Live use since it was first released, that’s how long I’ve been using it. In fact it’s also installed on my partner’s computer, and she has noticed no issues, even when it was officially Alpha, But it is officially Beta as of Plasma 6.6.

As far as I’m concerned it has just gotten better over time, not in how it functions, which is just fine, but in how it looks and fits with the overall Plasma eco system

4 Likes
165

Well, my case seems not related to the Keypress that wakes greeter from DPMS off / reveals hidden password field is passed through as input · Issue #2170 · sddm/sddm · GitHub bug

Anyway I got rid of sddm and switched to plasma-login-manager.

The problem remains and, as suggested here, I opened an issue on KDE Discuss:
Plasma 6.6.4 - wayland - windows restored in the wrong monitor

1 Like
166

It keeps going :confused:
Dirty Frag (Kernel - ESP Page-Cache Write vulnerability)
https://github.com/V4bel/dirtyfrag
https://nvd.nist.gov/vuln/detail/CVE-2026-43284

167

Bad news, this actually corrupted the filesystem and I lost some files, probably a NTFS instability as Lycan’s post mentioned. I have no idea why the system switched from ntfs-3g to the kernel driver with no warning, but this is dangerous.

To avoid further problems I added these lines at /etc/modprobe.d/no-kernel-ntfs.conf to prevent the kernel module from even loading to begin with.

blacklist ntfs3
install ntfs3 /bin/false
1 Like
168
1 Like
169

Because the line in /etc/fstab is probably set to auto instead of ntfs-3g so when the kernel driver became available it started using that over the external ntfs-3g.

3 Likes
170

The more likely scenario is that with ntfs3 you were actually notified of existing filesystem damage – ntfs3 tells you when there is damage (in the form of an error message);

ntfs-3g does not.

3 Likes
171

A post was split to a new topic: /boot/vmlinuz-6.12-x86_64 not found

172

Added some info about the refind situation in the FAQ.

It will probably be good if someone writes something about ntfs, but for me it is still a bit unclear when and why problems occur and i wouldn’t want to generally advise everyone to switch to ntfs-3g before being absolutely sure this is needed (and i am not).

173

The last sentence resumes everything

174

The only problem is, some of the people reporting problems with ntfs after last update are not on kernel 7.1…and that is where the mystery begins. Something else got backported, maybe.

175

everyone reporting issues are on 7.0, I haven’t seen a report on another kernel, even 6.19 is safe. And currently, 7.1 is also safe.