[Testing Update] 2025-11-17 - Kernel 6.18-rc6, Thunderbird 145.0, COSMIC Beta 6

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

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.58
  • linux617 6.17.8
  • linux618 6.18.0-rc6
  • linux61-rt 6.1.158_rt58
  • linux66-rt 6.6.116_rt66
  • linux612-rt 6.12.57_rt14
  • linux616-rt 6.16.0_rt3
  • linux617-rt 6.17.5_rt7

Package Changes (11/17/25 11:26 CET)

  • testing core x86_64: 5 new and 5 removed package(s)
  • testing extra x86_64: 458 new and 456 removed package(s)
  • testing multilib x86_64: 3 new and 3 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:


2 Likes

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.

Previous testing threads:

The 6.18-rc6 kernel is working well on my laptop,

3 Likes

Suspend is no longer working reliable for me. The system does not come up, does not react to any input and reboots after some time. I see the message The system will suspend now! twice in my logs, but have no clue if something else is suspicious here.

Nov 18 00:04:15 user systemd-logind[922]: The system will suspend now!
Nov 18 00:04:15 user ModemManager[994]: <msg> [sleep-monitor-systemd] system is about to suspend
Nov 18 00:04:15 user ModemManager[994]: <msg> [sleep-monitor-systemd] ready to sleep; dropping inhibitor
Nov 18 00:04:15 user NetworkManager[915]: <info>  [1763420655.6305] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Nov 18 00:04:15 user NetworkManager[915]: <info>  [1763420655.6306] device (wlp15s0): state change: unavailable -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
Nov 18 00:04:15 user NetworkManager[915]: <info>  [1763420655.6309] device (wlp15s0): set-hw-addr: reset MAC address to 2C:98:11:80:FF:8B (unmanage)
Nov 18 00:04:15 user NetworkManager[915]: <info>  [1763420655.6311] manager: NetworkManager state is now ASLEEP
Nov 18 00:04:15 user NetworkManager[915]: <info>  [1763420655.6312] device (enp14s0): state change: activated -> deactivating (reason 'sleeping', managed-type: 'full')
Nov 18 00:04:15 user systemd[1]: Starting Network Manager Script Dispatcher Service...
Nov 18 00:04:15 user systemd[1]: Started Network Manager Script Dispatcher Service.
Nov 18 00:04:15 user NetworkManager[915]: <info>  [1763420655.6664] device (enp14s0): state change: deactivating -> disconnected (reason 'sleeping', managed-type: 'full')
Nov 18 00:04:15 user NetworkManager[915]: <info>  [1763420655.6669] dhcp4 (enp14s0): canceled DHCP transaction
Nov 18 00:04:15 user NetworkManager[915]: <info>  [1763420655.6669] dhcp4 (enp14s0): activation: beginning transaction (timeout in 45 seconds)
Nov 18 00:04:15 user NetworkManager[915]: <info>  [1763420655.6669] dhcp4 (enp14s0): state changed no lease
Nov 18 00:03:03 user crontab[15285]: (root) LIST (root)
Nov 18 00:03:03 user crontab[15286]: (root) LIST (root)
Nov 18 00:03:03 user systemd[1]: run-timeshift-15230-backup.mount: Deactivated successfully.
Nov 18 00:03:03 user systemd[1]: tmp-grub\x2dbtrfs.TqjfzV02Jb.mount: Deactivated successfully.
Nov 18 00:03:03 user dbus-broker-launch[3566]: Noticed file-system modification, trigger reload.
Nov 18 00:03:03 user dbus-broker-launch[3566]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +31: Eavesdropping is deprecated and ignored
Nov 18 00:03:03 user dbus-broker-launch[3566]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +33: Eavesdropping is deprecated and ignored
Nov 18 00:03:03 user dbus-broker-launch[3566]: Noticed file-system modification, trigger reload.
Nov 18 00:03:03 user dbus-broker-launch[3566]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +31: Eavesdropping is deprecated and ignored
Nov 18 00:03:03 user dbus-broker-launch[3566]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +33: Eavesdropping is deprecated and ignored
Nov 18 00:03:04 user gnome-shell[3796]: Source ID 19457 was not found when attempting to remove it
Nov 18 00:03:04 user sudo[14977]: pam_unix(sudo:session): session closed for user root
Nov 18 00:03:04 user nordvpnd[919]: 2025/11/18 00:03:04 [Debug] 2 active user processes found
Nov 18 00:03:09 user gnome-shell[3796]: updates_checker.vala:59: check updates
Nov 18 00:03:09 user systemd[1]: Starting Pamac Daemon...
Nov 18 00:03:09 user systemd[1]: Started Pamac Daemon.
Nov 18 00:03:09 user systemd[1]: Starting Locale Service...
Nov 18 00:03:09 user systemd[1]: Started Locale Service.
Nov 18 00:03:10 user systemd[1]: pamac-daemon.service: Deactivated successfully.
Nov 18 00:03:14 user systemd[1]: fprintd.service: Deactivated successfully.
Nov 18 00:03:23 user rtkit-daemon[1352]: Supervising 8 threads of 5 processes of 1 users.
Nov 18 00:03:23 user rtkit-daemon[1352]: Supervising 8 threads of 5 processes of 1 users.
Nov 18 00:03:26 user rtkit-daemon[1352]: Supervising 8 threads of 5 processes of 1 users.
Nov 18 00:03:26 user rtkit-daemon[1352]: Supervising 8 threads of 5 processes of 1 users.
Nov 18 00:03:39 user systemd[1]: systemd-localed.service: Deactivated successfully.
Nov 18 00:04:02 user systemd[1]: Starting Time & Date Service...
Nov 18 00:04:02 user systemd[1]: Started Time & Date Service.
Nov 18 00:04:03 user systemd[3543]: app-gnome-zen\x2dbrowser-12990.scope: Consumed 17.409s CPU time, 1.8G memory peak.
Nov 18 00:04:15 user systemd-logind[922]: The system will suspend now!
Nov 18 00:04:15 user ModemManager[994]: <msg> [sleep-monitor-systemd] system is about to suspend
Nov 18 00:04:15 user ModemManager[994]: <msg> [sleep-monitor-systemd] ready to sleep; dropping inhibitor
Nov 18 00:04:15 user NetworkManager[915]: <info>  [1763420655.6305] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Nov 18 00:04:15 user NetworkManager[915]: <info>  [1763420655.6306] device (wlp15s0): state change: unavailable -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
Nov 18 00:04:15 user NetworkManager[915]: <info>  [1763420655.6309] device (wlp15s0): set-hw-addr: reset MAC address to 2C:98:11:80:FF:8B (unmanage)
Nov 18 00:04:15 user NetworkManager[915]: <info>  [1763420655.6311] manager: NetworkManager state is now ASLEEP
Nov 18 00:04:15 user NetworkManager[915]: <info>  [1763420655.6312] device (enp14s0): state change: activated -> deactivating (reason 'sleeping', managed-type: 'full')
Nov 18 00:04:15 user systemd[1]: Starting Network Manager Script Dispatcher Service...
Nov 18 00:04:15 user systemd[1]: Started Network Manager Script Dispatcher Service.
Nov 18 00:04:15 user NetworkManager[915]: <info>  [1763420655.6664] device (enp14s0): state change: deactivating -> disconnected (reason 'sleeping', managed-type: 'full')
Nov 18 00:04:15 user NetworkManager[915]: <info>  [1763420655.6669] dhcp4 (enp14s0): canceled DHCP transaction
Nov 18 00:04:15 user NetworkManager[915]: <info>  [1763420655.6669] dhcp4 (enp14s0): activation: beginning transaction (timeout in 45 seconds)
Nov 18 00:04:15 user NetworkManager[915]: <info>  [1763420655.6669] dhcp4 (enp14s0): state changed no lease
Nov 18 00:03:03 user crontab[15285]: (root) LIST (root)
Nov 18 00:03:03 user crontab[15286]: (root) LIST (root)
Nov 18 00:03:03 user systemd[1]: run-timeshift-15230-backup.mount: Deactivated successfully.
Nov 18 00:03:03 user systemd[1]: tmp-grub\x2dbtrfs.TqjfzV02Jb.mount: Deactivated successfully.
Nov 18 00:03:03 user dbus-broker-launch[3566]: Noticed file-system modification, trigger reload.
Nov 18 00:03:03 user dbus-broker-launch[3566]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +31: Eavesdropping is deprecated and ignored
Nov 18 00:03:03 user dbus-broker-launch[3566]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +33: Eavesdropping is deprecated and ignored
Nov 18 00:03:03 user dbus-broker-launch[3566]: Noticed file-system modification, trigger reload.
Nov 18 00:03:03 user dbus-broker-launch[3566]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +31: Eavesdropping is deprecated and ignored
Nov 18 00:03:03 user dbus-broker-launch[3566]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +33: Eavesdropping is deprecated and ignored
Nov 18 00:03:04 user gnome-shell[3796]: Source ID 19457 was not found when attempting to remove it
Nov 18 00:03:04 user sudo[14977]: pam_unix(sudo:session): session closed for user root
Nov 18 00:03:04 user nordvpnd[919]: 2025/11/18 00:03:04 [Debug] 2 active user processes found
Nov 18 00:03:09 user gnome-shell[3796]: updates_checker.vala:59: check updates
Nov 18 00:03:09 user systemd[1]: Starting Pamac Daemon...
Nov 18 00:03:09 user systemd[1]: Started Pamac Daemon.
Nov 18 00:03:09 user systemd[1]: Starting Locale Service...
Nov 18 00:03:09 user systemd[1]: Started Locale Service.
Nov 18 00:03:10 user systemd[1]: pamac-daemon.service: Deactivated successfully.
Nov 18 00:03:14 user systemd[1]: fprintd.service: Deactivated successfully.
Nov 18 00:03:23 user rtkit-daemon[1352]: Supervising 8 threads of 5 processes of 1 users.
Nov 18 00:03:23 user rtkit-daemon[1352]: Supervising 8 threads of 5 processes of 1 users.
Nov 18 00:03:26 user rtkit-daemon[1352]: Supervising 8 threads of 5 processes of 1 users.
Nov 18 00:03:26 user rtkit-daemon[1352]: Supervising 8 threads of 5 processes of 1 users.
Nov 18 00:04:02 user systemd[1]: Starting Time & Date Service...
Nov 18 00:04:02 user systemd[1]: Started Time & Date Service.
Nov 18 00:04:02 user systemd[1]: Starting Time & Date Service...
Nov 18 00:04:02 user systemd[1]: Started Time & Date Service.
Nov 18 00:04:03 user systemd[3543]: app-gnome-zen\x2dbrowser-12990.scope: Consumed 17.409s CPU time, 1.8G memory peak.
Nov 18 00:04:15 user systemd-logind[922]: The system will suspend now!
Nov 18 00:04:15 user ModemManager[994]: <msg> [sleep-monitor-systemd] system is about to suspend
Nov 18 00:04:15 user ModemManager[994]: <msg> [sleep-monitor-systemd] ready to sleep; dropping inhibitor
Nov 18 00:04:15 user NetworkManager[915]: <info>  [1763420655.6305] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Nov 18 00:04:15 user NetworkManager[915]: <info>  [1763420655.6306] device (wlp15s0): state change: unavailable -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
Nov 18 00:04:15 user NetworkManager[915]: <info>  [1763420655.6309] device (wlp15s0): set-hw-addr: reset MAC address to 2C:98:11:80:FF:8B (unmanage)
Nov 18 00:04:15 user NetworkManager[915]: <info>  [1763420655.6311] manager: NetworkManager state is now ASLEEP
Nov 18 00:04:15 user NetworkManager[915]: <info>  [1763420655.6312] device (enp14s0): state change: activated -> deactivating (reason 'sleeping', managed-type: 'full')
Nov 18 00:04:15 user systemd[1]: Starting Network Manager Script Dispatcher Service...
Nov 18 00:04:15 user systemd[1]: Started Network Manager Script Dispatcher Service.
Nov 18 00:04:15 user NetworkManager[915]: <info>  [1763420655.6664] device (enp14s0): state change: deactivating -> disconnected (reason 'sleeping', managed-type: 'full')
Nov 18 00:04:15 user NetworkManager[915]: <info>  [1763420655.6669] dhcp4 (enp14s0): canceled DHCP transaction
Nov 18 00:04:15 user NetworkManager[915]: <info>  [1763420655.6669] dhcp4 (enp14s0): activation: beginning transaction (timeout in 45 seconds)
Nov 18 00:04:15 user NetworkManager[915]: <info>  [1763420655.6669] dhcp4 (enp14s0): state changed no lease
Nov 18 00:04:15 user NetworkManager[915]: <info>  [1763420655.6669] dhcp6 (enp14s0): canceled DHCP transaction
Nov 18 00:04:15 user NetworkManager[915]: <info>  [1763420655.6669] dhcp6 (enp14s0): activation: beginning transaction (timeout in 45 seconds)
Nov 18 00:04:15 user NetworkManager[915]: <info>  [1763420655.6670] dhcp6 (enp14s0): state changed no lease
Nov 18 00:04:15 user gnome-shell[3796]: Type GITypeInfo of property AccountsService.User::password-mode does not match return type GITypeInfo of getter get_password_mode. Falling back to slow path
Nov 18 00:04:15 user gsd-media-keys[3946]: Unable to get default sink
Nov 18 00:04:15 user NetworkManager[915]: <info>  [1763420655.8381] device (enp14s0): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
Nov 18 00:04:15 user kernel: r8169 0000:0e:00.0 enp14s0: Link is Down
Nov 18 00:04:16 user gnome-shell[3796]: Cursor update failed: drmModeAtomicCommit: Invalid argument
Nov 18 00:04:16 user systemd[1]: Reached target Sleep.
Nov 18 00:04:16 user systemd[1]: Starting System Suspend...
Nov 18 00:04:16 user systemd[1]: session-3.scope: Unit now frozen-by-parent.
Nov 18 00:04:16 user systemd[1]: user@1000.service: Unit now frozen-by-parent.
Nov 18 00:04:16 user systemd[1]: user-1000.slice: Unit now frozen-by-parent.
Nov 18 00:04:16 user systemd[1]: user.slice: Unit now frozen.
Nov 18 00:04:16 user systemd-sleep[18237]: Successfully froze unit 'user.slice'.
Nov 18 00:04:16 user systemd-sleep[18237]: Performing sleep operation 'suspend'...
-- Boot ca8e4bbf18b74cc08c2d551d84974f9d --
Nov 18 22:50:55 user kernel: Linux version 6.12.58-1-MANJARO (linux612@manjaro) (gcc (GCC) 15.2.1 20251112, GNU ld (GNU Binutils) 2.45.1) #1 SMP PREEMPT_DYNAMIC Thu, 13 Nov 2025 21:49:23 +0000

