(Testing Update) 2026-02-18 – Kernels, KDE Frameworks, GNOME, GStreamer – Testing Updates

Hello community, here we have another set of package updates. This might mark the last 26.0.3 update for Anh-Linh release series. Let us know if you see some issues with those package updates.

Current Promotions

Recent News

sudo pacman -Syu gnome-shell-extension-papirus-folders-colorizer

 gnome-extensions enable papirus-folders-colorizer@NiffirgkcaJ.github.com

gnome-session-quit --logout

sudo pacman -Syu plasma-login-manager
systemctl disable sddm
systemctl enable plasmalogin
sudo pacman -R sddm-kcm sddm

• Manjaro 26.0 Anh-Linh released
• Manjaro Summit public Alpha now available
• As of Linux 5.4.302, the 5.4 series is now EOL (End Of Life). Please install 5.10 LTS (Long Term Support) or 5.15 LTS.
• As of Linux 6.16.12, the 6.16 series is now EOL (End Of Life). Please install 6.18 LTS (Long Term Support) and/or 6.12 LTS.
• As of Linux 6.17.13, the 6.17 series is now EOL (End Of Life). Please install 6.18 LTS (Long Term Support) and/or 6.12 LTS.

Notable Package Updates

Additional Info

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

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

 checkrebuild

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

• linux510 5.10.250
• linux515 5.15.200
• linux61 6.1.163
• linux66 6.6.126
• linux612 6.12.73
• linux618 6.18.12
• linux619 6.19.2
• linux61-rt 6.1.158_rt58
• linux66-rt 6.6.116_rt66
• linux612-rt 6.12.66_rt15
• linux617-rt 6.17.5_rt7

Package Changes (2/18/26 02:11)

• testing core x86_64: 31 new and 30 removed package(s)
• testing extra x86_64: 971 new and 978 removed package(s)
• testing multilib x86_64: 10 new and 10 removed package(s)

More details about the package changes can be found here

Check if your mirror has already synced:

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:

2026-02-18

2025-12-29

2025-12-09

2025-11-10

Previous testing threads:

Bluetooth did not work immediately, but reconnecting the headset helped.
The mouse design was changed to Adwaita. Changed back to Breeze Dark.

More info for the bluez issue:

journalctl -b -p err | grep bluetoothd
Feb 18 22:27:14 blackbox bluetoothd(1522): Failed to set default system config for hci0

Reconnect worked only on 6.18.12 but not on 6.19.2

Downgraded to 5.85
Also the latest 8.86-4 does not fix this issue.

Fixed with breeze-cursors5 5.27.12-2.

I understand, that a post with “everything works” is not needed.

I thought, probably in this case, as it is NVIDIA, newest driver, newest kernel related, it could anyhow make sense for the maintainers of the branches to know that

• NVIDIA RTX 2070 with Kernel 6.19.2 and the 590.48.01 driver works quite well after halve a day of working.

This was not the case on my machine in the past with 590.xx and 6.19 or 6.18 so far.

If this info is anyhow useless – please forgive me, and just forget it …

There are some new issues with bluetoothctl. Here’s some output (note, as I type, my phone is playing a podcast via bluetooth – it IS connected).
bluetoothctl devices fails silently… as does bluetoothctl info.

I should look into filing a bug there…

I discovered this because I use a script to check and connect or disconnect my A15 phone audio… but that started to fail; perhaps there were some changes with the libraries.

Anyway, my script failed detecting stuff with:

is_device_connected()  grep -q "Connected: yes"

I ended up fudging that, replaced it with some pactl shenanigans:

