pacman-mirrors: local (4.23.3-2) is newer than core (4.23.2+3+g4148c3d-1)
I also got the kpeoplevcard: local (0.1+r38.32d50a9-1) is newer than extra (0.1-2) and since above recomended allowing downgrade, I did that and it worked.
as for pacman-mirrors run
sudo pacman -Syuu
No need to sync again. The first line is enough.
pacman-mirrors version: 4.23.3+10+gbd0d802-1 is buggy
pacman-mirrors -G ==> result is:
LANGUAGES [‘de_DE’, ‘UTF-8’, ‘’, ‘en_US’]
APP_DIR /usr/share
LOCALE_DIR /usr/share/locale
LOCALE (‘de_DE’, ‘UTF-8’)
unstable
Version 4.23.3-2 is o.K.
pacman-mirrors -G ==> result is:
unstable
Me too:
sudo pacman-mirrors --fasttrack
LANGUAGES ['en_US', 'UTF-8', '', 'en_US', 'UTF-8']
APP_DIR /usr/share
LOCALE_DIR /usr/share/locale
LOCALE ('en_US', 'UTF-8')
::INFO Downloading mirrors from Manjaro
...
what you guys mean? that we display some debug messages to develop pacman-mirrors? Well you’re on the unstable branch, dude.
1 Like
not a bug - new feature on unstable branch 
- don’t worry - we will be out of your hair later …
1 Like
I like the horses in the un-stable too.
Wilhelm Busch (Max & Moritz):
“Doch zuletzt verzehret sie Meister Müllers Federvieh.”
In fact, the unstable branch is actually the most stable one. Because many necessary apps are only provided via AUR like
- Zoom,
- Slack,
- Skype,
- Spotify,
- Chrome,
- VSCode (with .NET debugger),
- Android Studio,
- Genymotion
- Teamviewer,
- Sublim Text,
- WPS Office,
- Foxit Reader/Editor,
- Joplin,
- …
And to ensure the stability and the compatibility of these apps with the rest of installed libraries, it’s safe and sometimes necessary to switch to unstable branch.
1 Like
I love testing and supporting development, but how are we supposed to know that was on purpose?
I too run testing and unstable on my machines (ew stable branch),
so the output difference is clear and makes you think.
Anyways, good to know. 
There is also this thing called flatpak that contains many of the things you list.
I know some ppl do not like to use flatpaks, but tbh, if the choice is flatpak or switch to unstable, flatpaks could be preferred choice for many ppl.
My rule of thumb is to not use anything in a container unless it is the only way to get a particular app, or the containered app is the only version of it that actually works. As for Manjaro Unstable I’ve run it more than a few times and no more issues with it then Stable.
2 Likes
And I agree to that, I do the same.
But I was talking about the “vanilla” user, the person that relies on pamac to automatically update and has always been on stable.
To that person, switching to unstable, doing updates daily (or at least not every 3-4 weeks like in stable) could easily create more problems than solving.
1 Like
I’m getting error: command failed to execute correctly after upgrading these packages
suitesparse
coin-or-clp
coin-or-cgl
coin-or-mp
containerd
krb5
ddcutil
docker
docker-compose
fzf
krita-plugin-gmic
lib32-brotli
lib32-libdrm
libmatio
linux-firmware-whence
linux-firmware
powerdevil
python-pikepdf
...
==> Image generation successful
( 6/10) Refreshing PackageKit...
( 7/10) Reloading system bus configuration...
( 8/10) Checking which packages need to be rebuilt
( 9/10) Updating the info directory file...
error: command failed to execute correctly
(10/10) Updating the desktop file MIME type cache...
Each time I force reinstalling those same packages, I always get that error.
Pacman log shows nothing important
[2023-10-29T22:45:37+0100] [ALPM-SCRIPTLET] ==> Image generation successful
[2023-10-29T22:45:39+0100] [ALPM] running '90-packagekit-refresh.hook'...
[2023-10-29T22:45:39+0100] [ALPM] running 'dbus-reload.hook'...
[2023-10-29T22:45:40+0100] [ALPM] running 'rebuild-detector.hook'...
[2023-10-29T22:47:13+0100] [ALPM] running 'texinfo-install.hook'...
[2023-10-29T22:47:13+0100] [ALPM] running 'update-desktop-database.hook'...
What hook is that?
Oh, looks like this one:
Which is from texinfo, which I have, but I have not noticed it complaining.
(actually, the hook was not triggered by the most recent updates)
It should be triggered by anything owning or installing to /usr/share/info/*
You can see the hook here:
cat /usr/share/libalpm/hooks/texinfo-install.hook
The exec line (and what is apparently failing) is
/bin/sh -c 'while read -r f; do install-info "$f" /usr/share/info/dir 2> /dev/null; done'
Heads up, bash 5.2 is among the current updates:
2 Likes
NVIDIA At least we are only affected by this:
NVIDIA GPU Display Driver for Windows and Linux contains a vulnerability in the kernel mode layer, where a NULL-pointer dereference may lead to denial of service.
Windows on the other hand… xD
Thank you for the heads up on the release.
we have to double check on the Nvidia driver modules as for 6.6 kernel series we have 3 different options in all our branches. So at least 390xx and 470xx need different compiles in each branch.
390 is EOL, there was no release. 