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

I now also applied the update on my cinnamon edition and I can confirm it went smoothly with no error :smiley:
As for ‘copy-fail’ I thought I read early in this post that the patch has only been applied to the ‘Unstable’ branch with an update for the stable branch coming soon?, but when I run the command

lsmod | grep algif_aead 

The result was a blank line! which I think mean it’s not loaded? so it appears the kernel patch had be added to the ‘Stable’ branch as well!? Am I correct?

1 Like

I edited /etc/xdg/user-dirs.defaults

2 Likes

All of our kernels now have the patch. :wink:

That is correct. Not everyone had that module loaded. I didn’t either.

I could be wrong, but I believe it only gets loaded if you have the encrypt or sd-encrypt hooks in /etc/mkinitcpio.conf, or otherwise put, if you’re using an encrypted filesystem.

3 Likes

It came sooner. Patched kernels were pushed to stable

Manjaro KDE user here, update has completely unresponsive input to keyboard and mouse at the log in screen. System now completely dead, can’t even switch to a terminal to troubleshoot. Perfect…

I updated it on two devices, one of which has a GTX 1060, and everything is working perfectly. I don’t know how you’re managing to do that.

1 Like

nova_core taking priority over nouveau utterly broke my laptop’s ability to put the dGPU to sleep, along with gpu passthrough to VM(nova can’t handle gpu handover/resets it seems, flawless going back to nouveau). Had to blacklist nova_core to get my laptop to work properly again.

Keep in mind: a module can be autoloaded if not blacklisted.

2 Likes

So the installation went fine and produced no errors; then after rebooting it is stuck and non-responsive on the login screen?

What is your normal login screen? Do you use SDDM or Plasma-login-manager or do you boot to a console login?

So you’re at the login screen and you can’t switch to a different tty, Ctrl+Shift+F3 for example?

Can you boot from a Manjaro installation USB?

After latest update audio seems to have stopped working from the laptop speakers

❯ inxi -A
Audio:
Device-1: NVIDIA GB205 High Definition Audio driver: snd_hda_intel
Device-2: Intel 800 Series ACE driver: snd_hda_intel
API: ALSA v: k7.0.3-1-MANJARO status: kernel-api
Server-1: PipeWire v: 1.6.4 status: active

I did reinstall pipewire to see if that fixed it, but nothing changed.

sudo pacman -Syu pipewire pipewire-pulse pipewire-alsa wireplumber pavucontrol
systemctl --user enable --now pipewire pipewire-pulse wireplumber

Bluetooth audio works fine.

The one that I always use is:
Device-2: Intel 800 Series ACE driver: snd_hda_intel

After the update my ntfs partitions mounted via veracrypt stopped mounting with error fsconfig() failed: ntfs3: Unknown parameter 'big_writes', so I disabled the option hoping the high cpu issues I was running into wouldn’t come back. To make things weirder big_writes seems to be deprecated since 2016 and always enabled now, I have no idea why it was working before hahaha

Since neither ntfs-3g nor veracrypt packages updated, the suspects are fuse3 or the linux kernel, which is integrating native support for NTFS. I don’t believe it’s the kernel because I now have version 7.0.3-1, while the ntfs integration should be added at version 7.1.

That’s right, installed went fine, boot process fine, keyboard has lights that say it’s connected just fine, but nothing works to move the cursor or otherwise enter my password to log in. All input is ignored, including ctrl+shift+F keys. I tried plugging in a different mouse, no change. Eventually the screen turns off due to no input.

Normal login I believe would be SDDM. The system has been updated successfully for several years now without issue, so this is a significant and unexpected problem.

I am booting on a USB stick today once I’m done work to try and fix things.

Konsole and some other application experiences flickering. I.e. konsole renders flickering while I typing. I tried disabling firmware, wayland, vulcan, tried different kernels, changed adaptive sync and refresg rate - nothing helped. No flickering before the update.

System:
  Kernel: 6.18.26-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
    clocksource: tsc
  Desktop: KDE Plasma v: 6.6.4 tk: Qt v: N/A wm: kwin_wayland vt: 2 dm: N/A
    Distro: Manjaro base: Arch Linux
Machine:
  Type: Laptop System: ASUSTeK product: ASUS Vivobook 18 M1807HA_M1807HA
    v: 1.0 serial: <superuser required>
  Mobo: ASUSTeK model: M1807HA v: 1.0 serial: <superuser required>
    uuid: <superuser required> Firmware: UEFI vendor: American Megatrends LLC.
    v: M1807HA.318 date: 08/11/2025
