Manjaro 21.1.3 Pahvo released!


Since we released Ornara earlier this year all our developer teams worked hard to get the next release of Manjaro out there. We call it Pahvo.

This release features major improvements to Calamares, including filesystem selection for automatic partitioning and enhanced support for btrfs. For btrfs installations, the default subvolume layout has been improved for easier rollbacks and less wasted space on snapshots. Additionally, swapfiles on btrfs filesystem are now supported.

The Gnome edition has received a major rework the update to Gnome 40. The default layout has been redesigned to follow more closely upstream defaults, with some adjustments to reduce the pointer travel for users who prefer using mouse with gnome.

For users that preferred the old vertical desktop layout, we have the Manjaro legacy layout, which mimics the previous gnome defaults. We made sure that all the layouts shipped with gnome-layout-switcher still work after the transition to Gnome 40.

Firefox now comes with the gnome-desktop style theme enabled by default for more consistent look with the desktop, but this can be toggled with one click from gnome-layout-switcher for users preferring the native Firefox look.

The Plasma edition comes with the latest Plasma 5.22 series, Frameworks 5.85 and Applications (Gear) 21.08. We also updated our default theme to match more upstream Breeze theming. This includes also a new wallpaper.

Plasma has become more pleasurable to use through improvements to the design and greater smoothness and consistency in transparencies, blurs, icons, and animations. Moving things to accessible locations, offering hints and visual cues, and creating new settings allows you to customize your work environment to make it fit perfectly to your needs. Following the true KDE spirit, the push for a more stable and attractive desktop does not mean you have to renounce control over how you want it to look or behave. Plasma 5.22, as always, packs all the flexibility and tools for customization you have come to expect and love, and some more to boot.

Meanwhile, the push to move Plasma in its entirety to Wayland (the display protocol of the future) continues in full swing. By using Wayland behind the scenes, Plasma is able to include features and bug fixes not possible to implement on X11, offering you a better experience and more stability. We also revisited a set of applications installed by default. Removed Konversation and replaced Cantata with Elisa. Additionally we provide Plasma browser integration support for desktop out of the box so now you need only one browser plugin.

With our XFCE edition, we have now Xfce 4.16. The window manager received lots of updates and improvements again in the area of compositing and GLX. Support for fractional scaling was added to the display dialog, along with highlighting the preferred mode of a display with an asterisk and adding aspect ratios next to resolutions. The settings manager has improved search and filter capabilities. Thunar file manager received a boatload of fixes and quite a few notable features, including pause for copy/move operations, support for queued file transfer, remembering view settings per directory and support for transparency in Gtk themes.

Kernel 5.13 is used for this release, such as the latest drivers available to date. With 5.4 LTS-Kernel minimal-ISOs we offer additional support for older hardware. We also updated Pamac to 10.2 series, which brings support for libpamac 11.1, a new gtk UI, now by default the GUI is optimized for the desktop and we introduce a version, optimized for mobile (launched with pamac-manager --mobile).

We hope you enjoy this release and let us know what you think of Pahvo.


Download XFCE



Minimal (linux54)

Download GNOME



Minimal (linux54)

Download KDE



Minimal (linux54)




Unstoppable release conveyor :slight_smile:

A post was merged into an existing topic: [Stable Update] 2021-09-16 - Kernels, Steam, Pipewire, Firefox, Thunderbird, Pamac, Pacman

A post was merged into an existing topic: [Stable Update] 2021-09-16 - Kernels, Steam, Pipewire, Firefox, Thunderbird, Pamac, Pacman

A post was merged into an existing topic: [Stable Update] 2021-09-16 - Kernels, Steam, Pipewire, Firefox, Thunderbird, Pamac, Pacman

A post was merged into an existing topic: [Stable Update] 2021-09-16 - Kernels, Steam, Pipewire, Firefox, Thunderbird, Pamac, Pacman

2 posts were split to a new topic: How do I update to 21.1.3?

The page still points to 21.1.2.

Please ship with kernel 5.14 from next release.

1 Like

You can simple install it: sudo mhwd-kernel -i linux514

It’s still too early to do so.
And as @pheiduck suggested, what’s the issue to install 5.14 post-install afterwards?

