Pamac may crash during big updates. Use regular pacman to update and after it finishes, reboot and update the remaining stuff (AUR packages, flatpaks, etc) with pamac.
You may want to try shelly as an alternative to pamac (but it’s in the AUR, so…)
No, you don’t want to use shelly for system updates !!! Use pacman. It also has the added benefit of not mixing system and aur updates.
4 Likes
I’d suggest using yay for AUR package rebuilds and upgrades. Maybe with octopi as a GUI interface. Naturally, after doing the repository packages. 
2 Likes
Please people, look at the “Known issues and solutions” post before commenting.
The pamac issue — and the workaround — have already been addressed 8 Stable Updates ago, and it’s still mentioned as such in the second post of this thread here.. 
5 Likes
Update went smoothly, no hiccups at all.
My system started with XFCE, which I still have, but I later added KDE, which I use daily (click my avatar circle to see the other parameters of my system).
I was able to update. Although I had to use the reset button on my case because when I executed the reboot command my fans kept spinning but the peripherals turned off. I suspect is because of the issue I posted about on the last update topic where the commands and plasma menu for reboot and turn off didn’t fully work. The solution had been to log out and turn off on SDDM. I’ll report back if that’s still the case.
Update all went smoothly, just curious, is there a reason every time the update puts me up on 7.1.4 instead of the LTS? What are the main benefits of the 7.1.4 kernel? I’ve been using 6.18 LTS
You probably have the linux-meta package installed, which will replace any EOL kernels on your system which are no longer in the repos with the latest stable release kernel from the repos. So, if you had linux70 or linux619 installed on your system, then the linux-meta package would have removed them and added linux71 to your system.
linux-meta is not a required package. You can safely remove it from your system if you want to manage your installed kernels yourself.
1 Like
I don’t use it myself, but If pamac is unreliable, why not just pull it out from the distro? I can understand that if a user is given a tool that is installed by default, they would consider that tool safe to use…
Why Manjaro has to offer a broken tool for such critical role? What is it purpose? If pamac can’t be repaired, let it just die.
1 Like
I was also wondering about this.
Why not change the default to octopi or fork pamac if the original developer is no longer working on it? I personally really like pamac visually, especially since it gives a small description of the programs and shows the app icon, some screenshots and other useful information. It also handles flatpaks too.
But sadly it’s been in a semi-broken state for a while now, which is really sad because I used to use it a lot several years ago when I started using Manjaro, but I barely ever use it now.
For newcomers to Manjaro, they will default to using the built in package manager which is Pamac and it will end up breaking their system on updates and they will assume that something is wrong with Manjaro itself when the fault actually lies with Pamac.
1 Like
this comes with new version fontconfig 2.18.2, alas i have the same problem as with 2.18.1: broken (monospace) fonts in vivaldi menu (chrome based browser).
downgraded back to 2.17.1 - all good again.
1 Like
2 posts were split to a new topic: Deepin package conflicts on latest stable update
The headline should be rather formulated neutral like “Pamac issue reported”. There is no real measure of reliability. There are also no statistics, merely some reports here and there. Moreover, while I experienced the issue myself (but only on one of my systems) I’m not aware that the whole upgrade process broke down. Rather the GUI or the CLI aren’t relevant for the actual upgrade process - they are just interfaces, the actual work is done by a background process. (However, of course, if you lose the feedback and reboot without checking whether the upgrade was finished successfully, then there is a good chance to break the system.)
2 Likes
I’m sorry, but that is simply not accurate. There have been numerous reports regarding pamac’s instability/unreliability. Even some of the mods here regularly advise users to use pacman instead.
Personally, I stopped using pamac for system upgrades due to it reproducibly crashing mid-update (on CLI, mind you). Yes, the update usually finishes successfully in the background, but that’s kinda besides the point.
1 Like
Though octopi doesn’t support appstream metadata (for icons, screenshots, changelog…) and the developer doesn’t want to add it.
It doesn’t work as well with the AUR by default, not showing the list of all packages, and with yay it only shows what we search, not the whole list.
I’m running Manjaro on my main driver since 6 years. I never used anything else but the pamac gui even when i switched to unstable. If i wouldn’t be in the forum i wouldn’t even know the issue would exist. Except for it appeared on one of my other systems but only on the one. There it looked to be quite reproducible so i won’t blame or laugh at anyone who experiences the issue and thinks it happens all the time for everyone. Then all of a sudden the issue disappeared again and i’m still waiting for it so i have another chance to perhaps find out more about it.