Battery:
  ID-1: BAT0 charge: 45.2 Wh (69%) condition: 65.5/70 Wh (93.6%) volts: 15.94
    min: 15.86 model: AS3GZEd3jC X160745 type: Unknown serial: <filter>
    charging: status: discharging cycles: N/A
CPU:
  Info: 8-core model: AMD Ryzen 7 260 w/ Radeon 780M Graphics bits: 64
    type: MT MCP smt: enabled arch: Zen 4 rev: 2 cache: L1: 512 KiB L2: 8 MiB
    L3: 16 MiB
  Speed (MHz): avg: 1093 min/max: 417/5103 boost: enabled cores: 1: 1093
    2: 1093 3: 1093 4: 1093 5: 1093 6: 1093 7: 1093 8: 1093 9: 1093 10: 1093
    11: 1093 12: 1093 13: 1093 14: 1093 15: 1093 16: 1093 bogomips: 121370
  Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a
    ssse3 svm
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] HawkPoint1 vendor: ASUSTeK
    driver: amdgpu v: kernel arch: RDNA-3 pcie: speed: 16 GT/s lanes: 16 ports:
    active: eDP-1 empty: DP-1, DP-2, DP-3, DP-4, DP-5, DP-6, DP-7, HDMI-A-1,
    Writeback-1 bus-ID: 03:00.0 chip-ID: 1002:1900 class-ID: 0300 temp: 39.0 C
  Device-2: Sonix ASUS FHD webcam driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 bus-ID: 3-1:2 chip-ID: 3277:0018 class-ID: fe01
    serial: <filter>
  Display: wayland server: X.org v: 1.21.1.22 with: Xwayland v: 24.1.11
    compositor: kwin_wayland driver: X: loaded: amdgpu unloaded: modesetting
    alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: 0
  Monitor-1: eDP-1 model: BOE Display NE180WUM-NY3 res: mode: 1920x1200
    hz: 144 scale: 100% (1) dpi: 126 size: 388x242mm (15.28x9.53")
    diag: 457mm (18") modes: max: 1920x1200 min: 640x480
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
    device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi
    wayland: drv: radeonsi x11: drv: radeonsi
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 26.0.6-arch1.1
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon 780M Graphics (radeonsi
    phoenix ACO DRM 3.64 6.18.26-1-MANJARO) device-ID: 1002:1900
    display-ID: :0.0
  API: Vulkan v: 1.4.341 layers: 6 surfaces: N/A device: 0
    type: integrated-gpu hw: amd driver: mesa radv device-ID: 1002:1900
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor wl: wayland-info
    x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: Advanced Micro Devices [AMD/ATI] Radeon High Definition Audio
    vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s
    lanes: 16 bus-ID: 03:00.1 chip-ID: 1002:1640 class-ID: 0403
  Device-2: Advanced Micro Devices [AMD] Audio Coprocessor vendor: ASUSTeK
    driver: snd_pci_ps v: kernel pcie: speed: 16 GT/s lanes: 16 bus-ID: 03:00.5
    chip-ID: 1022:15e2 class-ID: 0480
  Device-3: Advanced Micro Devices [AMD] Ryzen HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16
    bus-ID: 03:00.6 chip-ID: 1022:15e3 class-ID: 0403
  Device-4: Razer USA Kraken V3 X driver: hid-generic,snd-usb-audio,usbhid
    type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 bus-ID: 1-1:2 chip-ID: 1532:0537
    class-ID: 0300 serial: <filter>
  API: ALSA v: k6.18.26-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator
  Server-1: sndiod v: N/A status: off
  Server-2: JACK v: 1.9.22 status: off
  Server-3: PipeWire v: 1.6.4 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
Network:
  Device-1: Realtek RTL8852BE PCIe 802.11ax Wireless Network vendor: Foxconn
    driver: rtw89_8852be v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: f000
    bus-ID: 01:00.0 chip-ID: 10ec:b852 class-ID: 0280
  IF: wlp1s0 state: up mac: <filter>
  IF-ID-1: br-06025739e5cd state: down mac: <filter>
  IF-ID-2: br-35bf71c6d6a7 state: down mac: <filter>
  IF-ID-3: br-3dead74fd9bc state: down mac: <filter>
  IF-ID-4: br-7c0c8f0b91fc state: down mac: <filter>
  IF-ID-5: br-a5714a369e97 state: down mac: <filter>
  IF-ID-6: br-be2ef058976a state: down mac: <filter>
  IF-ID-7: br-ca273061b702 state: down mac: <filter>
  IF-ID-8: br-d40158f502d2 state: down mac: <filter>
  IF-ID-9: docker0 state: down mac: <filter>
Bluetooth:
  Device-1: Foxconn / Hon Hai Bluetooth Radio driver: btusb v: 0.8 type: USB
    rev: 1.0 speed: 12 Mb/s lanes: 1 bus-ID: 1-3:4 chip-ID: 0489:e123
    class-ID: e001 serial: <filter>
  Report: rfkill ID: hci0 rfk-id: 0 state: down bt-service: enabled,running
    rfk-block: hardware: no software: yes address: see --recommends
Drives:
  Local Storage: total: 953.87 GiB used: 162.69 GiB (17.1%)
  ID-1: /dev/nvme0n1 vendor: Micron model: MTFDKBA1T0QGN-1BN1AABGA
    size: 953.87 GiB speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: V8MA000 temp: 33.9 C scheme: GPT
Partition:
  ID-1: / size: 292.97 GiB used: 44.97 GiB (15.3%) fs: btrfs dev: /dev/dm-2
    mapped: luks-ccbcfee1-7eb1-486d-867d-2c473ed99d3d
  ID-2: /boot/efi size: 998 MiB used: 984 KiB (0.1%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-3: /home size: 625 GiB used: 117.72 GiB (18.8%) fs: btrfs
    dev: /dev/dm-1 mapped: luks-ffd865c9-dbb0-4673-b8fd-1380e4782109
  ID-4: /var/log size: 292.97 GiB used: 44.97 GiB (15.3%) fs: btrfs
    dev: /dev/dm-2 mapped: luks-ccbcfee1-7eb1-486d-867d-2c473ed99d3d
Swap:
  ID-1: swap-1 type: partition size: 34.92 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/dm-0 mapped: luks-ae3aea6d-819f-4c8e-91f3-10e99685a6cd
Sensors:
  System Temperatures: cpu: 45.2 C mobo: N/A gpu: amdgpu temp: 40.0 C
  Fan Speeds (rpm): cpu: 2000 fan-1: 2040
Info:
  Memory: total: 32 GiB note: est. available: 30.61 GiB used: 3.26 GiB (10.7%)
  Processes: 532 Power: uptime: 10m states: freeze,mem,disk suspend: s2idle
    wakeups: 0 hibernate: platform Init: systemd v: 260 default: graphical
  Packages: pm: pacman pkgs: 1379 Compilers: gcc: 15.2.1 Shell: Zsh v: 5.9
    running-in: krusader inxi: 3.3.40

did you even read the announcement? Manjaro 26.1 Bian-May - Preview released - #2 by Lycan

Hi all,
I have a Plasma-wayland session.

after this update sddm login showed a strange behaviour: sometimes the password is not recognized.

I have four users; if I select the user icon and type the password for some users it is refused, for other it is accepted.
The users for which the the password is refused change everytime.

Rebooting don’t solve the problem,

WORKAROUND: click the “other” icon and type username and password (it is always accepted)

There is something I can do?

KDE - Wayland on nvidia 575 (GPU card 1050 Ti) kernel 6.18

> inxi -G
Graphics:
  Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] driver: i915 v: kernel
  Device-2: NVIDIA GP107M [GeForce GTX 1050 Ti Mobile] driver: nvidia
  Display: wayland server: X.org v: 1.21.1.22 with: Xwayland v: 24.1.11
    compositor: kwin_wayland driver: X: loaded: modesetting,nvidia
    unloaded: nouveau dri: iris gpu: i915 resolution: 1920x1080~120Hz

I’ve tried kernel 6.19 on previous update and i’ve reverted back to 6.18 because it didn’t work at all.
I’m keeping 6.18, for now. I’ve not tried 7.0, yet.

The update was smooth with kernel 6.18, thank you.

1 Like

Remove SDDM and install Plasma Login Manager. That might help.

And to make it easier: :point_down:

2 Likes

Suspend breaks on Lenovo Thinkpad P15Gen2 with “Linux gaz 7.0.3-1-MANJARO”.

Resume process just freezed time-to-time. Has no ideas for now.

Report your problem to KDE:

1 Like