[multilib]
SigLevel = PackageRequired
Include = /etc/pacman.d/mirrorlist
Finished the update. Had an issue with Cairo-Dock, solved by downgrading. Avoided the electron dependency hell by uninstalling all versions before the update and then installing the electron package after the update. All seems fine now. Thanks to everyone who posted about these issues. Made it a lot easier for me.
1 Like
This is a little harsh… I maintain my system very well, but completely missed this. When you do a full update, the lines go by so fast, you miss it 768 patches less than a MB goes by really fast. I saw the error and checked this thtread and only then did i realize there was a pacnew on here. Debian implemented something neat where the changelogs are now part of the update with apt. When you do a apt upgrade, first thing it does is pull down the changelogs and displays them. Does pacman have a similar option or funcationality? I guess I will have to tee the output going forward.
Edit: if u use pamac gui, Joe user normally doesnt even check the text output unless there is an error.
2 Likes
Refresh your mirrors and databases, and update your system packages first… 
sudo pacman-mirrors -f && sudo pacman -Fy && sudo pacman -Syyu
Then update the rest…
pamac update
Also, see this handy tutorial below…
The golden rule is to always check the Announcements > Stable Updates thread first — or at the very least, the first two posts of it — and to also always run…
pacdiff -o
… after updating, so that you would know whether there are any .pacnew files.
No, pacman does not have that, but you can inspect the logs with the paclog utility.
Yes, and that is unfortunate. At the risk of once again being misunderstood, Manjaro is not a suitable distribution for people who regard their system as merely a kitchen sink appliance — which is exactly how Microsoft and Apple want you to think of your computer, and how they have thus conditioned their user base to think.
Manjaro is based upon Arch, and even though Manjaro is a lot more user-friendly than Arch, it still is and remains a very technical distribution. This does not mean that you have to be a computer scientist in order to use Manjaro, but it does require a certain commitment and sense of responsibility from its users.
It’s a distribution that requires periodic maintenance and a willingness to learn and get one’s hands dirty, so to speak, both because of its Arch roots and because of the fact that it’s a (curated) rolling-release distribution.
“Rolling release” means that the system is not updated/upgraded monolithically, but rather in small and sometimes not-so-small increments of the versions of different components, but with different incremental steps depending on the exact components. As such, it’ll never be as smooth as a fresh install of a point-release distribution like Ubuntu, Mageia, Mint, et al — and mind you that even said other distributions bring along their fair share of hiccups.
All things considered, Manjaro is a rock-solid distribution if one is willing to learn and pay attention. Occasional gotchas do pop up from time to time — some worse than others — but just as an example, I installed this system in late April 2019, and I have so far never had to reinstall.
I did have to restore a timeshift backup once — due to the Plasma 5.25 fiasco, but that was obviously an upstream problem — but other than that I’ve so far never had any serious problems with Manjaro, and I’m using it as my daily driver.
11 Likes
If you have not done so already, you may want to try refreshing your mirror list.
sudo pacman-mirrors --continent
From a few other similar threads, I am getting the impression that your problem may be caused by one of the handful of out-of-date mirrors. For example, right now India’s 2 mirrors don’t seem to be in good shape.
1 Like
What I do is copy the entire Terminal output to a log file (on a separate partition).
You will have to set scrollback to “unlimited” (or at least a couple of thousand lines) to avoid losing the top part.
For example:
Select all text, copy it then do something like
nano /DATA/LOGS/System_Upgrade_20250305.txt
and paste, save, exit.
In my case /DATA is the partition I set up for general storage.
This way the update logs are easily accessible for review.
Another method is to append --logfile= <path-to-file> e.g.:
sudo pacman -Syu --logfile /DATA/LOGS/System_Upgrade_20250305.txt
1 Like
Exactly that. I have been using Manjaro since 2022 and I love it and it suits my needs. I love that it is a curated rolling release and it has been smooth sailing. But I will not recommend it to a new user as, as you said, it requires you to get your hands dirty, such as choosing your own kernel.
For new users I usually recommend other distros based on their daily tasks.
3 Likes
Once again, I say Bravo, job well done!
Today I updated four Manjaro systems: a mini, a laptop, an ancient dinosaur, and a nvidia monster gaming machine, all without a single issue.
I’m in danger of becoming a Manjarohollic 
5 Likes
Anyone able to comment on whether the previous stable release’s SDL2=>SDL3 update (introducing the sdl2-compat compatibility layer) has been addressed in this release with regards to the steam coredumps?
EDIT: Hmm I might have found my answer by checking Branch compare for Manjaro … seems the required version is in Stable now, but would still like to hear anyone’s experience confirming no more steam coredumps with SDL3/sdl2-compat.
I had a problem with HDR, the colors were extremely saturated.
As the “HDR” checkbox is no longer displayed in the settings (why?), I had to use the command line to disable it:
kscreen-doctor output.DP-1.hdr.disable
Replace DP-1 with your screen. To find out what it is, use the command:
kscreen-doctor -o
For the record, I’m using KDE Plasma, Wayland and an RTX 4080 with the proprietary NVIDIA driver.
1 Like
No problems, both computers. just as stable as the last update. Thanks team Manjaro 
2 Likes
Trying the update I get this error:
sudo pacman -Syu ✔
:: Synchronizing package databases...
core is up to date
extra is up to date
multilib is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: installing icu (76.1-1) breaks dependency 'libicui18n.so=75-64' required by electron28
:: installing icu (76.1-1) breaks dependency 'libicuuc.so=75-64' required by electron28
:: installing flac (1.5.0-1) breaks dependency 'libFLAC.so=12-64' required by electron28
:: installing icu (76.1-1) breaks dependency 'libicui18n.so=75-64' required by electron29
:: installing icu (76.1-1) breaks dependency 'libicuuc.so=75-64' required by electron29
:: installing flac (1.5.0-1) breaks dependency 'libFLAC.so=12-64' required by electron29
I’ve checked my etc/pacman.conf and pacnew files and they don’t reference the community repo.
I’ve solved the issue by executing sudo pacman -R electron28 electron29.
No dependencies seem to be broken and I’m assuming I was already not using the community repo since I didn’t encounter an issue related to that while updating.
3 Likes
Pamac window vanished suddenly during the update process, same as last stable update three weeks ago. Unfortunately there’s no pamac log file, afaik. Pacman log shows no error, at least the update went through successfully. Over time I become wiser, so next time I will use pacman to update the system.
There is also paclog, which lists everything, also with colours.
EDIT: is part of the package pacutils.
3 Likes
For anyone having a problem with icu and flac dependencies for electron, if you need a specific version, just install the -bin version from the AUR which doesn’t depend on icu and flac.
1 Like
Such a lovely update! Went smooth as butter on both of my machines.
This has finally resolved screen tearing issues with wayland session for me (not all of them, but most of them).
1 Like
Issue with kernel 6.13.2 using AMD amd-pstate=pstate-passive.
I still experience my Zen3 idle clocks not lowing to the lowest pstate. They stick around the ~1700Mhz mark while idle.
Switching back to 6.12.x resolves this.
Is there a way to retain output generated by pamac somehow? There seems to be no option like pacman’s --logfile.
Install pacutils and run paclog; you can output it to a text file, if you need to retain it.
3 Likes
Just look into /var/log/pacman.log and you will see most, if not all, pamac output.
2 Likes