[Testing Update] 2025-11-10 - Kernels, Systemd, Mkinitcpio, KDE Gear, Plasma

Announcements Testing Updates
1

Hello community, here we have another set of package updates. Welcome to our new development cycle of Manjaro 25.1.0, code-named ‘Anh-Linh’.We will focus on Plasma 6.5 series and will introduce GNOME 49, maybe Cosmic 1.0 (Beta).

Current Promotions

Recent News

Valkey to replace Redis in the [extra] Repository

2025-04-17 - Andrew Crerar

Valkey, a high-performance key/value datastore, will be replacing redis in the [extra] repository. This change is due to Redis modifying its license from BSD-3-Clause to RSALv2 and SSPLv1 on March 20th, 2024.

Arch Linux Package Maintainers intend to support the availability of the redis package for roughly 14 days from the day of this post, to enable a smooth transition to valkey. After the 14 day transition period has ended, the redis package will be moved to the AUR. Also, from this point forward, the redis package will not receive any additional updates and should be considered deprecated until it is removed.

Users are recommended to begin transitioning their use of Redis to Valkey as soon as possible to avoid possible complications after the 14 day transition window closes.

– Arch Linux - News: Valkey to replace Redis in the [extra] Repository

Previous News
Finding information easier about Manjaro

Finding information easier about Manjaro always has been a topic that needed to be solved. With our new search we have put all Manjaro data accessible in one place and divided by sections so it makes it easier to digest: News – Manjaro

image
image679×348 45.7 KB

Notable Package Updates

Additional Info

Python 3.13 info

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

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

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

Rebuild them all at once:*

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

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.

Our current supported kernels

  • linux54 5.4.301
  • linux510 5.10.246
  • linux515 5.15.196
  • linux61 6.1.158
  • linux66 6.6.116
  • linux612 6.12.57
  • linux617 6.17.7
  • linux618 6.18.0-rc5
  • linux61-rt 6.1.156_rt56
  • linux66-rt 6.6.116_rt66
  • linux612-rt 6.12.49_rt13
  • linux616-rt 6.16.0_rt3
  • linux617-rt 6.17.5_rt7

Package Changes (11/10/25 08:39 CET)

  • testing core x86_64: 26 new and 26 removed package(s)
  • testing extra x86_64: 897 new and 919 removed package(s)
  • testing multilib x86_64: 15 new and 15 removed package(s)

A list of all changes can be found here.

  • No issue, everything went smoothly
  • Yes there was an issue. I was able to resolve it myself.(Please post your solution)
  • Yes i am currently experiencing an issue due to the update. (Please post about it)
0 voters

Check if your mirror has already synced:

1 Like
Manjaro GNOME 25.0.10 won't boot in Virtualbox VM
[Testing Update] 2025-11-06 - Kernels, Mesa, Grub, Nvidia, Plasma 6.5, LibreOffice
CPU stuck at 400MHz in browsers, works fine elsewhere
Manjaro GNOME 25.0.10 won't boot in Virtualbox VM
2

Known issues and solutions

This is a wiki post; please edit as necessary.
Please, consider subscribing to the Testing Updates Announcements RSS feed

Please RTFT (Read This Fine Thread) first before reporting the same issues over and over again!

Note: Do not forget to review your .pacnew files:

:arrow_right: 2025-11-10

mkinitcpio v40 disabled fallback image creation for new installs

mkinitcpio v40, packaging changes and kernel-install - Arch-dev-public - lists.archlinux.org
This is only affects new installs as we can’t change the hook files on existing installs.

To disable fallback image creation on older installed systems

  • Change PRESETS=('default' 'fallback') line to PRESETS=('default') in the respective .preset files in /etc/mkinitcpio.d/.
  • Regenerate initramfs
  • Update your boot loader configuration.

Warning
Disabling all fallback initramfs generation will deprive you of another option to boot into the system in case a default initramfs fails. Before proceeding, make sure you have a bootable installation medium for rescue purposes on hand.

2025-09-28

2025-9-27

Heads up: Gnome 49 is here and wayland is the default.

2025-08-24

Graphical issues on older hardware (Black screen, Flickering) due to mesa 25.2.x update

It seems on older hardware the mesa 25.2.x update created some regressions which may result in black screens or flickering. Some older Nvidia cards with nouveau driver seem to be affected.

You can try to use the 25.1.x series of Mesa via this repo. Simply place it on top of [extra] in your /etc/pacman.conf file and use sudo pacman -Syuu to downgrade.

