[Testing Update] 2023-10-21 – Kernels, GNOME 45, VirtualBox, KDE, Thunderbird – Testing Updates
Hello community,
Another testing branch update with some usual package updates for you.
Get the lastest SoftMaker Office with ChatGPT buillt-in. You will find our Special Offer here!
Recent News:
- Manjaro, like many other open-source projects, relies on the generosity of its community through donations and corporate sponsorships to support its growth and development. These donations are essential in covering the various expenses incurred in the operations of the project such as server costs, software development tools, infrastructure expenses, training, flying people to events or conferences and the salaries of key developers. With the help of these donations, Manjaro is able to secure the necessary financial stability that allows the project to continuously improve and remain active. If you love Manjaro, consider to donate!
Previous News
Finding information easier about Manjaro
Finding information easier about Manjaro always has been a topic that needed to be solved. With our new search we have put all Manjaro data accessible in one place and divided by sections so it makes it easier to digest: New Manjaro search engine is available | Blog
Notable Package Updates:
- Most Kernels got updated
- we dropped ZFS support.
There is still some dkms support but we are considering to drop it completely
- we dropped ZFS support.
- GNOME 45
- PipeWire is now at 1.0-rc3
- KDE Gear got renewed to 23.08.2 and KDE Frameworks is at 5.111.0
- We updated Gnome to 45.0
- remember to check your extensions for compability
- Thunderbird got updated to 115.3.3
- Virtualbox got renewed to 7.0.12
- Usual Haskell and Python updates
Additional Info
Info about AUR packages
AUR (Arch User Repository) packages are neither supported by Arch nor Manjaro. Posts about them in Announcement topics are off-topic and will be flagged, moved or removed without warning.
Get our latest daily developer images now from Github: Plasma, GNOME, XFCE. You can get the latest stable releases of Manjaro from CDN77.
Our current supported kernels
- linux419 4.19.296
- linux54 5.4.258
- linux510 5.10.198
- linux515 5.15.136
- linux61 6.1.59
- linux64 6.4.16 [EOL]
- linux65 6.5.8
- linux66 6.6.0rc6
- linux61-rt 6.1.59_rt16
- linux64-rt 6.4.6_rt8
- linux65-rt 6.5.2_rt8
Package Changes (Sat Oct 21 07:16:24 CEST 2023)
- testing core x86_64: 37 new and 40 removed package(s)
- testing extra x86_64: 1971 new and 1971 removed package(s)
- testing kde-unstable x86_64: 283 new and 275 removed package(s)
- testing multilib x86_64: 24 new and 27 removed package(s)
All changes can be found here.
- No issue, everything went smoothly
- Yes there was an issue. I was able to resolve it myself.(Please post your solution)
- Yes i am currently experiencing an issue due to the update. (Please post about it)
Check if your mirror has already synced:
4 Likes
Known issues and solutions
This is a wiki post; please edit as necessary.
Please, consider subscribing to the Testing Updates Announcements RSS feed
Please RTFT (Read This Fine Thread) first before reporting the same issues over and over again!
2023-10-21
ZFS package changes
ZFS extramodules; i.e., linuxXX-zfs
, have been dropped from the repos. There have been recent difficulties building them and no one on the Manjaro Team uses ZFS.
Please install zfs-dkms
instead. You will to need to manually remove the old 2.1.13 extramodule package(s) first to install the new 2.2.0 packages; i.e., with linux61
:
sudo pacman -R linux61-zfs && sudo pacman -Syu zfs-dkms
Restarting gnome-shell using Alt+F2 and entering R, causes a crash
FS#79884 : [gnome-shell] Restarting gnome-shell using Alt+F2 and entering R, causes a crash
GNOME Extensions that target older GNOME versions will not work in GNOME 45
It is recommended to remove all third-party extensions before updating, then install the compatible versions after updating and rebooting. All Most extensions in the Manjaro repos are already updated.
2023-10-05
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/*/*
2023-09-27
Changes to default password hashing algorithm and umask settings
2023-09-22 – David Runge
With shadow >=
4.14.0
, Arch Linux’s default password hashing algorithm changed from SHA512 to yescrypt [1].Furthermore, the
umask
[2] settings are now configured in/etc/login.defs
instead of/etc/profile
.This should not require any manual intervention.
Reasons for Yescrypt
The password-based key derivation function (KDF) and password hashing scheme yescrypt has been chosen due to its adoption (readily available in libxcrypt, which is used by pam [3]) and its stronger resilience towards password cracking attempts over SHA512.
Although the winner of the Password Hashing Competition [4] has been argon2, this even more resilient algorithm is not yet available in libxcrypt [5][6].
Configuring yescrypt
The
YESCRYPT_COST_FACTOR
setting in/etc/login.defs
is currently without effect, until pam implements reading its value [7]. If aYESCRYPT_COST_FACTOR
higher (or lower) than the default (5
) is needed, it can be set using therounds
option of thepam_unix
[8] module (i.e. in/etc/pam.d/system-auth
).General list of changes
- yescrypt is used as default password hashing algorithm, instead of SHA512
- pam honors the chosen
ENCRYPT_METHOD
in/etc/login.defs
and does not override the chosen method anymore- changes in the filesystem (>=
2023.09.18
) and pambase (>=20230918
) packages ensure, thatumask
is set centrally in/etc/login.defs
instead of/etc/profile
[1] yescrypt – scalable KDF and password hashing scheme
[2] umask(1p) — Arch manual pages
[3] PAM – ArchWiki
[4] https://www.password-hashing.net/
[5] https://github.com/besser82/libxcrypt/pull/113
[6] Add support for Argon2 by maandree · Pull Request #150 · besser82/libxcrypt · GitHub
– Arch Linux – News: Changes to default password hashing algorithm and umask settings
2023-09-06
filesystem and bashrc-manjaro pacnews
With the filesystem
2023.09.03-1 and bashrc-manjaro
5.1.016-3 updates there may be pacnews for the following files if you have local modifications:
/etc/shells
/etc/bash.bashrc
This would be a good time to test @Ste74’s new manjaro-pacnew-checker
program. See Check and manage pacnew files for more info.
2023-08-25
ansible-core >= 2.15.3-1 update may require manual intervention
2023-08-19 – Robin Candau
As of
ansible-core 2.15.3
, upstream moved documentation and examples to a separate dedicated repository (see the related changelogs).
This means that, starting from version2.15.3
theansible-core
package will stop shipping documentation and a default configuration example under/etc/ansible/ansible.cfg
.Regarding the documentation, it is available online: https://docs.ansible.com/
As for the configuration file, as explained in the wiki, a base config can be generated with the following command:
ansible-config init --disabled > ansible.cfg
After updating from
ansible-core
<=2.15.2-1
to >=2.15.3-1
, everyone using a custom global Ansible configuration file stored under/etc/ansible/ansible.cfg
will have their configuration saved as apacsave
file.
To restore it, run the following command:
mv /etc/ansible/ansible.cfg.pacsave /etc/ansible/ansible.cfg
– Arch Linux – News: ansible-core >= 2.15.3-1 update may require manual intervention
2023-08-04
Possible glibc 2.38 posix_memalign regression
There seems a performance regression of posix_memalign in Glibc-2.38. More info here: 30723 – Poor posix_memalign performance with long free lists
Workarounds:
You can try another malloc like mimalloc or jemalloc as workaround. Install mimalloc and start mpv with:
LD_PRELOAD=/usr/lib/libmimalloc.so mpv
or
LD_PRELOAD=/usr/lib/libjemalloc.so mpv
For folks that dont want to change things too much … an apparent workaround is to set a lowish cache size:
mkdir -p ~/.config/mpv && printf 'ndemuxer-max-bytes=50MiBndemuxer-max-back-bytes=25MiBn' | tee -a ~/.config/mpv/mpv.conf
budgie-desktop >= 10.7.2-6 update requires manual intervention
When upgrading from budgie-desktop
10.7.2-5 to 10.7.2-6, the package mutter43
must be replaced with magpie-wm
, which currently depends on mutter
. As mutter43
conflicts with mutter
, manual intervention is required to complete the upgrade.
First remove mutter43
, then immediately perform the upgrade. Do not relog or reboot between these steps.
pacman -Rdd mutter43
pacman -Syu
2023-07-28
Grub conflicting files
Error: Failed to commit transaction:
conflicting files:
grub: /usr/bin/update-grub already exists in filesystem (owned by grub-update)
sudo pacman -Rdd grub-update
sudo pacman -Suu grub
2023-07-24
One core of CPU has high IO-wait operation at 100%
[Unstable Update] 2023-05-21 – Repository changes – #199 by Zesko
Kernel 6.4.4, 6.4.5 and 6.1.39 LTS are affected:
The known issue and report:
2023-07-15
Steam crashes on startup with lib32-libgudev installed
The latest lib32-libgudev
update does not cooperate with the version of the same package provided by steam, and steam seems to attempt making calls to both leading to the crash.
Details: bug report, arch task, arch forum thread.
-
Workaround #1 (causes steam to avoid making any calls to
lib32-libgudev
by using a different library altogether)sudo pacman -S lib32-libnm
-
Workaround #2 (forces steam and any other application to always use the new
lib32-libgudev
)sudo pacman -S lib32-libudev0-shim
-
Workaround #3 (use
steam-native-runtime
, which doesn’t have the issue)sudo pacman -S steam-native-runtime
Previous testing threads:
2 Likes
Update to gnome 45 went well, I do miss the green accent at login.
No installed extension issues so far.
Investigating why my Realtek RTL8111/8168/8411 network card downshifts to 100Mbps when this used to work with 1000Mbps
[ 8.673578] r8169 0000:05:00.0 enp5s0: renamed from eth0
[ 9.893749] r8169 0000:05:00.0 enp5s0: Link is Down
[ 26.359744] r8169 0000:05:00.0 enp5s0: Link is Up - 100Mbps/Full (downshifted) - flow control rx/tx
This might have something to do with the unit my isp supplies me with.
sadly linuxxx-zfs is dropped in testing also
I’m getting the following error:
:: Starting full system upgrade...
:: Replace kirigami-addons with extra/kirigami-addons5? [Y/n] Y
warning: kpeoplevcard: local (0.1+r38.32d50a9-1) is newer than extra (0.1-2)
resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: installing kpeople5 (5.111.0-1) breaks dependency 'kpeople' required by kpeoplevcard
:: installing kcontacts5 (5.111.0-1) breaks dependency 'kcontacts' required by kpeoplevcard
-> error installing repo packages
@gothicVI you may want to update without kpeoplevcard and reinstall it if needed:
sudo pacman -Rdd kpeoplevcard
sudo pacman -Syu
sudo pacman -S kpeoplevcard
3 Likes
i get these errors
oct. 21 14:06:32 gvfsd-trash[1269]: GFileInfo created without standard::name
oct. 21 14:06:32 gvfsd-trash[1269]: file ../glib/gio/gfileinfo.c: line 1699 (g_file_info_get_name): should not be reached
oct. 21 14:06:32 gvfsd-trash[1269]: GFileInfo created without standard::name
oct. 21 14:06:32 gvfsd-trash[1269]: file ../glib/gio/gfileinfo.c: line 1699 (g_file_info_get_name): should not be reached
oct. 21 14:06:32 gvfsd-trash[1269]: GFileInfo created without standard::name
oct. 21 14:06:32 gvfsd-trash[1269]: file ../glib/gio/gfileinfo.c: line 1699 (g_file_info_get_name): should not be reached
oct. 21 14:06:32 gvfsd-trash[1269]: GFileInfo created without standard::name
oct. 21 14:06:32 gvfsd-trash[1269]: file ../glib/gio/gfileinfo.c: line 1699 (g_file_info_get_name): should not be reached
just for 4 files in trash → empty
new microcode AMD Zen coming
Had the same thing happen on unstable
.kpeoplevcard 0.1+r38.32d50a9-1
was built by Manjaro’s @oberon and the newer 0.1-2
coming from arch doesn’t have a higher version number (due to disadvantageous revision naming on the older Manjaro package).
Simply allow to downgrade to update:
$ sudo pacman -Syuu
5 Likes
ZFS extramodules; i.e.,
linuxXX-zfs
, have been dropped from the repos. There have been recent difficulties building them and no one on the Manjaro Team uses ZFS.Please install
zfs-dkms
instead. You will to need to manually remove the old 2.1.13 extramodule package(s) first to install the new 2.2.0 packages; i.e., withlinux61
:sudo pacman -R linux61-zfs && sudo pacman -Syu zfs-dkms
Have you tried using r8168 driver instead of r8169 driver ?
Yes, thanks for the reminder, there where some post regarding that particular chip a few announcements back.
Summary
System:
Kernel: 6.5.8-1-MANJARO
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: ASRock driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
port: f000 bus-ID: 05:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp5s0 state: up speed: 100 Mbps duplex: full mac: <filter>
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: ASRock driver: r8168 v: 8.052.01-NAPI modules: r8169 pcie: gen: 1
speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 05:00.0 chip-ID: 10ec:8168
class-ID: 0200
IF: enp5s0 state: up speed: 100 Mbps duplex: full mac: <filter>
When testing and finding nothing, also tried lts kernel just to check & no change.
After reboot to 6.5:
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: ASRock driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
port: f000 bus-ID: 05:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
[ 9.026649] r8169 0000:05:00.0 enp5s0: renamed from eth0
[ 10.156803] r8169 0000:05:00.0 enp5s0: Link is Down
[ 22.623627] r8169 0000:05:00.0 enp5s0: Link is Up - 1Gbps/Full - flow control rx/tx
It’s a kind of magic, won’t dwell on it, was planning to reset the ISP box next…
I had to allow downgrade of package in order to apply the update.
Correct, thank you.
This git package was pushed to extra instead of kde-unstable by accident. Please just ‘downgrade’ to the stable version.
pacman -S manjaro-settings-manager okular pamac-tray-icon-plasma sddm-breath-theme
resolving dependencies...
warning: cannot resolve "kitemmodels", a dependency of "manjaro-settings-manager"
warning: cannot resolve "kauth", a dependency of "manjaro-settings-manager"
warning: cannot resolve "kcoreaddons", a dependency of "manjaro-settings-manager"
warning: cannot resolve "kpty", a dependency of "okular"
warning: cannot resolve "kactivities", a dependency of "okular"
warning: cannot resolve "threadweaver", a dependency of "okular"
warning: cannot resolve "kparts", a dependency of "okular"
warning: cannot resolve "knotifications", a dependency of "pamac-tray-icon-plasma"
:: The following packages cannot be upgraded due to unresolvable dependencies:
manjaro-settings-manager okular pamac-tray-icon-plasma
:: Do you want to skip the above packages for this upgrade? [y/N]
error: failed to prepare transaction (could not satisfy dependencies)
:: unable to satisfy dependency 'kitemmodels' required by manjaro-settings-manager
:: unable to satisfy dependency 'kauth' required by manjaro-settings-manager
:: unable to satisfy dependency 'kcoreaddons' required by manjaro-settings-manager
:: unable to satisfy dependency 'kpty' required by okular
:: unable to satisfy dependency 'kactivities' required by okular
:: unable to satisfy dependency 'threadweaver' required by okular
:: unable to satisfy dependency 'kparts' required by okular
:: unable to satisfy dependency 'knotifications' required by pamac-tray-icon-plasma
A post was merged into an existing topic: [ARM Testing Update] 2023-10-21 – Kernels, PipeWire, KDE Gear & Frameworks, Thunderbird
Can you maybe put the proper package back in Testing repo then?
@ivanich Maybe properly update your system before trying to do what you’re trying to do (what are you doing!?).
@omano pacman -Suy is what I initially did, but the above packages conflicted so I removed them and then did usual upgrade with Suy, so it’s not a user error if you meant that.
@ivanich thx for reporting. seems KDE Framework 5.111.0 on Arch removed the provides lines, hence all our overlay packages need to be adjusted for the new renaming of those.
You probably should have posted that then instead of removing packages. Weird that nobody had issues with these packages but you. Also, since couple update at least we have knotifications5
, kactivities5
, and so on. Packages got renamed before, didn’t you get these renamed packages? Or did you refuse to replace these packages in previous updates?