Why haven’t I received the Plasma update after switching from the stable branch to the testing branch?

Support KDE Plasma
1

Why haven’t I received the Plasma update after switching from the stable branch to the testing branch?

I switched to the test branch following these instructions in order to get the Plasma 6.6.3 update, but it tells me that there is no update available.

sudo pacman-mirrors --api --set-branch testing
sudo pacman-mirrors --fasttrack 5 && sudo pacman -Syu

After update and reboot I have:
Operating System: Manjaro Linux
KDE Plasma Version: 6.5.6
KDE Frameworks Version: 6.24.0
Qt Version: 6.10.2
Kernel Version: 6.18.20-1-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 5600H with Radeon Graphics
Memory: 16 GiB of RAM (15.0 GiB usable)
Graphics Processor: AMD Radeon Graphics
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: VivoBook_ASUSLaptop M1603QA_M1603QA
System Version: 1.0

2

Hi @pp2222,

Probably because that version is only in the Unstable branch:

$ mbn info plasma-desktop -q
Branch         : archlinux
Name           : plasma-desktop
Version        : 6.6.2-1
Repository     : extra
Build Date     : Tue 03 Mar 2026 23:26:01
Packager       : Antonio Rojas <arojas@archlinux.org>
Branch         : unstable
Name           : plasma-desktop
Version        : 6.6.2-1
Repository     : extra
Build Date     : Tue 03 Mar 2026 23:26:01
Packager       : Antonio Rojas <arojas@archlinux.org>
Branch         : testing
Name           : plasma-desktop
Version        : 6.5.6-1
Repository     : extra
Build Date     : Thu 12 Mar 2026 05:44:23
Packager       : Philip Mueller <philm@manjaro.org>
Branch         : stable
Name           : plasma-desktop
Version        : 6.5.5-1
Repository     : extra
Build Date     : Tue 13 Jan 2026 22:11:15
Packager       : Tomaz Canabrava <tcanabrava@archlinux.org>

Find a branch comparison tool here:

3

Strange…
Here is from the same page

image
image921×140 10.3 KB

And I had 6.5.6-1.1 on stable not 6.5.5-1 as on your table

4

Someone forgot to update their mbn database…

mbn info plasma-desktop -q | grep -Ev 'Name|Repository|Packager'
Branch         : archlinux
Version        : 6.6.3-2
Build Date     : Sat 28 Mar 2026 23:48:58 
Branch         : unstable
Version        : 6.6.3-2
Build Date     : Sat 28 Mar 2026 23:48:58 
Branch         : testing
Version        : 6.6.3-2
Build Date     : Sat 28 Mar 2026 23:48:58 
Branch         : stable
Version        : 6.5.6-1.1
Build Date     : Tue 31 Mar 2026 14:19:08

@pp2222 Try force refreshing the pacman databases when you do the update:

sudo pacman -Syyu

You can also double-check which branch you are on with the following command:

pacman-mirrors --get-branch
4 Likes
5

Thank you!

pacman-mirrors --get-branch

this helped :backhand_index_pointing_up:

Operating System: Manjaro Linux
KDE Plasma Version: 6.6.3
KDE Frameworks Version: 6.24.0
Qt Version: 6.11.0
Kernel Version: 6.18.20-1-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 5600H with Radeon Graphics
Memory: 16 GiB of RAM (15.0 GiB usable)
Graphics Processor: AMD Radeon Graphics
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: VivoBook_ASUSLaptop M1603QA_M1603QA
System Version: 1.0

2 Likes
6

I noticed the same after switching to unstable, though rebooting fetched updates.

7

It is important do force the download of metadata after switching branch.

The reason is the timestamp of the metadata.

If the timestamp of your current metadata in /var/lib/pacman/sync is equal to or newer than the timestamp of the server - the metadata will not be fetched - that is how the pacman API provided by libalpm work.

So after a change in mirror list - whether that is caused by change of branch or done automagically using the pamac-mirrorlist.timer - it is recommended to use -Syyu to force the refresh of metadata.

If using pamac - the equivalent is --force-refresh

3 Likes
8

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.