[Testing Update] 2023-12-10 – Kernels, KDE Gear, Pamac 11.7, KDE-git, Python – Testing Updates
Hello community,
Another testing branch update with some usual package updates for you.
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:
- Some Kernels got updated
- we have now more or less a full feature complete support of the ASUS ROG ALLY
- KDE Gear got updated to 23.08.4
- Pamac 11.7.0 got now fully ported to libadwaita 1.4
- it is now fully adaptive and works with phosh
- Gnome 45 is now supported
- Usual KDE-git, 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 Announcements topics are off-topic and will be flagged, moved or removed without warning.
For help with AUR packages, please create a new topic in AUR and a helpful volunteer may be able to assist you.
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.301
- linux54 5.4.263
- linux510 5.10.203
- linux515 5.15.142
- linux61 6.1.66
- linux65 6.5.13 [EOL]
- linux66 6.6.5
- linux67 6.7-rc4
- linux61-rt 6.1.64_rt17
- linux65-rt 6.5.2_rt8
- linux66-rt 6.6.0_rt15
Package Changes (Sun Dec 10 02:04:15 CET 2023)
- testing core x86_64: 8 new and 9 removed package(s)
- testing extra x86_64: 449 new and 448 removed package(s)
- testing kde-unstable x86_64: 233 new and 233 removed package(s)
- 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:
1 Like
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-12-10
2023-11-10
Nvidia 545 drivers might have issues
Due to various issues including non working backlights on some machines, the NVIDIA 545 series feature branch drivers have been downgraded to the 535 series production branch drivers.
If you are having no issues with the 545 series, there is nothing to do. If you are, you can downgrade to the 535 series with pamac update --enable-downgrade or sudo pacman -Syuu.
So far we know about these issues the Nvidia 545 driver series has:
If you experience similar or new issues please run sudo usr/bin/nvidia-bug-report.sh and post either in an already given post or create a new one, including your generated nvidia-bug-report.log.gz for Nvidia to fix the issue: Linux – NVIDIA Developer Forums
Changes in JDK / JRE 21 packages may require manual intervention
2023-11-02 – Frederik Schwan
We are introducing a change in JDK/JRE packages of our distro. This is triggered from the way a JRE is build in modern versions of Java (>9). We are introducing this change in Java 21.
To sum it up instead of having JDK and JRE packages coexist in the same system we will be making them conflict. The JDK variant package includes the runtime environment to execute Java applications so if one needs compilation and runtime of Java they need only the JDK package in the future. If, on the other hand, they need just runtime of Java then JRE (or jre-headless) will work.
This will (potentially) require a manual user action during upgrade:
- If you have both JDK and JRE installed you can manually install the JDK with
pacman -Syu jdk-openjdkand this removes the JRE related packages.- If you have both JRE and JRE-headless you will need to choose one of them and install it manually since they would conflict each other now.
- If you only have one of the JDK/JRE/JRE-headless pacman should resolve dependencies normally and no action is needed.
At the moment this is only valid for the upcoming JDK 21 release.
– Arch Linux – News: Incoming changes in JDK / JRE 21 packages may require manual intervention
2023-10-21
Mechanical HDDs may not spin-down properly on shutdown
There might be a regression introduced with 6.6.0-rc4 which got also backported to 6.1.59 and 6.5.8 Kernels. There is a discussion with the author of the offending patch ongoing here.
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.defsinstead 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_FACTORsetting in/etc/login.defsis currently without effect, until pam implements reading its value [7]. If aYESCRYPT_COST_FACTORhigher (or lower) than the default (5) is needed, it can be set using theroundsoption 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_METHODin/etc/login.defsand does not override the chosen method anymore- changes in the filesystem (>=
2023.09.18) and pambase (>=20230918) packages ensure, thatumaskis set centrally in/etc/login.defsinstead 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] [RFC] Add argon2 backend. by ferivoz · Pull Request #113 · besser82/libxcrypt · GitHub
[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.
Previous testing threads:
After update (probably related to 2023-12-08 update), wifi is no longer working, and causes graphical interface to freeze, also computer is unable to shutdown, I have to use sysrq REISUB to shutdown. Here is output from dmesg:
[ 245.447119] INFO: task kworker/u16:6:91 blocked for more than 122 seconds.
[ 245.447134] Tainted: P OE 6.1.66-1-MANJARO #1
[ 245.447139] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 245.447141] task:kworker/u16:6 state:D stack:0 pid:91 ppid:2 flags:0x00004000
[ 245.447154] Workqueue: events_power_efficient reg_check_chans_work [cfg80211]
[ 245.447308] Call Trace:
[ 245.447311] <TASK>
[ 245.447322] __schedule+0x370/0x12c0
[ 245.447346] schedule+0x5e/0xd0
[ 245.447358] schedule_preempt_disabled+0x15/0x30
[ 245.447371] __mutex_lock.constprop.0+0x39a/0x6a0
[ 245.447380] ? psi_task_switch+0xd6/0x230
[ 245.447395] reg_check_chans_work+0x31/0x5b0 [cfg80211 179e320274a3318060cab106d8259346ff593330]
[ 245.447507] ? __schedule+0x378/0x12c0
[ 245.447521] process_one_work+0x1c7/0x3a0
[ 245.447535] worker_thread+0x51/0x390
[ 245.447546] ? process_one_work+0x3a0/0x3a0
[ 245.447554] kthread+0xde/0x110
[ 245.447563] ? kthread_complete_and_exit+0x20/0x20
[ 245.447572] ret_from_fork+0x22/0x30
[ 245.447590] </TASK>
[ 245.447609] INFO: task NetworkManager:1036 blocked for more than 122 seconds.
[ 245.447615] Tainted: P OE 6.1.66-1-MANJARO #1
[ 245.447618] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 245.447620] task:NetworkManager state:D stack:0 pid:1036 ppid:1 flags:0x00000002
[ 245.447628] Call Trace:
[ 245.447631] <TASK>
[ 245.447634] __schedule+0x370/0x12c0
[ 245.447646] ? asm_sysvec_apic_timer_interrupt+0x1a/0x20
[ 245.447660] schedule+0x5e/0xd0
[ 245.447671] schedule_preempt_disabled+0x15/0x30
[ 245.447681] __mutex_lock.constprop.0+0x39a/0x6a0
[ 245.447689] ? wlc_mac_promisc+0x64/0x69 [wl ef76ec59f46a4298fc950ac0dff1005a1be92cd2]
[ 245.447872] cfg80211_netdev_notifier_call+0x12e/0x4c0 [cfg80211 179e320274a3318060cab106d8259346ff593330]
[ 245.447980] ? update_sd_lb_stats.constprop.0+0x12b/0x940
[ 245.447991] ? sugov_update_single_freq+0x184/0x250
[ 245.448001] ? wlc_iovar_check+0x152/0x21b [wl ef76ec59f46a4298fc950ac0dff1005a1be92cd2]
[ 245.448176] ? wlc_iovar_op+0x1c3/0x1fb [wl ef76ec59f46a4298fc950ac0dff1005a1be92cd2]
[ 245.448343] ? rtnl_is_locked+0x15/0x20
[ 245.448355] ? inetdev_event+0x3d/0x620
[ 245.448366] raw_notifier_call_chain+0x48/0x60
[ 245.448380] __dev_close_many+0x5f/0x110
[ 245.448391] __dev_change_flags+0x1a6/0x240
[ 245.448399] dev_change_flags+0x26/0x60
[ 245.448406] do_setlink+0x37a/0x1240
[ 245.448415] ? __nla_validate_parse+0x61/0xc20
[ 245.448429] ? update_curr+0x69/0x1e0
[ 245.448445] __rtnl_newlink+0x623/0x9e0
[ 245.448451] ? check_preempt_curr+0x1/0x70
[ 245.448460] ? ttwu_do_wakeup+0x17/0x170
[ 245.448469] ? __kmem_cache_alloc_node+0x1a5/0x2d0
[ 245.448479] rtnl_newlink+0x47/0x70
[ 245.448486] rtnetlink_rcv_msg+0x152/0x3c0
[ 245.448498] ? __kmem_cache_alloc_node+0x1a5/0x2d0
[ 245.448504] ? __alloc_skb+0x8c/0x1a0
[ 245.448511] ? rtnl_calcit.isra.0+0x140/0x140
[ 245.448522] netlink_rcv_skb+0x55/0x100
[ 245.448536] netlink_unicast+0x24e/0x3a0
[ 245.448546] netlink_sendmsg+0x254/0x4b0
[ 245.448557] __sock_sendmsg+0x5f/0x70
[ 245.448564] ____sys_sendmsg+0x26a/0x2e0
[ 245.448571] ? copy_msghdr_from_user+0x7d/0xc0
[ 245.448581] ___sys_sendmsg+0x9a/0xe0
[ 245.448596] __sys_sendmsg+0x7a/0xd0
[ 245.448606] do_syscall_64+0x60/0x90
[ 245.448620] ? syscall_exit_to_user_mode+0x2b/0x40
[ 245.448628] ? do_syscall_64+0x6c/0x90
[ 245.448637] ? syscall_exit_to_user_mode+0x2b/0x40
[ 245.448643] ? do_syscall_64+0x6c/0x90
[ 245.448652] entry_SYSCALL_64_after_hwframe+0x64/0xce
[ 245.448663] RIP: 0033:0x7f8d53e94b3d
[ 245.448698] RSP: 002b:00007ffd34d41100 EFLAGS: 00000293 ORIG_RAX: 000000000000002e
[ 245.448706] RAX: ffffffffffffffda RBX: 0000000000000028 RCX: 00007f8d53e94b3d
[ 245.448711] RDX: 0000000000000000 RSI: 00007ffd34d41140 RDI: 000000000000000d
[ 245.448715] RBP: 00007ffd34d41510 R08: 0000000000000000 R09: 0000000000000000
[ 245.448718] R10: 0000000000000000 R11: 0000000000000293 R12: 000055fdbbb98cb0
[ 245.448722] R13: 0000000000000001 R14: 0000000000000000 R15: 0000000000000000
[ 245.448729] </TASK>
[ 245.448733] INFO: task wpa_supplicant:1080 blocked for more than 122 seconds.
[ 245.448737] Tainted: P OE 6.1.66-1-MANJARO #1
[ 245.448740] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 245.448742] task:wpa_supplicant state:D stack:0 pid:1080 ppid:1 flags:0x00004002
[ 245.448750] Call Trace:
[ 245.448752] <TASK>
[ 245.448756] __schedule+0x370/0x12c0
[ 245.448767] ? asm_sysvec_apic_timer_interrupt+0x1a/0x20
[ 245.448781] schedule+0x5e/0xd0
[ 245.448791] schedule_preempt_disabled+0x15/0x30
[ 245.448801] __mutex_lock.constprop.0+0x39a/0x6a0
[ 245.448809] ? __nla_reserve+0x3c/0x50
[ 245.448819] nl80211_send_iface+0x25b/0x960 [cfg80211 179e320274a3318060cab106d8259346ff593330]
[ 245.448943] ? kmalloc_reserve+0x4b/0xa0
[ 245.448951] ? __alloc_skb+0xde/0x1a0
[ 245.448958] nl80211_get_interface+0x4f/0xa0 [cfg80211 179e320274a3318060cab106d8259346ff593330]
[ 245.449076] genl_family_rcv_msg_doit+0x100/0x160
[ 245.449091] genl_rcv_msg+0x11e/0x250
[ 245.449100] ? nl80211_dump_interface+0x1f0/0x1f0 [cfg80211 179e320274a3318060cab106d8259346ff593330]
[ 245.449216] ? nl80211_send_iface+0x960/0x960 [cfg80211 179e320274a3318060cab106d8259346ff593330]
[ 245.449331] ? genl_family_rcv_msg_doit+0x160/0x160
[ 245.449341] netlink_rcv_skb+0x55/0x100
[ 245.449352] genl_rcv+0x28/0x40
[ 245.449361] netlink_unicast+0x24e/0x3a0
[ 245.449370] netlink_sendmsg+0x254/0x4b0
[ 245.449381] __sock_sendmsg+0x5f/0x70
[ 245.449388] ____sys_sendmsg+0x26a/0x2e0
[ 245.449394] ? copy_msghdr_from_user+0x7d/0xc0
[ 245.449403] ___sys_sendmsg+0x9a/0xe0
[ 245.449417] __sys_sendmsg+0x7a/0xd0
[ 245.449427] do_syscall_64+0x60/0x90
[ 245.449438] ? __sys_setsockopt+0xef/0x1f0
[ 245.449446] ? syscall_exit_to_user_mode+0x2b/0x40
[ 245.449453] ? do_syscall_64+0x6c/0x90
[ 245.449461] ? do_syscall_64+0x6c/0x90
[ 245.449470] entry_SYSCALL_64_after_hwframe+0x64/0xce
[ 245.449480] RIP: 0033:0x7f42c5d30b04
[ 245.449493] RSP: 002b:00007fff78f22678 EFLAGS: 00000202 ORIG_RAX: 000000000000002e
[ 245.449499] RAX: ffffffffffffffda RBX: 0000562211e79d50 RCX: 00007f42c5d30b04
[ 245.449503] RDX: 0000000000000000 RSI: 00007fff78f226b0 RDI: 0000000000000006
[ 245.449507] RBP: 0000562211eef880 R08: 0000000000000004 R09: 0000000000000001
[ 245.449510] R10: 00007fff78f22790 R11: 0000000000000202 R12: 0000562211e79c60
[ 245.449514] R13: 00007fff78f226b0 R14: 00005622109240c0 R15: 00007fff78f22790
[ 245.449521] </TASK>
Wifi model is Broadcom BCM43142, kernel version is 6.1.66-1, driver is linux61-broadcom-wl 6.30.223.271-76. I tried upgrading to kernel 6.6 but same issue happens. I have to downgrade kernel to 6.1.65-1 and linux61-broadcom-wl to 6.30.223.271-75 to have a working system.
Update: linux 6.7.0rc4-8 + linux67-broadcom-wl 6.30.223.271-0.11 is working.
Please do vote in the poll as well, as it stand now., it’s “No issue, everything went smoothly” for 100% of voters.
2 Likes