[ARM Unstable Update] 2025-08-01 - Linux, Plasma, Thunderbird, Firefox, Chromium

ARM ARM Unstable Updates
1

Hi,

Manjaro ARM Unstable Update Topic For August.

Thanks to the Manjaro ARM devs for their hard work.
The Manjaro x86_64 devs are involved too, thanks to them.

Currently the only maintained branch for ARM is unstable branch.

It’s time for you to update your ARM device(s) running Manjaro ARM, whatever your ARM device(s) or desktop environment.

Glad to see old ARM users coming back, as well as newcomers. (the more the merrier)

Manjaro uses a Rolling Release Development Model

Find the packages version with the Branch Compare Page

https://manjaristas.org/branch_compare?q=plasma&arm=on

There are 3 methods for installing Manjaro ARM on your devices.

1) Download the official Manjaro ARM images on the Manjaro website

https://manjaro.org/products/download/arm

Give preference to methods 2 and 3 as they are kept up to date.

2) Manjaro Linux Images For ARM Devices

https://github.com/manjaro-arm

3) Build your own Manjaro ARM images, read this wiki post

https://forum.manjaro.org/t/wiki-how-to-contribute-to-manjaro-arm/35461

To add or remove some packages modify this file (choose your desktop environment here)
/usr/share/manjaro-arm-tools/profiles/arm-profiles/editions/

Find the build image here
/var/cache/manjaro-arm-tools/img/

For Your RPI Kernel Devices See The Link Below

Manjaro ARM Linux Kernel For RPI Devices

For Your Odroid ARM Kernel Devices See The Link Below

Manjaro ARM Linux Kernel For Odroid Devices

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

Check and manage pacnew files

Info about AUR packages

Link

Arch User Repository - Manjaro

You’re welcome to post, feedback from users is a part of software development

Enjoy !

3 Likes
2

Plasma 6.4 is moving to Wayland only, to get the X11 option back, see the link below

A KDE Discuss Member Appreciated The @linux-aarhus Solution

activating x11 on plasma 6.4.3 - #4 by nl.smart - Help - KDE Discuss

2 Likes
3

Updated 2025-08-02:

Today’s arch-arm sync: 86 packages

4 Likes
4

Could you rebuild manjaro-settings-manager and update obs-studio to 31.1.1.

5

“chromium” is in the title of this thread which made me think that maybe arch updated chromium at last, but it is still the december 2024 version.

6

talk to @nl.smart about that. He will know why.

7

By the way, i have the following line in my pacman.conf. I don’t remember putting it there. Is it normal?

HoldPkg = pacman glibc manjaro-system

8

Sorry, I don’t use chromium, but the Manjaro ARM users are talking often about Chromium :slight_smile:

More details about Chromium here

[ARM] Chromium does not run after latest unstable update

9

We discussed changes to the presentation, and my suggestion was to just leave the date in the title. And possibly to include in the post some comment only when there is a major change in the version of Plasma, Gnome, or Xfce or something else important.

@Sam_Fisher yes normal

10

Pushed to unstable when the mirrors sync.

manjaro-settings-manager-0.5.7-12
obs-studio-31.1.1-2

Added 2025-08-05:

Today’s arch-arm sync: 63 packages

2 Likes
11

rpi-ffpmeg needs a rebuild too

qmapshack
qmapshack: symbol lookup error: /usr/bin/../lib/libQt6WebEngineCore.so.6: undefined symbol: av_stream_get_first_dts, version LIBAVFORMAT_61
12

GT King Pro - Gnome update successfully.

# System Details Report
---

## Report details
- **Date generated:**                              2025-08-07 13:35:54

## Hardware Information:
- **Hardware Model:**                              (null)
- **Memory:**                                      3.7 GiB
- **Processor:**                                   
- **Graphics:**                                    Mali-G52 (Panfrost)
- **Disk Capacity:**                               61.9 GB

## Software Information:
- **Firmware Version:**                            (null)
- **OS Name:**                                     Manjaro ARM Linux
- **OS Build:**                                    rolling
- **OS Type:**                                     64-bit
- **GNOME Version:**                               48
- **Windowing System:**                            Wayland
- **Kernel Version:**                              Linux 6.16.0-1-MANJARO-ARM

With linux-6.16.0-1 on GT King Pro witi still takes around 90-120 seconds to be available after system boot up to desktop. This have been the case on GT King Pro since linux-6.14-rc.

On Opi5-Plus with Manjaro linux kernel wifi is basically available on boot up.

1 Like
13

is anyone else having trouble with audio outputs recently? aplay -l lists the hdmi-output but it doesn’t show up in pavucontrol and it won’t play sound using speaker-test (or any other program). this happened to me a couple weeks ago for the first time. it fixed itself for no apparent reason back then and came back the other day. just wondering if this is one of the hiccups of recent updates or if it’s worth starting its own thread for. i’m on rock pi 4b+, testing-branch

1 Like
14

Opi5-Plus KDE upgraded successfully to KDE Plasma-6.4.4 KDE Framework-6.17.0.

1 Like
15

just did some superficial testing on another rock-pi. did get normal audio from hdmi while on current stable-branch. but hdmi-out did not show up in pavucontrol either, at least not as hdmi but as analog output. weird but ok.

i then switched to testing-branch. after an update i still get sound but also a couple of issues i ran into before on my main-install:

  • hdmi-audio (if present) is very loud and distorted unless turned down to 30/40 in alsamixer. any lower than that will reveal an unbearable noise-floor. none of this is true for analog output.
  • analog and hdmi cards have switched positions (hdmi used to be card 1 and is now card 0, vice-versa for analog)

it appears these are related to the updates. another issue i had on this fresh testing-install was a trackpad not working anymore after the update. i’m still not entirely sure wether the dead hdmi-output on my main-install is caused by software or if it’s a hardware-fault…

16

Just a heads up. The new mesa-25.2.1-1 have issue/conflict with Chromium_v139 – randomly have visual artifacts on Opi5-Plus.

17

Something similar happened a few months ago (mesa+chromium). Another regression?

18

Looks like it. Other rk3588 users also highlighted the chromium and mesa-25.2.1-1 visual artifact issue. Not sure whether it affects other SOCs.

Edit: 2025-08-25 New Panthor Mali-CSF-Firmware seems to improve glmark2-es2-wayland score.

https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/arm/mali/arch10.8/mali_csffw.bin

But unfortunately does not resolve the bad visual artifacts and freezes with mesa-25.2.1-1 or mesa-25.2.1-2 and Chromium_v139 (on --ozone-platform=wayland). No visual artifact issue mesa-25.2.1-1/2 with Chromium_v139 on --ozone-platform=x11.

19

Hi,

TY for your work on Manjaro ARM!

May it be possible to sync the unstable branch with last available updates?

Wish You well

1 Like
20

@philm @Darksky @spikerguy @Manjaro-Arm

Should I create a post dedicated to Manjaro ARM Unstable for September 2025 ?

The Manjaro team will take care of it. Right ?

1 Like