[Unstable Update] May 2026

Announcements Unstable Updates
,
1

Welcome to the new monthly unstable branch thread.

Recent News

Breaking changes for all users of varnish, which is renamed to vinyl-cache

2026-05-25 - Sven-Hendrik Haase

The Varnish project has renamed itself to Vinyl Cache. We followed this rename with a new vinyl-cache package. This upgrade results in breaking changes and users are advised to study these changes and how it affects them before following the replacement. All references to “varnish” have been changed to “vinyl” in all binaries and directories.

At minimum, users will have to:

  • rename /etc/varnish to /etc/vinyl-cache
  • rename /var/lib/varnish to /var/lib/vinyl-cache
  • fix up ownership of files inside /var/lib/varnish
  • user varnish becomes vinyl
  • group varnish becomes vinyl
  • user varnishlog becomes vinyllog
  • user vcache remains the same
  • disable the old varnish.service and varnishncsa.service systemd units
  • enable the new vinyl-cache.service and vinylncsa.service systemd units

Meanwhile, the varnish package has been dropped from [extra]. We’re not currently planning to maintain a new varnish package as it’s a different upstream project.

– Arch Linux - News: Breaking changes for all users of `varnish`, which is renamed to `vinyl-cache`

Notable Package Changes

Known Issues

Additional Info

Python 3.14 info

:information_source: You will need to rebuild any AUR Python packages that install files to site-packages or link to libpython3.13.so.

Print a list of of packages that have files in /usr/lib/python3.13/ :

pacman -Qoq /usr/lib/python3.13/

Rebuild them all at once:*

pamac build $(pacman -Qoq /usr/lib/python3.13)

Use rebuild-detector to see if anything else needs to be rebuilt:

 checkrebuild

* It’s recommended to clean your build cache first with pamac clean --build-files

Info about AUR packages

:warning: AUR (Arch User Repository) packages are neither supported by Arch nor Manjaro. Posts about them in Announcements topics are off-topic and will be flagged, moved or removed without warning.

For help with AUR packages, please create a new topic in Support > AUR and a helpful volunteer may be able to assist you.

Get our latest daily developer images now from Github: Plasma, GNOME, XFCE. You can get the latest stable releases of Manjaro from CDN77.

Check if your mirror has already synced:

1 Like
[Unstable Update] April 2026
2

i hit the snag of having archlinux-keyring-wkd-sync failing repeatedly. with same troublesome expired key. followed;

to remove the expired key and it is working again

3

Can’t reproduce. What key? That thread is from 2024 and the key mentioned there was long removed.

4

same key; ‘andrew@archlinux.org’. don’t know if it was failing all this time, only noticed now. i only keep, weeks worth of logs. so doubt i can peek at last week’s refresh failed or not

5

From my system (I also don’t keep a lot of logs)

apr 24 20:25:59 gid archlinux-keyring-wkd-sync[100494]: Skipping key B8151B117037781095514CA7BBDFFC92306B1121 with UID andrew@archlinux.org...
apr 24 20:26:09 gid archlinux-keyring-wkd-sync[100494]: Refreshing key B8151B117037781095514CA7BBDFFC92306B1121 with UID andrew@archlinux.org...
apr 24 20:26:09 gid archlinux-keyring-wkd-sync[100689]: gpg: error retrieving 'andrew@archlinux.org' via WKD: No data
apr 24 20:26:12 gid archlinux-keyring-wkd-sync[100494]: Error refreshing key B8151B117037781095514CA7BBDFFC92306B1121 with UID andrew@archlinux.org.

I’ve not seen the failing of archlinux-keyring-wkd-sync but do see the refresh error.
Solved this manually by deleting the key.

6

it seems cuda 13.2 have issues with gcc 16.1 compatibility. Therefore it is not possible to build projects that use it, such as llama.cpp.
Can you tell me why kwin is using version 6.6.4-1.0 instead of 6.6.4-1? I’m curious and I couldn’t find this package on your gitlab

7

Could this be the answer?

All 3 branches are on kwin v6.6.4-1.0

1 Like
8

thanks, that’s probably the reason. Unfortunately, I couldn’t see the list of changes in the package on gitlab as the arch allows. sorry to disturb you

1 Like
9

just about turbostat ( that coming from kernel linux )

