[Testing Update] 2025-11-27 - Firmware, GNOME, Xorg, Firefox, Qt, ROCm

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.117
  • linux612 6.12.59
  • linux617 6.17.9
  • linux618 6.18.0-rc7
  • linux61-rt 6.1.158_rt58
  • linux66-rt 6.6.116_rt66
  • linux612-rt 6.12.57_rt14
  • linux617-rt 6.17.5_rt7

Package Changes (11/27/25 11:24 CET)

  • testing core x86_64: 20 new and 20 removed package(s)
  • testing extra x86_64: 709 new and 707 removed package(s)
  • testing multilib x86_64: 8 new and 8 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:

5 Likes
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 - sudo mkinitcpio -P
  • Update boot loader - sudo update-grub

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:

3

I moved to Testing today, in the hopre that I can contribute more, in the form of bug reporting. Concurrent, it appears, with this update.

Other than the unexpected changes to mkinitcpio.conf via a pacnew, I have experienced no issues.

4 Likes
4

Have you seen this: Attention when updating to Qt 6.10.1

1 Like
5

@frdbr well: upgpkg: 6.5.3-2: Qt 6.10.1 rebuild (27460c0b) · Commits · Arch Linux / Packaging / Packages / plasma-workspace · GitLab

1 Like
6

Testing is having more and more issues on my end. Today I got a complete freeze of the system, the first time since ages.

Nov 27 18:21:19 user kernel: BUG: unable to handle page fault for address: ffffd6ce4346bb58
Nov 27 18:21:19 user kernel: BUG: unable to handle page fault for address: ffffd6ce4346bb58
Nov 27 18:21:19 user kernel: #PF: supervisor read access in kernel mode
Nov 27 18:21:19 user kernel: #PF: error_code(0x0000) - not-present page
Nov 27 18:21:19 user kernel: Fixing recursive fault but reboot is needed!
Nov 27 18:21:19 user kernel: BUG: scheduling while atomic: gameoverlayui/43453/0x00000000
Nov 27 18:22:19 user kernel: rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
Nov 27 18:22:19 user kernel: rcu:         Tasks blocked on level-1 rcu_node (CPUs 0-11): P43453/1:b..l
Nov 27 18:22:19 user kernel: rcu:         (detected by 0, t=18002 jiffies, g=1112949, q=39513 ncpus=24)
Nov 27 18:22:47 user kernel: rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { P43453 } 18337 jiffies s: 8441 root: 0x1/.
Nov 27 18:22:47 user kernel: rcu: blocking rcu_node structures (internal RCU debug): l=1:0-11:0x0/T
Nov 27 18:25:19 user kernel: rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
Nov 27 18:25:19 user kernel: rcu:         Tasks blocked on level-1 rcu_node (CPUs 0-11): P43453/1:b..l
Nov 27 18:25:19 user kernel: rcu:         (detected by 0, t=72007 jiffies, g=1112949, q=157187 ncpus=24)
Nov 27 18:25:51 user kernel: rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { P43453 } 73633 jiffies s: 8441 root: 0x1/.
Nov 27 18:25:51 user kernel: rcu: blocking rcu_node structures (internal RCU debug): l=1:0-11:0x0/T
Nov 27 18:26:17 user systemd-logind[918]: Failed to get load state of suspend.target: Connection timed out
Nov 27 18:26:42 user systemd-logind[918]: Failed to get load state of poweroff.target: Connection timed out
Nov 27 18:27:07 user systemd-logind[918]: Failed to get load state of reboot.target: Connection timed out
Nov 27 18:27:32 user systemd-logind[918]: Failed to get load state of suspend.target: Connection timed out
Nov 27 18:27:57 user systemd-logind[918]: Failed to get load state of hibernate.target: Connection timed out
Nov 27 18:28:19 user kernel: rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
Nov 27 18:28:19 user kernel: rcu:         Tasks blocked on level-1 rcu_node (CPUs 0-11): P43453/1:b..l
Nov 27 18:28:19 user kernel: rcu:         (detected by 0, t=126012 jiffies, g=1112949, q=280344 ncpus=24)
Nov 27 18:29:02 user kernel: rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { P43453 } 130977 jiffies s: 8441 root: 0x1/.
Nov 27 18:29:02 user kernel: rcu: blocking rcu_node structures (internal RCU debug): l=1:0-11:0x0/T
Nov 27 18:31:19 user kernel: rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
Nov 27 18:31:19 user kernel: rcu:         Tasks blocked on level-1 rcu_node (CPUs 0-11): P43453/1:b..l
Nov 27 18:31:19 user kernel: rcu:         (detected by 13, t=180017 jiffies, g=1112949, q=318447 ncpus=24)
Nov 27 18:32:13 user kernel: rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { P43453 } 188321 jiffies s: 8441 root: 0x1/.
Nov 27 18:32:13 user kernel: rcu: blocking rcu_node structures (internal RCU debug): l=1:0-11:0x0/T
Nov 27 18:34:04 user kernel: Bluetooth: hci0: Opcode 0x2041 failed: -110
Nov 27 18:34:04 user kernel: Bluetooth: hci0: start background scanning failed: -110
-- Boot 0c9c14ddaeb8487da80e37eef46d226c --
7