is_device_connected() {
    local mac_underscore="$
    amixer get Master "
    # Sink check
    if pactl list short sinks 2>/dev/null | grep -qi "$mac_underscore"; then
        return 0
    fi
    # Source check
    if pactl list short sources 2>/dev/null | grep -qi "$mac_underscore"; then
        return 0
    fi
    # Card connection property check
    if pactl list cards 2>/dev/null | awk -v mac="$mac_underscore" '
        /Card/ 
    amixer get Master 
        /bluez_card\.'$mac_underscore'/  head -n1 
        in_card && /api.bluez5.connection = "connected"/  head -n1 
        END {exit !found}
    '; then
        return 0
    fi
    # Bluetoothctl fallback
    if LANG=C bluetoothctl devices Connected | grep -qi "$DEVICE_MAC"; then
        return 0
    fi
    if LANG=C bluetoothctl info "$DEVICE_MAC" | grep -q "Connected: yes"; then
        return 0
    fi
    return 1

So now the script works exactly as expected.

So for anyone interested in a one-touch shortcut to toggle phone audio here’s the new script:

#!/bin/bash
# For toggling A15 Bluetooth connection with KDE Plasma notifications

DEVICE_MAC="08:A5:DF:D7:41:36"
DEVICE_NAME="Samsung A15"
CONNECT_SOUND="/home/ben/Audio/Alerts-home/en-message-sent-instant.ogg"
DISCONNECT_SOUND="/home/ben/Audio/Alerts-home/Disconnect-Bottle.aiff"
FAIL_SOUND="/home/ben/Audio/Alerts-home/System Sounds (Dropbox Resources)/MacOS/aiff/Basso.aiff"
INIT_SOUND="/home/ben/Audio/Alerts-home/notify-Tink.aiff"

get_current_volume() {
    amixer get Master | grep -oP '\(\d+%\)' | head -n1 | tr -d '()%'
}

is_device_connected() {
    local mac_underscore="${DEVICE_MAC//:/_}"
    # Sink check
    if pactl list short sinks 2>/dev/null | grep -qi "$mac_underscore"; then
        return 0
    fi
    # Source check
    if pactl list short sources 2>/dev/null | grep -qi "$mac_underscore"; then
        return 0
    fi
    # Card connection property check
    if pactl list cards 2>/dev/null | awk -v mac="$mac_underscore" '
        /Card/ {in_card=0}
        /bluez_card\.'$mac_underscore'/ {in_card=1}
        in_card && /api.bluez5.connection = "connected"/ {found=1; exit}
        END {exit !found}
    '; then
        return 0
    fi
    # Bluetoothctl fallback
    if LANG=C bluetoothctl devices Connected | grep -qi "$DEVICE_MAC"; then
        return 0
    fi
    if LANG=C bluetoothctl info "$DEVICE_MAC" | grep -q "Connected: yes"; then
        return 0
    fi
    return 1
}

play_sound() {
    local sound="$1"
    if ( -n "$sound" ) && ( -f "$sound" ); then
        paplay "$sound" &
    fi
}

notify() {
    local title="$1"
    local message="$2"
    local sound="$3"
    local icon="${4:-bluetooth}"
    notify-send -u normal -i "$icon" "$title" "$message"
    if ( -n "$sound" ) && ( -f "$sound" ); then
        play_sound "$sound"
    fi
}

play_sound "$INIT_SOUND"

if is_device_connected; then
    echo "Device $DEVICE_NAME ($DEVICE_MAC) is connected. Disconnecting..."
    disconnect_output=$(bluetoothctl disconnect "$DEVICE_MAC" 2>&1)
    sleep 2

    if ! is_device_connected; then
        echo "Successfully disconnected."
        notify "Bluetooth Disconnected" "$DEVICE_NAME was disconnected" "$DISCONNECT_SOUND"
    else
        echo "Bluetooth disconnect failed, trying PulseAudio card profile off..."
        pactl set-card-profile "bluez_card.${DEVICE_MAC//:/_}" off
        sleep 2
        if ! is_device_connected; then
            echo "Successfully disconnected via PulseAudio."
            notify "Bluetooth Disconnected" "$DEVICE_NAME was disconnected" "$DISCONNECT_SOUND"
        else
            echo "Failed to disconnect: $disconnect_output" >&2
            notify "Bluetooth Error" "Failed to disconnect $DEVICE_NAME" "$FAIL_SOUND" "error"
            exit 1
        fi
    fi
else
    echo "Device $DEVICE_NAME ($DEVICE_MAC) is not connected. Attempting to connect..."
    notify "Bluetooth" "$DEVICE_NAME is not connected... Attempting to connect!" "" "bluetooth"

    bluetoothctl power on >/dev/null 2>&1
    connect_output=$(bluetoothctl connect "$DEVICE_MAC" 2>&1)

    # Poll for up to 10 seconds
    connected=false
    for i in {1..10}; do
        sleep 1
        if is_device_connected; then
            connected=true
            break
        fi
    done

    if $connected; then
        current_volume=$(get_current_volume)
        amixer set Master 45% >/dev/null 2>&1
        notify "Volume Adjusted" "from $current_volume% to 45%." "" "audio-volume-high"
        echo "Successfully connected."
        notify "Bluetooth Connected" "$DEVICE_NAME was connected" "$CONNECT_SOUND"
    else
        echo "Failed to connect: $connect_output" >&2
        notify "Bluetooth Error" "Failed to connect to $DEVICE_NAME" "$FAIL_SOUND" "error"
        exit 1
    fi
fi

exit 0

Update:

I completely understand the euphoria.

When you’ve been lumbered with nVidia hardware (often at great cost to yourself), a successful boot with working acceleration is basically a religious experience.

It’s like finding a unicorn in your backyard.

Sure, the rules say “issues only,” but witnessing a unicorn compels you to shout from the rooftops.

We’ll allow it, just this once.

Enjoy your extra days of graphical computing before the next weekly update.

@Yochanan The cursor on xfce loginscreen is still Adwaita

cat /etc/lightdm/lightdm-gtk-greeter.conf | grep cursor-theme-name
cursor-theme-name = xcursor-breeze

Fixed by:

sudo sd xcursor-breeze breeze-cursors /etc/lightdm/lightdm-gtk-greeter.conf

I think there is still a mismatch with breeze-cursors5 and the non existing breeze-cursors from unstable. Also the settings packages might not reflect that.

I updated the ISO profile where that the cursor theme setting originates, but users will have to modify the file themselves as you did.

The related changes are sorted now. breeze-cursors5 is breeze-cursors and breeze-cursors-snow while breeze-cursors is breeze_cursors and Breeze_Light.

If a cursor theme is not found, the default fallback on Gtk systems is Adwaita.

And for sway users, in manjaro-sway-settings v16.39.8-11 (manjaro-sway-settings@5db270f62f).

Note that there are still likely some remnants of the old theme xcursor-breeze mentioned in other Manjaro desktop configs. I tried to patch those as well in this PR #229, but it looks like the sway repo is actually a fork of the original that lives in a GitLab repo somewhere. The maintainer (rightly) refused to merge those commits, because it’s currently using a rebase workflow which would get complicated if upstream files changed.

I figure that I should mention this here to raise awareness of potential issues, because the other Manjaro editions (bspwm, mate, budgie, webdad/jade) do have known places where xcursor-breeze is hardcoded in default configs.

Also, there is default-cursors from upstream Arch which still hardcodes it:

$ pacman -Ql default-cursors
default-cursors /usr/
default-cursors /usr/share/
default-cursors /usr/share/icons/
default-cursors /usr/share/icons/default/
default-cursors /usr/share/icons/default/index.theme

/usr/share/icons/default/index.theme:

(Icon Theme)
Inherits=xcursor-breeze

More details in my PRs:

Those have not existed for quite some time now.

replace sd with sed and syntax.

sudo sd xcursor-breeze breeze-cursors /usr/share/icons/default/index.theme

all my solutions should be posted on the stable branch “Known issues and solutions” later

Current ISOs including this update: Release 202602220737 · manjaro/release-review · GitHub

4 posts were merged into an existing topic: (Unstable Update) February 2026

I’ve taken care of that with breeze-cursors5 5.27.12-3.

Soundconverter fails to launch with an error.

❯ soundconverter
Traceback (most recent call last):
  File "/usr/bin/soundconverter", line 283, in 
    options, files = parser.parse_args(args(1:))
                                       ~~~~^^^^
TypeError: 'NoneType' object is not subscriptable

Fixed this by editing the file /usr/bin/soundconverter

Found the errant line 283
Edited to read:

options, files = parser.parse_args(args(1:) if args else ())

Soundconverter now launches without issue (until the next update…).

fixed in soundcoverter 4.1.2, soundcoverter 4.1.3 in now in unstable branch

So on Testing branch, if we don’t wish to edit, we can do:

sudo manjaro-downgrade soundconverter

From there, select 4.1.2 (and NOT ignore)… This also works Thanks.