[Stable Update] 2023-10-09 - Mesa, Grub, GlibC, Thunderbird, KDE Frameworks Renaming

[AMDave]

pacman likes to get your permission for each package
If you prefer not to have to respond to each package prompt, you can use pamac instead of pacman

sudo pamac update

pamac will take care of it for you

But refresh your mirrors beforehand

sudo pacman-mirrors --country all --api --protocols all --set-branch stable

assuming you are on stable branch as you are posting in this thread.

Together in sequence:

sudo pacman-mirrors --country all --api --protocols all --set-branch stable && sudo pamac update

[Xephon]

The update shuffled application grid in KDE Application Launcher->Favourites. Not an issue but a weird behaviour. Except that everything looks fine.

[MrLavender]

@Xephon

The update shuffled application grid in KDE Application Launcher->Favourites. Not an issue but a weird behaviour. Except that everything looks fine.

Yes I also saw that behaviour. Not a big deal and preferable to it forgetting window size/position preferences as has happened in the past.

I needed sudo pacman -Syu glibc-locales --overwrite /usr/lib/locale/\*/\* so thanks @philm for that heads up. Now taking bets on how many people won’t read that.

[Fabian]

Why does that require renames? Doesn’t hat imply that I will not get the version 6 update?

[Keruskerfuerst]

I have a problem with update from today:
e.g.: glibc locales: /usr/lib/locale/zu_ZA_utf.8/LC Time exists in filesystem.

[Mirdarthos]

@philm

glibc-locales update requires manual intervention

If you had the old glibc-locales package from the extra repo installed, the update to the new core package will need manual intervention:

 sudo pacman -Syu glibc-locales --overwrite /usr/lib/locale/\*/\*

[stormschip]

During boot i noticed a warning

BFPT parsing failed please consider SPI_NO

journalctl -b -t kernel -p3

spi-nor spi0.0: BFPT parsing failed. Please consider using SPI_NOR_SKIP_SFDP when declaring the flash

The solution for me is create a file spi_nor.conf in /etc/modprobe.d

sudo vim /etc/modprobe.d/spi_nor.conf
blacklist spi_nor

more information in the archwiki
https://wiki.archlinux.org/title/Kernel_module#Blacklisting

[reinheaven]

Update failed using pacman-mirrors -f && sudo pacman -Syyu but updating via GUI/pamac worked.

One minor thing that caught my eye is that favorites in the application overview are no longer in the order I set.

The update also solved a problem I had been having for some time where icons on the desktop would no longer show as highlighted after they were selected.

[1efaf7d71a8637c6800a]

Thank you for getting the security fix for glibc out!

I’m also getting a renamed GTK package, before updating:
libgedit-amtk and amtk are in conflict
and Pacman wants me to remove the latter [y/N]

Says the package amtk was renamed here:
“The project has been renamed to libgedit-amtk and is now hosted on…” Gedit Technology.

So it’s probably reinstalled under the new name during the process.

[Aragorn]

@AMDave

pacman likes to get your permission for each package
If you prefer not to have to respond to each package prompt, you can use pamac instead of pacman

sudo pamac update

pamac will take care of it for you

@AMDave

Together in sequence:

sudo pacman-mirrors --country all --api --protocols all --set-branch stable && sudo pamac update

Never use sudo with pamac. It will mess up the permissions on your package databases.

pamac is intended to be run with the user’s own privileges and will prompt you for a password when needed.

---

@Fabian

Why does that require renames? Doesn’t hat imply that I will not get the version 6 update?

It simply implies that there will be a choice when Plasma 6 hits the repos, so that no packages from Plasma 6 will be overwriting packages needed in Plasma 5.

[MrLavender]

@philm

If you had the old glibc-locales package from the extra repo installed, the update to the new core package will need manual intervention:

 sudo pacman -Syu glibc-locales --overwrite /usr/lib/locale/\*/\*

@MrLavender

Now taking bets on how many people won’t read that.

[Aragorn]

Somehow — only the universe knows why — my Plasma desktop was once again completely screwed up after updating. The symptoms were the same as the last time.

I had to restore a full system backup — and a separate (and even earlier) copy of my $HOME, because the copy in the last backup was corrupt again as well — and then run the update process all over again. And then it all worked out fine again.

[ARSManiac]

After reading this update announcement as I always do the update went fine
(I did sudo pacman -Syu glibc-locales --overwrite /usr/lib/locale/\*/\* and said Yes to replace some packages), the only thing I noticed is that pamac in now full white (it had a dark theme like the rest of my system) but not bothering me at all since everything is working as it should.
Manjaro XFCE for more than 3 years here.