Language Selection

English French German Italian Portuguese Spanish

Review: Manjaro Linux 19.0

Filed under

Manjaro Linux is one of those distributions I have tried many times over the years but was always unable to keep for any length of time due to this or that issue cropping up. Either package management was limited, it wouldn't boot up after the install, or even straight away. Whatever the issues I don't exactly recall, because the last time I tested it must have been around 2014 or even 2013, which would have made this Manjaro 0.8.x. Has it really been around this long already? My, I'm getting quite long in the tooth. Manjaro 19.0 looks really interesting and it's brand new. I'm sure lots has changed so, in somebody else's words, test we must.

Many of the people behind Manjaro are the same that are, or at least were, behind the Chakra distribution, a KDE-centric distribution I really liked and found interesting back in the day but which appears quite dormant. Developers moved on. I recall getting an e-mail once about this new project they were going to start called Manjaro and asking if I wanted to do an early review but unfortunately time didn't permit back then. And when I did it appeared not mature yet so it seemed better not to write anything. But an incremental number 19 seems plenty mature. Enough of the babble, let's go.

The release announcement for 19.0 informs us that it comes in three desktop variants with GNOME 3.34, Xfce 14.4 or with KDE Plasma 5.17. Cutting edge stuff. Also with something called Architect which as it turns out is included in all editions as a shortcut on the desktop, similar to the install button, and allows us to customize installations. Architect can also be downloaded on its own and is basically a net-install image to install the latest available packages and set up and configure Manjaro in every detail using the command line, custom setup tool included. We'll be looking at this in more detail later.

I opted to download the KDE edition via a torrent which is clocked at 2,892MB (about 2.8GB) but which took up 3.0GB on my hard drive. I guess it depends on what cluster size one has used for formatting.

The release announcement includes a 43 minute long video walking us through all the editions which is a really nice introduction to features and looks and can help decide which edition is for you.

This release is underpinned by the latest LTS Linux kernel 5.4 to have the most up to date drivers available. Looks-wise Manjaro has updated Xfce with their own new theme called Matcha, the Plasma desktop has received a fully integrated look with a comprehensive and all-encompassing set of themes called Breath2 in light and dark variants. And yes, it looks slick if that is your style but personally I'm not one for the abstract wallpapers and flat looks in fashion nowadays. Not a biggie, can be changed.

It is quite evident though, even at this stage, from looking at the website that Manjaro has a lot of resources behind it and a lot of people must be committing time to this, so it's certainly not a project in danger of withering away over night in case people are concerned about long-term viability and support for their installs. Plus, Manjaro is of course based on Arch Linux which has been around since the early 2000s. Packages from the official Arch Linux repositories and user contributed packages and build scripts should be working fine. Like Arch Linux, Manjaro is also a rolling release distribution that should not require a reinstall if everything goes well. The team behind Manjaro go to some lengths to make sure it does, by tweaking and moderating changes from upstream and channeling packages through their own repositories.

Read more

Manjaro 19.0 Kyria KDE Edition

  • Manjaro 19.0 Kyria KDE Edition – Features KDE Plasma 5.17 and Powered by Linux Kernel 5.4

    Manjaro 19 KDE Edition ships with the latest version KDE plasma 5.17. The themes have been updated including new “light” and “dark” versions within the Breath2 theme. In addition, KDE 19.12.2 packages and applications have been included.

    Manjaro 19 offering Office Suite Freeoffice 2018 by SoftMaker during installation. Bauh, the graphical package manager now supports Snaps, Flatpaks, Appimage and the Arch AUR. This means that Manjaro users now have three choices of application installation in the GUI.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Essential Guide: How to Upgrade to Ubuntu 20.04 (Beta) Right Now

Well, in this guide I show you the steps required to upgrade to Ubuntu 20.04 from Ubuntu 18.04 or Ubuntu 19.10 right now, , nice and early, ahead of the final release. You do not need to download an .iso, fuss around with a USB thumb drive, or lose any of your files — you can upgrade directly with a half-way decent internet connection. Just keep in mind that (at the time you read this) the final stable release of the Focal Fossa is not yet available, only a beta quality candidate is. Read more

Plasma Mobile: How to help us!

We often get asked: “how long until the 1.0 release?”. Or: “how far away is Plasma Mobile 1.0?”. The usual answer to both these question is “It’ll be ready when it is ready”. But, really, how do we know that it is ready? Recently some of us prepared a check list of items which we consider necessary before we can declare Plasma Mobile “ready” or at rc1 status. Read more

Android Leftovers

today's leftovers

  • Mesa 20.0.3 Released With Latest Open-Source Graphics Driver Fixes

    While many of you are users of Mesa Git for experiencing the bleeding-edge graphics drivers especially if you are a gamer wanting peak performance, for those on the Mesa stable series the Mesa 20.0.3 update has now shipped. Mesa 20.0.3 is the latest bi-weekly point release for back-porting the fixes to this Q1'2020 stable series.

  • Adrien Plazas: A Coloring API for GTK

    This week we had the Design Tools Hackfest 2020, virtualized because of COVID-19, where we discussed that recoloring API. We came up with something I think is interesting enough to discuss more widely.

  • [Former Canonical manager] Dustin Kirkland: Coordinated Launch Cycles at Apex

    I joined Apex Clearing last year, having spent the previous 20 years as a software engineer, product manager, and executive, mostly around open source software, including Ubuntu, OpenStack, and Kubernetes. Albeit IBM, Canonical and Google differ from fintech on many levels, these operating systems and cloud infrastructure technology platforms share a number of similarities with Apex's software-as-a-service platform. Moreover, there also exists some literal overlap: we’re heavy users of both Ubuntu and Kubernetes here at Apex. Ubuntu, OpenStack, and Kubernetes all share similar, predictable, time-based release cycles. Ubuntu has released every April and October, since October of 2004 – that's 32 major software platform releases, on time, every time, over 16 years. Ubuntu has set the bar for velocity, quality, and predictability in the open source world. OpenStack’s development processes have largely mirrored Ubuntu’s, with many of the early project leaders having been ex-Ubuntu engineers and managers. OpenStack, too, has utilized a 6-month development cycle, since 2010, now on its 20th release. Kubernetes came along in 2014, and sought to increase the pace a bit, with quarterly release cycles. Kubernetes is a little bit looser with dates than Ubuntu or OpenStack, but has generally cranked out 4 quality releases per year, over the last 6 years. I’ve been involved in each of these projects at some level, and I’ve thoroughly enjoyed coaching a number of early stage start-ups on how to apply these principles to their product development methodologies.

  • Ulrike Uhlig: Breaking the chain reaction of reactions to reactions

    Each of these interactions is embedded in larger society, and, as said above, we learn these roles from childhood. Therefore, we perpetually reproduce power structures, and learnt behavior. I doubt that fixing this on an individual level is sufficient to transform our interactions outside of small groups, families or work places. Although that would be a good start. We can see that the triangle holds together because the Victim, seemingly devoid of a way to handle their own needs, transfers care of their needs to the Rescuer, thereby giving up on their autonomy. The Rescuer is provided by the Victim with a sense of autonomy, knowledge, and power, that only works while denying the Victim their autonomy. At the same time, the Persecutor denies everyone else's needs and autonomy, and feels powerful by dismissing others. I've recently mentioned the importance of autonomy in order to avoid burnout, and as a means to control one's own life. If the Rescuer can acknowledge being in the triangle, and give the Victim autonomy, by supporting them with compassion, empathy, and guidance, and at the same time respecting their own boundaries, we could find even more ways to escape the drama triangle.