It is unable to use 5.14 on LiveCD if not to build that LiveCD by yourself (

You are talking about updating of installed OS copy, but @Computer_Email23 talking about kernel version included into ISO.
To execute new installed kernel it need to reboot, after reboot that ISO’s kernel version will be loaded - so 5.13 only. ISO should be changed to load another kernel.

Why not to make an ISO w/ included several kernel versions:
5.10 (default)
5.13 as current stable
5.14 as feature-rich (for example for btrfs installations)
This make users to be able to choose a kernel version during LiveCD boot up.

Why to have only the one kernel for all? Why to restrict ability to choose it? Why not to have several included?
You will use your 5.13, me and @Computer_Email23 will use 5.14 during installation.

One of the points is:

The Btrfs code base is stable. However, new features are still under development. Every effort is made to ensure that it remains stable and fast at each and every commit. This rapid pace of development means that the filesystem improves noticeably with every new Linux release so it’s highly recommended that users run the most modern kernel possible.

(btrfs Wiki)

1 Like

It’s not because an iso would be bloated with 4 (!) kernels that users would have the ability to choose it like that. It would require a development modification of LiveCD boot up or Calamares to achieve that.
Unless overloading every Manjaro user new install with four kernels…

Some new users are already lost with the choice of free or proprietary drivers at boot. Adding a list of kernels to pick is not really beginner friendly in my opinion.

Because it works for the majority without anything to do.

Those wanting to change kernels have some Linux knowledge. One can build a custom system with Architect or from the manual Arch way. Or simply adding new kernels with mhwd.

I still don’t see what would be the problem to perform a standard installation with Calamares and 5.13 kernel, not rebooting immadiately but chroot into the installed system. Then install (or uninstall) any kernels and additional packages you want.

After a reboot, you will have 5.13, 5.14 kernels, Brave, Vivaldi, Krita or Lutris already installed at your first fresh boot.

Not a very small answer, I prefer to hide it under that spoiler to keep the thread less complicated to skip our discussion for others

Kernel list menu is overloading a user? Really hard to choose kernel by hitting Enter on default/recommended version?
Now download section and users rescue flash drives is bloating of images count: 5.4, 5.10, 5.13 kernels for each ISO image (which will load, which will not?).

Yes, there other cons, including image size increase, development efforts.

There a default options which can be used for all including beginners.

Yes, Win OS is easier: no care of update procedure: it will update itself, no care of PC health status (software and hardware), to re-install OS if BSOD came on every Win boot. It is so easy to do not learn, do not understand, do not care of what is going on.

Again majority only, but not other second and third massive groups by it’s count.

Choose default item in grub boot menu is that hard?

OK, I load LiveCD with the newest possible 5.13 kernel.
What do I need to do to load LiveCD with 5.14 kernel? mhwd? Can’t realize the way, a hint will be so much useful.

The problem is that btrfs file system version structures are created before copying a file of new OS installation copy, so newest kernel need at the stage of creating file system structures, so while installation act, before copying OS files.

Generally I agree w/ you, that there some cons against that idea to have many kernels: to check and to support all of them and to test them before release (but single-kernel images also testing before release), and developers efforts to do that, but could be other more actual / priority tasks to do.

every new added kernel will add the

$ pacman -Qi linux514 | grep -i size
Installed Size  : 101.53 MiB

to the ISO image.
May be that is a big additional size, may be not.
If somebody uses 4GB drives to installation, than we come closer to the limit of their flash drives and now they may be don’t have any size to add: may be they already used 3 GB to image file and other for their additional files on additional partition.
64 GB microSD currently costs around 10 USD. May be it is too much for someone to upgrade from that 4 GB or 8 GB flash drives. Also USB 3.0 card reader for microSD cards costs around 5 USD.
So as always there are pros and cons.

May be it is a good idea: when Manjaro team will have developers time for some new feature and wants to know what users thinks, than to let community to get a voting process at least of week long and that will eliminate usage profile of future feature and / or percentage of second and third groups by it’s user count.
For example, if some voting results in 90% / 5% / 5% - probably it is need only 1 option to develop, but if 60% / 30 % / 10% - may be both with the option got 60% users by default.
Again, if it is usage profile related stuff, not developer internal stuff, which they know a way better.

But obviously to got service for us we need to fund the project also, helping developers to work for us also.
For my shame, I use Manjaro for 3.5 years and still did not contribute to the project any single cent currently. Need to fix it.

Can anyone confirm if a bug exists in Calamares (installer) for Manjaro 21.1.3?

This one is hard for me to test, because I came upon it for a friend’s new installation (from scratch.)

The possible bug (using the “Manual partitioning” option)

The installer immediately closes when it gets to the step where it begins to install your system, and more specifically, when it proceeds to format the root filesystem. :x:

However, if I format the filesystem ahead of time, the installer has no issues. :white_check_mark:

In other words, it doesn’t matter if I choose Ext4, XFS, or Btrfs during the installer’s setup, as long as I choose to “format” the root filesystem, it predictably crashes the installer once it gets to that part. I can confirm that no such formatting took place, as the partition still remains as “unformatted” when I check it under parted or KDE Partition Manager.

If I format to Ext4 or XFS ahead of time, and simply tell the installer to “use and mount to /” (but not to “format”), then it works fine and completes a successful installation.

1 Like

Calamares also broke off at this point for me yesterday. At the second attempt it has then worked. So YES, I can confirm it.

1 Like

@winnie, @anon71035019
Thank you for point this.
If you somehow collect and still have a log (e.g. journalctl or Camamares itself if it logs by default) and crash dumps from that LiveCD session than it would be very helpful to understand the exact reason.


What are the exact full names of the ISO used where Calamares crashed?

Did a hash check of the image and compare to shared one before to burn it into installation media?

I do not have a log, because I immediately tried again afterwards. The ISO was the 21.1.3 minimal KDE

1 Like

And now released yesterday and 21.1.4 today