sudo turbostat 
turbostat version 2026.02.14 - Len Brown <lenb@kernel.org>
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-7.0-x86_64 root=UUID=d96e5436-0218-4bfb-87f0-cb7b5418df96 rw amdgpu.ppfeaturemask=0xffffffff "acpi_osi=!Windows 2015" "acpi_os_name=Microsoft Windows" nowatchdog nvme_load=YES splash systemd.unified_cgroup_hierarchy=true scsi_mod.use_blk_mq=1
CPUID(0): AuthenticAMD 0x10 CPUID levels
CPUID(1): family:model:stepping 0x1a:44:0 (26:68:0) microcode 0xb404035
CPUID(0x80000000): max_extended_levels: 0x80000028
CPUID(1): SSE3 MONITOR No-SMX No-EIST No-TM2 No-HV TSC MSR No-ACPI-TM HT No-TM
CPUID(6): APERF, No-TURBO, No-DTS, No-PTM, No-HWP, No-HWPnotify, No-HWPwindow, No-HWPepp, No-HWPpkg, No-EPB
CPUID(7): No-SGX No-Hybrid
cpu0: cpufreq driver: amd-pstate-epp
cpu0: cpufreq governor: powersave
cpufreq boost: 1
/dev/cpu_dma_latency: 2000000000 usec (default)
current_driver: acpi_idle
current_governor: menu
current_governor_ro: menu
cpu0: POLL: CPUIDLE CORE POLL IDLE
cpu0: C1: ACPI FFH MWAIT 0x0
cpu0: C2: ACPI IOPORT 0x414
cpu0: C3: ACPI IOPORT 0x415
RAPL: 234 sec. Joule Counter Range, at 280 Watts
intel-rapl:0: package-0 disabled
intel-rapl:0/intel-rapl:0:0: core disabled
cpu0: MSR_RAPL_PWR_UNIT: 0x000a1000 (1.000000 Watts, 0.000015 Joules, 0.000977 sec.)
turbostat: turbostat.c:8687: rapl_perf_init: Assertion `next_domain < num_domains' failed.
Abandon                    sudo turbostat
10

No issue here with Intel. :man_shrugging:

turbostat version 2026.02.14 - Len Brown <lenb@kernel.org>
Kernel command line: root=UUID=cf70171e-27dd-43ec-a0b7-52a1fa96be2a rw add_efi_memmap initrd=boot\intel-ucode.img initrd=boot\initramfs-7.0-x86_64.img dyndbg=
CPUID(0): GenuineIntel 0x20 CPUID levels
CPUID(1): family:model:stepping 0x6:9a:3 (6:154:3) microcode 0x43b
12

I would like to try the new ntfs kernel module that will be available in linux 7.1.0. I checked the modules loaded in the linux 7.1.0rc2 kernel, but only found ntfs3. Is there a way to use the new kernel with the provided binaries or do I need to compile the kernel myself? In case of the latter, is there a recent tutorial for compiling the manjaro kernel?

Some further questions: Will manjaro enable the new driver in the final 7.1.0 kernel? If ntfs and ntfs3 are mutually exclusive, which one will manjaro support?

I have found the solution myself. The kernel module is included and can be mounted with ntfs. I use

ntfs defaults,iocharset=utf8,uid=1000,gid=1000,umask=000,noatime,windows_names,sparse 0 0

It can coexist with ntfs-3g and ntfs3. As ntfs-3g hijacks ntfs, I had to use

sudo mv /usr/bin/mount.ntfs /usr/bin/mount.ntfs.fuse

to prevent this.

13

turbostat : solved with last build this morning
local/turbostat 7.0.3-1 (linux-tools)
Report processor frequency and idle statistics

14

can you tell me more? I’m still getting same error, kernel 7.1-rc2

15

What build? 7.0.3-1 is still the latest version.

16

Sure? I’d guess 7.0.3-2 is latest:

$ uname -a
Linux columbo 7.0.3-2-MANJARO #1 SMP PREEMPT_DYNAMIC Sat, 02 May 2026 22:44:28 +0000 x86_64 GNU/Linux
17

We’re talking about the version of turbostat. :wink:

EDIT: Ah, apparently the 7.0.3-2 GCC 16 rebuild of the kernel helped, then.

19

missing this morning linux618-nvidia-580xx

20

Nothing is missing, 580.159.03-5 was pushed earlier and I’m currently pushing 580.159.03-6 along with the new kernel updates.

21

thats new

Mai 10 19:20:59 org_kde_powerdevil[1294]: [  1294] Watching for DPMS state changes unimplemented
Mai 10 19:20:59 org_kde_powerdevil[1294]: [  1294][  1.410838] Time since library initialized:   1.410838 seconds
Mai 10 19:20:59 org_kde_powerdevil[1294]: [  1294][  1.410839] Extra delay starting dw_start_watch_displays: 0 millisec
22

@Yochanan in upgrade of plasma 6.6.5, kwin is still seem to be stuck at (6.6.4-1.0)