I’ve only taken a very quick glance at your logs, but it could be the same issue which has been fixed in Plasma 6.5.3:

Plasma 6.5.3

Worked around a kernel bug that that made some systems fail to go to sleep the first time it was initiated. (Bhushan Shah, link)

Plasma 6.5.3 has reached Unstable branch:

mbn info plasma-desktop -q | grep -Ev 'Name|Repository|Packager'
Branch         : archlinux
Version        : 6.5.3-1
Build Date     : Wed 19 Nov 2025 00:50:54 
Branch         : unstable
Version        : 6.5.3-1
Build Date     : Wed 19 Nov 2025 00:50:54 
Branch         : testing
Version        : 6.5.2-1
Build Date     : Fri 07 Nov 2025 09:43:22 
Branch         : stable
Version        : 6.3.6-1
Build Date     : Wed 09 Jul 2025 02:10:33 

mbn can be found in the manjaro-check-repos package

If you want to give it a try, here are preprepared instructions for switching branches:

To switch to Testing branch:

sudo pacman-mirrors -a -B testing && sudo pacman-mirrors --continent && sudo pacman -Syyu

or, to switch to Unstable branch:

sudo pacman-mirrors -a -B unstable && sudo pacman-mirrors --continent && sudo pacman -Syyu
1 Like

Thanks man, but I am running GNOME under testing, so this is not for me I suppose.

1 Like

Ooops. :flushed_face: Sorry.

As I said, I only took a quick glance at the logs (didn’t see the gnome-shell line). I had seen the Plasma fix just a few days ago, so my brain connected the two issues without thinking too much about it.

Edit: still, as the issue with Plasma was considered a kernel bug, it might be worth testing by booting into an older kernel (say, linux612 LTS). Maybe the same kernel issue is also occurring with entering sleep mode on GNOME?

1 Like

@scotty65 he is already using linux612

2 Likes

I seem to be having one of those days… :face_with_spiral_eyes: