Manjaro 24.0 released with KDE Plasma 6, GNOME 46, Linux kernel 6.9

I tried Manjaro in February but it broke after an update. I was unable to boot so I wiped the disk and install Kubuntu instead.

i think this is the problem a lot of manjaro users have.

remove QUIET from grub fixes it.
but i would not use manjaro today with AMD GPU, because they removed x264/5 hardware acceleration from mesa

KDE 6 is the same, all the manjaro kernel or mhwd settings are not in system settings anymore which is annoying.

Typical Manjaro amateurs with KDE a 2nd-class citizen there, see also Pamac GUI based on GTK4 for... KDE, it should be dropped from the list of recommended distros by KDE for the 2nd time. https://invent.kde.org/nmariusp/kde-org/-/commit/45c7cd58f85ba3e34f52b12755bb7d387b2c1d87


Last edited by sudoer on 15 May 2024 at 4:42 pm UTC

After breaking my desktop install yesterday I decided to Update my laptop install to plasma 6 using the TTY method as described in the tutorial section on Manjaro website.(Search for (HOW TO) Install Updates from TTY) for instructions. Its located in the tutorials section.

Update went without a hitch.

I have never, in over two decades of using Linux, had a problem with updating a distro from a desktop terminal.

Not a GNOME user then?

I've almost always used KDE. I used xfce for a bit at one point, and some other super minimalist desktop environment that I've forgotten the name of (it was so minimal that I had to do things like manually edit a text file to add items to its equivalent of the Start menu), but the majority of my Linux experience has been KDE.


Last edited by Mountain Man on 15 May 2024 at 8:04 pm UTC

I tried Manjaro in February but it broke after an update. I was unable to boot so I wiped the disk and install Kubuntu instead.

i think this is the problem a lot of manjaro users have.

remove QUIET from grub fixes it.
but i would not use manjaro today with AMD GPU, because they removed x264/5 hardware acceleration from mesa

In the last 3 out of 4 years of me using Manjaro this was literally my only real issue, although I used the testing branch.

After I had that issue and couldn't fix it I tried a few Distros until I settled with Fedora and I have to say I don't get how Fedora can be considered a stable Distro?!

The package manager takes ages to load, especially after the first install, I have constant crashes of some applications(more recently mostly when closing anyway but still) sometimes the Desktop just randomly restarts itself, some webpages cause Fedora to freeze my whole PC(and not just FireFox WTF) and the XWayland-videobridge is broken, upgrading to the Fedora 40 Beta with Plasma 6 kinda improved the situation, but maybe I have just gotten used to a lot of it(I also disabled a lot of the crash notifications).

Compared to Manjaro a long term friend and the first Linux Distro I settled with when I switched ~5years ago from Windows and being able to use the AUR without any issues, and butter smooth experience until you have a bug once in a while(or nearly never) is probably going to make me switch back to Manjaro some time soon. Although I might consider testing out another Arch(-based) Distro with a tiling-windowmanager that supports hardware accaleration.

This is second amazing update of KDE for me since KDE3.5 update. İt was beautiful shiny and very usefull yet traditional. Then yesterday i got kde plasma 6 update and manjaro update as an KDE aspect it is really became faster yet smooth and fluent for me. Only minor problems with couple applicatons become odd and unable to update thus system wide upgrade happened before their updates show up. But i did uninstall and re-install as google-chrome,scrcpy,freedownloadmanager. İts very good in shape and performans. İ like Manjaro more now. mostly using it for gaming and for AI stuff.

If you love Manjaro, I'm not going to change your mind. Good for you. Be happy. Promote it even.

I moved on because there were small differences between my kids' Manjaro systems and my Arch system, and I got fed up. I wanted to be able to expect my configuration actions to have the same results (like script functionality and software versions). Additionally, avoiding a "major upgrade" as is described here is the exact reason I am on a rolling release, so Manjaro's user experience does not jive with me. It's like a rounded step release instead of rolling.

avoiding a "major upgrade" as is described here is the exact reason I am on a rolling release, so Manjaro's user experience does not jive with me. It's like a rounded step release instead of rolling.

i am not avoiding, i am delaying
!link

it just does not look very good, but i will clone my drive in a few days an try the update


many problems come with KDE6, so it does not matter what form of release you have. kubuntu will face the same issues, but they have 5 more months to fix them, because they did not use it for 24.4


Last edited by mylka on 19 May 2024 at 7:00 pm UTC

!link

I had one issue on one of my computer where Manjaro is installed:
upgrade did not start, I had an error message about gpart.
I uninstalled gpart then everything ok

It's a little issue, nothing compared to an Ubuntu upgrade version where upgrade halted before the end and you can no more start the computer.


Last edited by legluondunet on 19 May 2024 at 9:20 pm UTC

It's a little issue, nothing compared to an Ubuntu upgrade version where upgrade halted before the end and you can no more start the computer.

according to your profile you are not using KDE and i think most people have troubles with the step from KDE5 to KDE6.

i have a second PC with Kubuntu for some years now. never had troubles upgrading it. btw i need to upgrade to 24.4
but i try to keep my systems as vanilla as possible to avoid such problems

many problems come with KDE6, so it does not matter what form of release you have. kubuntu will face the same issues, but they have 5 more months to fix them, because they did not use it for 24.4

Well, that depends. Any distribution's customizations can have an effect if they have to be tweaked for compatibility. It would be interesting if the same poll was on Arch and KDE Neon, some of the earliest adopters I can think of.

I don't think I had any unexpected issues with the multiple Arch machines I maintain. But yes, I made BTRFS snapshots of my root and home partitions as well as a file-level backup of the entire system before I upgraded. I also performed the upgrade in a Virtual Machine first, like I do routinely with system updates.


Last edited by 14 on 20 May 2024 at 2:27 am UTC

I don't think I had any unexpected issues with the multiple Arch machines I maintain.

Just expected issues?

I don't think I had any unexpected issues with the multiple Arch machines I maintain.

Just expected issues?

I have been running Arch since 2015, and if memory serves, have experienced two updates that prohibited me from booting and logging in normally.

There used to be a trend that started from Windows, but I think those same people got used to it and became fond of "reformatting" every 1-2 years. You know what? I'm not one of those guys. I do not like reconfiguring all my settings and preferences. You think you're done, but then you open a program you seldomly use, and now have to spend all this extra time you didn't alot any time for. I ran away from major OS upgrades which recommended reinstalls for a cleaner experience.

So yeah, a reliable way to roll back single files or an entire snapshot is my style whether a problem is expected or not. I do backups every week, and it wasn't Arch that started that habit. It was Windows 98 and my dad's teaching, further cemented by my IT infrastructure career.

I know you were only poking. Oh well. I responded.

I don't think I had any unexpected issues with the multiple Arch machines I maintain.

Just expected issues?

I've been running Arch for the past four years.

Last year, many people found out that Arch does not automatically upgrade GRUB; you need to do that yourself. This became an issue when a new GRUB version wasn't compatible with the old version for [reasons], I forget.

I also got my laptop serviced and after some testing was run in the BIOS, my bootloader was broken. I needed to re-install GRUB via LiveCD.

Two years ago, my sound suddenly disappeared. This was the pipewire-media-session➜wireplumber transition (or maybe pulse to pipewire, I forget). It took me several hours to figure out how to get my sound back, and in the process, I learned the basics of pulseaudio sound sinks. This knowledge continues to come in handy many years later as I regularly need to use Pavucontrol to reroute audio streams to the right audio device whenever I plug my laptop in via HDMI, as for some reason that causes it to become greatly confused with some programs (but not others). I don't have much love for audio configuration on Linux.

Over the past few years, several programs like Anki have no longer opened after being updated—and actually, Anki has been broken for a few weeks now. This underscores to me the value in separation between host system and user programs that Silverblue creates. I'd rather use Verified Flatpaks though, and Anki doesn't have much interest in adopting the package.

There have been a few other incidents not significant enough for me to remember in any detail.

Breakage on Arch tends to visit me every few months, but for a long time I've viewed breakage as inevitable on Linux. The only difference is I know how to fix the breakage on Arch, but I wouldn't have a clue if you put me in front of Ubuntu or openSUSE. Part of that is lack of experience; the other part is complexity.

...but I've been playing with Fedora Workstation/Silverblue lately, and I've had my perspective challenged.

I know you were only poking.

Yeah, the winkie emoji was supposed to be this subtle signal that I was joking around. Too subtle for some, it would seem.

I know you were only poking.

Yeah, the winkie emoji was supposed to be this subtle signal that I was joking around. Too subtle for some, it would seem.

Is it worse if I was also aware it was a joke and took it seriously anyway?

Probably. It's a slow week.

I don't think I had any unexpected issues with the multiple Arch machines I maintain.

Just expected issues?

I've been running Arch for the past four years.

Last year, many people found out that Arch does not automatically upgrade GRUB; you need to do that yourself. This became an issue when a new GRUB version wasn't compatible with the old version for [reasons], I forget.

I also got my laptop serviced and after some testing was run in the BIOS, my bootloader was broken. I needed to re-install GRUB via LiveCD.

Two years ago, my sound suddenly disappeared. This was the pipewire-media-session➜wireplumber transition (or maybe pulse to pipewire, I forget). It took me several hours to figure out how to get my sound back, and in the process, I learned the basics of pulseaudio sound sinks. This knowledge continues to come in handy many years later as I regularly need to use Pavucontrol to reroute audio streams to the right audio device whenever I plug my laptop in via HDMI, as for some reason that causes it to become greatly confused with some programs (but not others). I don't have much love for audio configuration on Linux.

Over the past few years, several programs like Anki have no longer opened after being updated—and actually, Anki has been broken for a few weeks now. This underscores to me the value in separation between host system and user programs that Silverblue creates. I'd rather use Verified Flatpaks though, and Anki doesn't have much interest in adopting the package.

There have been a few other incidents not significant enough for me to remember in any detail.

Breakage on Arch tends to visit me every few months, but for a long time I've viewed breakage as inevitable on Linux. The only difference is I know how to fix the breakage on Arch, but I wouldn't have a clue if you put me in front of Ubuntu or openSUSE. Part of that is lack of experience; the other part is complexity.

...but I've been playing with Fedora Workstation/Silverblue lately, and I've had my perspective challenged.

I'm a debian stable user.
Random breakage is rare.
I'm also a low tier tinkerer.
To me "expected issues" are issues I create by trying some ridiculous trickery I don't need.
Running it on an ARM processor breaks my standard browser.
Getting fingerprint scanning to work requires driver trickery.
Having a lot of privacy protections on your browser breaks websites.
Etc.

Last year, many people found out that Arch does not automatically upgrade GRUB; you need to do that yourself. This became an issue when a new GRUB version wasn't compatible with the old version for [reasons], I forget.

If you got bitten by this, I suggest joining the mailing list. You'll know in advance if manual action is required. It is not noisy either. It is exactly the Latest News RSS feed on the main page: https://archlinux.org/

Running systemd-boot for years and never had a problem, plus its configuration is so simple. Running (the often problematic in the past) GRUB in 2024 makes no sense to me (except you have an old motherboard), when for years most (common) distros use systemd, and you can switch from it to systemd-boot easily.


Last edited by sudoer on 21 May 2024 at 1:07 pm UTC

Last year, many people found out that Arch does not automatically upgrade GRUB; you need to do that yourself. This became an issue when a new GRUB version wasn't compatible with the old version for [reasons], I forget.

If you got bitten by this, I suggest joining the mailing list. You'll know in advance if manual action is required. It is not noisy either. It is exactly the Latest News RSS feed on the main page: https://archlinux.org/

I didn't, actually. I hadn't updated for a few weeks coincidentally, but I happened to read a post on reddit about it so I knew in advance. I already have the Arch News RSS feed in my reader, but Arch took several days to announce the GRUB issue. I followed the instructions and nothing went wrong on any of my Arch computers.

The mailing list is a good suggestion.

Running systemd-boot for years and never had a problem, plus its configuration is so simple. Running (the often problematic in the past) GRUB in 2024 makes no sense to me (except you have an old motherboard), when for years most (common) distros use systemd, and you can switch from it to systemd-boot easily.

I only run it because I understand it. GRUB has been (generally) reliable for me and at least when I break it, I know how to fix it. Same reason as Arch, actually. I can't be bothered to learn a new bootloader, basically.

And I know Pop uses Systemd-boot, but Fedora and Ubuntu use GRUB. Linux Mint probably does too. So there must be a reason. I don't know about openSUSE, though.