Seems plymouth update wasn’t ready as we thought. We had adopted to Arch changes which leaded to some issues with some of your installs. I’ve created now a new branch to track changes more slowly. Plymouth became installed by default with 23.0 install medias. Before most of you had plymouth only installed manually. Gnome edition might have adopted plymouth earlier. So let the migration be done properly.
- 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!
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 updated Mesa to 23.3.3
- Plymouth got downgraded to 22.02.122-16.1
- you may want to use
sudo pacman -Syuu to downgrade again if you had issues
- Similar to Arch we use now dbus-broker by default.
- For the foreseeable future we will still support the use of dbus-daemon, the previous implementation. You will be asked by your package manager whether to install dbus-broker-units or dbus-daemon-units. We recommend picking the default.
- See also here for more information about that change: rfcs/0025-dbus-broker-default.rst · master · Arch Linux / RFCs · GitLab
- Firefox got updated to 121.0.1 and Thunderbird to 115.6.1
- Usual KDE-git, Haskell and Python updates
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.304
- linux54 5.4.266
- linux510 5.10.206
- linux515 5.15.146
- linux61 6.1.71
- linux65 6.5.13 [EOL]
- linux66 6.6.10
- linux67 6.7.0
- linux61-rt 6.1.70_rt21
- linux65-rt 6.5.2_rt8
- linux66-rt 6.6.10_rt19
Package Changes (Thu Jan 11 01:28:39 CET 2024)
- testing core x86_64: 21 new and 19 removed package(s)
- testing extra x86_64: 1349 new and 1350 removed package(s)
- testing kde-unstable x86_64: 260 new and 260 removed package(s)
- testing multilib x86_64: 12 new and 12 removed package(s)
A list of all package 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:
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!
Making dbus-broker our default D-Bus daemon
2024-01-09 - Jan Alexander Steffens
We are making
dbus-broker our default implementation of D-Bus, for improved performance, reliability and integration with systemd.
For the foreseeable future we will still support the use of
dbus-daemon, the previous implementation. Pacman will ask you whether to install
dbus-daemon-units. We recommend picking the default.
For a more detailed rationale, please see our RFC 25.
– Arch Linux - News: Making dbus-broker our default D-Bus daemon
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 -Sy jdk-openjdk && pacman -Su and 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
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.
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
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.
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/\*/\*
Previous testing threads:
It’s not really a problem.
except Package Details: vivaldi-snapshot-ffmpeg-codecs.aur.
Smooth. Reboot and cold boot back to being smooth.
“You will be asked by your package manager whether to install dbus-broker-units or dbus-daemon-units.” This pop-up was empty (no options, all 3 computers I installed this update on), I just clicked Enter, that apparently installed
dbus-broker-units which I’ll assume is the default.
Kernel 6.7.0 - No WiFi, no reboot (still black screen).
Kernel 6.6.10 - Yes WiFi, no reboot (still black screen).
My CPU - Intel
My GPU - AMD
Do you have Plymouth installed?
Yes, Plymouth is installed. I did not do anything to it, just installed the update.
Hi @Alex24 ,
Downgrade plymouth with
pacman -Syuu as @philm suggest it in the first post and You’ll be good
Wish You well
Thanks! Downgrading Plymouth helped. But it’s not a solution, just a temporary workout.
Disable it by removing splash from /etc/default/grub followed by update-grub to see if that solves the issue with shutdown.
I’m starting now to do a soft migration to more plymouth Arch based way on how plymouth gets installed. This is the first installment on that: [pkg-upd] 22.02.122-16.2 (d992a274) · Commits · Packages / Community / Plymouth · GitLab
@2old4gaming and @Alex24 would be interesting to know if anything breaks.
Hey, thanks for the fast update!
At first, I thought everything went smoothly. But I now realized, that at Kernel 6.7.0 (not 6.6.x) I am not able to suspend on Manjaro Gnome with my Ideapad (Lenovo IdeaPad 5 Pro 14ARH7 (AMD)). The screen turns black and the computer is unresponsive, only a forced shutdown via the power button works then. Is that something I should report to kernel.org?
@philm thanks for the fast reply! I did not use plymouth-encrypt before, so I shouldn’t be affected by the issue afaik. Or do I mix things up? However, I can test the package, but the build hook failed on gitlab - just to let you know:)
Updated. Nothing broken (cold boot or reboot).
The previous best practice was to explicitly purge plymouth, even if installed on a whim, so why is plymouth being auto-installed at all all of a sudden?
mkinitcpio (37.1-2 → 37.2-1) failed to find nvidia extramodules for kernel 6.1.71-1 and 6.6.10-1 when building images for ‘default’ and ‘fallback’:
ERROR: file not found: '/lib/modules/6.6.10-1-MANJARO/extramodules/nvidia-uvm.ko.xz'
ERROR: file not found: '/lib/modules/6.6.10-1-MANJARO/extramodules/nvidia-modeset.ko.xz'
ERROR: file not found: '/lib/modules/6.6.10-1-MANJARO/extramodules/nvidia.ko.xz'
ERROR: file not found: '/lib/modules/6.6.10-1-MANJARO/extramodules/nvidia-drm.ko.xz'
xz: /tmp/mkinitcpio.VQ1GfP/root//lib/modules/6.6.10-1-MANJARO/extramodules/nvidia-uvm.ko.xz: No such file or directory
xz: /tmp/mkinitcpio.VQ1GfP/root//lib/modules/6.6.10-1-MANJARO/extramodules/nvidia-modeset.ko.xz: No such file or directory
xz: /tmp/mkinitcpio.VQ1GfP/root//lib/modules/6.6.10-1-MANJARO/extramodules/nvidia.ko.xz: No such file or directory
xz: /tmp/mkinitcpio.VQ1GfP/root//lib/modules/6.6.10-1-MANJARO/extramodules/nvidia-drm.ko.xz: No such file or directory
Generating module dependencies
Creating gzip-compressed initcpio image: '/boot/initramfs-6.6-x86_64-fallback.img'
WARNING: errors were encountered during the build. The image may not be complete.
and system was unable to boot -
nvidia-persistenced failed to initialize
nvidia-470xx-dkms to replace
linux-nvidia470xx was able to run mkinitcpio without errors and get system boot working
Before anyone asks: If you have no issues with 37.2-1, then there’s nothing to do.