if you have this in your journal log

x86/split lock detection: #DB: warning on user-space bus_locks

see for more split_lock_detect=off

1 Like
8

That’s not the case, but thanks anyway!

9

Also need to rebuild Plasma-Desktop Attention when updating to Qt 6.10.1

1 Like
10

2 posts were split to a new topic: Lost 2560x1080 resolution

11

Since this update (Nov 27):

Nov 28 11:40:50  gnome-control-c[2426]: Settings schema 'org.gnome.desktop.a11y.interface' does not contain a key named 'reduced-motion'

Nov 28 11:40:50  systemd-coredump[2442]: Process 2426 (gnome-control-c) of user 1000 dumped core.

Same on two machines…
EDIT:
Nov 28 15:31:12 systemd[1029]: dbus-:1.1-org.gnome.Settings.GlobalShortcutsProvider@0.service: Failed with result 'core-dump'

12

Something positive (as this is seldom in the current days …):

  • With the last update the time for wakeup from sleep is visibly faster - I would tend to compare it 2-3 times faster in comparison to the time before this update
  • Visible on 3 different laptops with different GPUs, so this is not related to the graphic driver but to the system (Gnome, systemd, …) itself
13

Most likely fixed in Release 49.2.2 · GNOME/gnome-control-center · GitHub

1 Like
14

I have tried all three ways to Gnome screenshot. None seem to work (which they all used to).

inxi -Gxxx 
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Cedar [Radeon HD
    5000/6000/7350/8350 Series] vendor: VISIONTEK driver: radeon v: kernel
    arch: TeraScale-2 pcie: speed: 2.5 GT/s lanes: 4 ports: active: HDMI-A-1
    empty: DVI-D-1,VGA-1 bus-ID: 04:00.0 chip-ID: 1002:68f9 class-ID: 0300
  Device-2: NVIDIA GA102 [GeForce RTX 3080 Lite Hash Rate] vendor: Gigabyte
    driver: vfio-pci v: N/A arch: Ampere pcie: speed: 2.5 GT/s lanes: 8
    bus-ID: 0c:00.0 chip-ID: 10de:2216 class-ID: 0300
  Display: wayland server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.9
    compositor: gnome-shell v: 49.2 driver: X: loaded: modesetting,radeon
    alternate: fbdev,vesa dri: nouveau,r600 gpu: radeon display-ID: 0
  Monitor-1: HDMI-A-1 model: Acer XB241YU serial: T6CAA0018500
    res: 2560x1440 dpi: 123 size: 527x296mm (20.75x11.65") diag: 604mm (23.8")
    modes: max: 1920x1080 min: 640x480
  API: EGL v: 1.5 hw: drv: amd r600 platforms: device: 0 drv: r600 device: 1
    drv: swrast gbm: drv: kms_swrast surfaceless: drv: r600 wayland: drv: r600
    inactive: x11
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: mesa v: 25.2.7-arch1.1
    note: incomplete (EGL sourced) renderer: llvmpipe (LLVM 21.1.5 256 bits),
    AMD CEDAR (DRM 2.51.0 / 6.17.9-1-MANJARO LLVM 21.1.5)
  Info: Tools: api: eglinfo,glxinfo x11: xprop,xrandr

This may be a me problem as these warnings are new-ish for my GPU. And this is the first time I’ve noticed my inxi says note: incomplete (EGL sourced) for OpenGL.

Logs:

Nov 28 15:12:46 mbox org.gnome.Screenshot[176650]: Unable to use GNOME Shell's builtin screenshot interface: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: ScreenshotWindow is not allowed
Nov 28 15:12:46 mbox org.gnome.Screenshot[176650]: Unable to capture a screenshot of any window
Nov 28 15:12:51 mbox org.gnome.Lollypop.SearchProvider[179481]: /usr/lib/lollypop/lollypop-sp:71: DeprecationWarning: Gio.DBusConnection.register_object is deprecated
Nov 28 15:12:51 mbox org.gnome.Lollypop.SearchProvider[179481]:   con.register_object(object_path=path,
Nov 28 15:12:52 mbox org.gnome.Characters[179477]: Vulkan: ../mesa-25.2.7/src/amd/vulkan/radv_physical_device.c:2182: Device '/dev/dri/renderD128' is not using the AMDGPU kernel driver: Invalid argument (VK_ERROR_INCOMPATIBLE_DRIVER)
Nov 28 15:12:52 mbox org.gnome.Characters[179477]: Vulkan: Loader Message: setup_loader_term_phys_devs:  Failed to detect any valid GPUs in the current config
Nov 28 15:12:52 mbox org.gnome.Characters[179477]: vkEnumeratePhysicalDevices(): Initialization of an object could not be completed for implementation-specific reasons. (VK_ERROR_INITIALIZATION_FAILED) (-3)
Nov 28 15:12:52 mbox org.gnome.Nautilus[179471]: Localsearch search engine has no connection
Nov 28 15:13:04 mbox org.gnome.Screenshot[179854]: Unable to use GNOME Shell's builtin screenshot interface: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: ScreenshotWindow is not allowed
Nov 28 15:13:04 mbox org.gnome.Screenshot[179854]: Unable to capture a screenshot of any window
Nov 28 15:13:08 mbox org.gnome.Lollypop.SearchProvider[183958]: /usr/lib/lollypop/lollypop-sp:71: DeprecationWarning: Gio.DBusConnection.register_object is deprecated
Nov 28 15:13:08 mbox org.gnome.Lollypop.SearchProvider[183958]:   con.register_object(object_path=path,
Nov 28 15:13:08 mbox org.gnome.Nautilus[183948]: Localsearch search engine has no connection
Nov 28 15:13:08 mbox org.gnome.Characters[183954]: Vulkan: ../mesa-25.2.7/src/amd/vulkan/radv_physical_device.c:2182: Device '/dev/dri/renderD128' is not using the AMDGPU kernel driver: Invalid argument (VK_ERROR_INCOMPATIBLE_DRIVER)
Nov 28 15:13:08 mbox org.gnome.Characters[183954]: Vulkan: Loader Message: setup_loader_term_phys_devs:  Failed to detect any valid GPUs in the current config
Nov 28 15:13:08 mbox org.gnome.Characters[183954]: vkEnumeratePhysicalDevices(): Initialization of an object could not be completed for implementation-specific reasons. (VK_ERROR_INITIALIZATION_FAILED) (-3)
Nov 28 15:13:14 mbox org.gnome.Screenshot[184150]: Unable to use GNOME Shell's builtin screenshot interface: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Screenshot is not allowed
Nov 28 15:13:14 mbox org.gnome.Screenshot[184150]: Unable to capture a screenshot of any window
Nov 28 15:13:19 mbox org.gnome.Lollypop.SearchProvider[186659]: /usr/lib/lollypop/lollypop-sp:71: DeprecationWarning: Gio.DBusConnection.register_object is deprecated
Nov 28 15:13:19 mbox org.gnome.Lollypop.SearchProvider[186659]:   con.register_object(object_path=path,
Nov 28 15:13:19 mbox org.gnome.Characters[186655]: Vulkan: ../mesa-25.2.7/src/amd/vulkan/radv_physical_device.c:2182: Device '/dev/dri/renderD128' is not using the AMDGPU kernel driver: Invalid argument (VK_ERROR_INCOMPATIBLE_DRIVER)
Nov 28 15:13:19 mbox org.gnome.Characters[186655]: Vulkan: Loader Message: setup_loader_term_phys_devs:  Failed to detect any valid GPUs in the current config
Nov 28 15:13:19 mbox org.gnome.Characters[186655]: vkEnumeratePhysicalDevices(): Initialization of an object could not be completed for implementation-specific reasons. (VK_ERROR_INITIALIZATION_FAILED) (-3)
Nov 28 15:13:24 mbox org.gnome.Screenshot[186785]: Unable to use GNOME Shell's builtin screenshot interface: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: SelectArea is not allowed
Nov 28 15:13:27 mbox org.gnome.Screenshot[186785]: Unable to use GNOME Shell's builtin screenshot interface: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: SelectArea is not allowed
15

plasma-desktop 6.5.3-2 will be coming along shortly.

1 Like
16

I had an interesting issue when an update for plasma-desktop come through. I’m not sure if it’s part of the current update, but pamac flagged a “Some Files were not downloaded” error, though it appeared to successfully complete the update.

Just to be sure I reinstalled plasma-desktop using pacman

sudo pacman -Syu plasma-desktop

pacaman informed me it was reinstalling and completed the update.

I logged out then back in.

Everything appears normal.

17

Sounds like there might have been an issue with the first mirror. It most likely finished the update transaction using the next working mirror.

1 Like
18

I’ve been getting the following message whenever I use the xdg-open command to open a URL in my default browser (Firefox):

qt.qpa.services: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for 'org.kde.kioclient'")

The URL opens correctly, so it isn’t causing any issues (apart from the irritating message).

I also just tested opening an image file in my default image viewer (qimgv) using the xdg-open command. The picture opened correctly, but the same message also appeared:

xdg-open /home/scotty/Pictures/Wallpapers/SFW/Bing-wallpapers/OHR.AcroporaReef_ROW9713296408_1920x1080.jpg

qt.qpa.services: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for 'org.kde.kioclient'")

The only thing is, I’m not 100% sure if the issue started with this update, or the previous Testing update (2025-11-24). I thought it might have been something to do with plasma-desktop requiring a rebuild, however the plasma-desktop (6.5.3-1 → 6.5.3-2) update today has not fixed this non-critical issue.

As I said, it isn’t causing any problems at the moment.

Edit: I just tried opening a bunch of URLs with journalctl -f running, and it looks like it might be an issue with baloo:

Nov 30 14:44:46 scott-ser systemd[773]: Started Firefox - Web Browser.
Nov 30 14:44:46 scott-ser baloo_file_extractor[228937]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for 'org.kde.baloo'")
Nov 30 14:44:48 scott-ser systemd[773]: Started Firefox - Web Browser.
Nov 30 14:44:48 scott-ser baloo_file_extractor[229131]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for 'org.kde.baloo'")
Nov 30 14:44:49 scott-ser systemd[773]: Started Firefox - Web Browser.
Nov 30 14:44:49 scott-ser baloo_file_extractor[229191]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for 'org.kde.baloo'")
Nov 30 14:44:50 scott-ser systemd[773]: Started Firefox - Web Browser.
Nov 30 14:44:50 scott-ser baloo_file_extractor[229243]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for 'org.kde.baloo'")
Nov 30 14:44:52 scott-ser systemd[773]: Started Firefox - Web Browser.
Nov 30 14:44:52 scott-ser baloo_file_extractor[229328]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for 'org.kde.baloo'")
Nov 30 14:44:54 scott-ser systemd[773]: Started Firefox - Web Browser.
Nov 30 14:44:54 scott-ser baloo_file_extractor[229426]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for 'org.kde.baloo'")
Nov 30 14:44:56 scott-ser systemd[773]: Started Firefox - Web Browser.
Nov 30 14:44:56 scott-ser baloo_file_extractor[229487]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for 'org.kde.baloo'")
Nov 30 14:44:57 scott-ser systemd[773]: Started Firefox - Web Browser.
Nov 30 14:44:57 scott-ser baloo_file_extractor[229587]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for 'org.kde.baloo'")
Nov 30 14:44:59 scott-ser systemd[773]: Started Firefox - Web Browser.
Nov 30 14:44:59 scott-ser baloo_file_extractor[229746]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for 'org.kde.baloo'")
Nov 30 14:45:02 scott-ser systemd[773]: Started Firefox - Web Browser.
Nov 30 14:45:02 scott-ser baloo_file_extractor[229835]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for 'org.kde.baloo'")

I might purge the baloo database and see if that does anything.

Edit 2: I think the App info not found for 'org.kde.baloo' messages may have been unrelated to the xdg-open messages. Purging the baloo database stopped the above App info not found for 'org.kde.baloo' messages appearing in the journal, however the original App info not found for 'org.kde.kioclient' messages are still appearing in the terminal window from which I am launching the xdg-open command. Strangely, those App info not found for 'org.kde.kioclient' errors do not appear in the journal.

1 Like
19

I don’t use baloo, and I can confirm the issues exists.

[tracy@daphne Pictures]$ xdg-open /home/tracy/Pictures/710jHHSTs5L._AC_SL1500_-1307418147.jpg 
qt.qpa.services: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for 'org.kde.kioclient'")
1 Like
21