[mesa-251]
SigLevel = PackageRequired
Server = https://download.manjaro.org/pkgs/mesa

If you have no graphical session available you can access the bootloader by pressing ESC key during boot and select the bootloader entry. Press CTRL+E for edit and search for the words quiet and splash. Delete those and add 3 to the line. Then execute CTRL+x to start your session. You will land in a text console TTY. Login with your user.

Edit the /etc/pacman.conf with nano: sudo nano /etc/pacman.conf. Perform the downgrade and reboot.

Previous testing threads:

3

By default, mkinitcpio 40 no longer produces the fallback initcpio.

4 Likes
4

mkinitcpio needs an update..

2 Likes
5

Please update ffmpeg as well.

6

ffmpeg is a package we import from Arch verbatim, and the version of ffmpeg in the Manjaro Unstable and Testing repositories is 2:8.0-3, which is the same as in Arch.

2 Likes
7

So it will be in the next release release, cool

1 Like
8

Right, that’s by design:

Disabled fallback image creation for new installs.

Generally they are not super useful and people that need them can enable them if
they would like too. This is only affects new installs as we can’t change the
hook files on existing installs.

– mkinitcpio v40, packaging changes and kernel-install - Arch-dev-public - lists.archlinux.org

1 Like
9

Fallback images are for wussies.

/me hides under the table :stuck_out_tongue:

6 Likes
10

Fallback images are like suspenders. If you’re wearing a belt, you (almost) never need them.

But when it comes to computers, software, and my data, I always wear a belt and suspenders, and sometimes a safety pin too. (In real life, a belt is enough for me.)
:footprints:
3 kernel, fallback, btrfs-raid (2 different SSDs), snapshots(@,@home,@…), backups(external) & live-USB

3 Likes
11

I was so happy when pacdiff’s merge feature got fixed in Manjaro after being broken for a few months. (Last year was it?)

I’ve never done it any other way! Update every system easily with ssh, and much quicker than meld for me.

Now it’s doing something really wonky.

Even though I should not get this, for one pacnew I got:

==> pacnew file found for /etc/default/grub-btrfs/config
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q] m
  -> Unable to find an older package to base merge on.

I skipped that file, and moved on to one of the other 8 I think I had. I was 3 or 4 in when I realised the merge view was off.

The remaining ones, (V)iew and (M)erge are completely different diffs, (V)iew being correct.

For now, I have to rollback, I saved botched pacnews. :slightly_frowning_face:

12

Did you remove grub-btrfs 4.13-2 from your cache?

Always leave at least one older version. I usually leave three and use sudo paccache -rvk3 occasionally.

I suppose you could downgrade temporarily to that version with sudo manjaro-downgrade grub-btrfs, then update and deal with the pacnew. Not tested, however in theory I imagine that should work.

1 Like
13

What to do for existing installs?

1 Like
14

Copy the hook.preset to a configurable location and uncomment the fallback bits:

sudo cp /usr/share/mkinitcpio/hook.preset /etc/mkinitcpio.conf.d/
1 Like
15

It’s not about the package, it’s the (M)erge feature of pacdiff.

The other ones that didn’t error like that one, weren’t handling pacnew files correctly either.

Edit:

I forgot I undid a whole slew of pacnew files from the last massive update. (Then forgot to move them back.)

User error.

I’m still scarred from the months of mergeless pacdiff for everyone! I can now sleep again.

16

interesting change. Frankly, as a sdboot user, this saves a lot of space efi partitions, as fallback images are huge. With just one kernel it is usually enough, but I had run into problems with two kernels present (i.e. four initram images).

17

ArchWiki - mkinicpio - Disabling fallback intramfs generation

The generation of fallback images can be disabled:

  • Change PRESETS=('default' 'fallback') line to PRESETS=('default') in the respective .preset files in /etc/mkinitcpio.d/.
  • Remove the fallback initramfs images in /boot/.
  • Update your boot loader configuration.

Warning
Disabling all fallback initramfs generation will deprive you of another option to boot into the system in case a default initramfs fails. Before proceeding, make sure you have a bootable installation medium for rescue purposes on hand.

7 Likes
18

Can gajim 2.4 and the required deps be snuck into this round of updates? :crossed_fingers:

19

It already is.

1 Like
20

Switched from stable to testing. Going well for now. Thanks for the work.

3 Likes