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!
As you might have seen some of our team were able to attend FOSDEM 2023 and the conference proved to be incredibly productive for us. See our blog post for more.
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: News – Manjaro
Nvidia drivers got downgraded to 550.100, therefore update with sudo pacman -Syuu. If you want to stay on the 555 driver series you may either switch to unstable or install nvidia-dkms via: sudo pacman -U https://mirror.easyname.at/manjaro/pool/overlay/nvidia-dkms-555.58.02-1-x86_64.pkg.tar.zst. More info about Nvidia drivers here:
You will need to rebuild any AUR Python packages that install files to site-packages or link to libpython3.11.so.
Print a list of of packages that have files in /usr/lib/python3.11/ :
pacman -Qoq /usr/lib/python3.11/
Rebuild them all at once:*
pamac build $(pacman -Qoq /usr/lib/python3.11)
* Note that if any fail to build, you’ll have to rebuild what’s remaining one or a few at a time.
Use rebuild-detector to see if anything else needs to be rebuilt:
checkrebuild
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.
The issue is most prominent with Nvidia systems but reports exist that it may affect other systems as well.
System freezes for 60 seconds and then wakes back up or hangs after waking up
Since systemd v256, systemd freezes user.slice before sleeping. This process can fail due to kernel bugs, particularly when KVM is in use.[13][14]
Messages in the logs will contain Failed to freeze unit 'user.slice' before sleep. When such an issue occurs, trying to login (start another session) would fail with pam_systemd(process:session): Failed to create session: Job 9876 for unit 'session-6.scope' failed with 'frozen'.
To temporarily revert back to the old behavior, edit systemd-suspend.service, systemd-hibernate.service, systemd-hybrid-sleep.service, and systemd-suspend-then-hibernate.service with the following drop-in:
With KDE Plasma 6.1, the session saving feature can make Plasma hang.
A workaround is to disable it in System settings > Session > Desktop Session, by choosing “Start with an empty session”.
KDE Session auto login can't be re-enabled for X11
Once session auto login for X11 gets disabled, it can’t be re-enabled in settings.
A workaround is to edit the /etc/sddm.conf.d/kde_settings.conf file and replace Session=Plasma (X11) by Session=plasma
2024-08-04
pulseaudio-ctl requires pulseaudio and is not compatible with pipewire
If one is using PipeWire, one will need to remove pulseaudio-ctl if prompted during the update as it’s only compatible with pulseaudio
2024-07-14
Nvidia driver downgrade
Nvidia drivers got downgraded to 550.100, therefore update with sudo pacman -Syuu. If you want to stay on the 555 driver series you may either switch to unstable or install nvidia-dkms via: sudo pacman -U https://mirror.easyname.at/manjaro/pool/overlay/nvidia-dkms-555.58.02-1-x86_64.pkg.tar.zst. More info about Nvidia drivers here:
Note, this was not just a Ruby rebuild, Ruby was upgraded from 3.2.5 to 3.3.5 and people need to rebuild their AUR packages that depend on it.
Compared to the previous update which was from Ruby 3.0 to Ruby 3.2 (from EOL and skipping a version), this bump should be quite safe and straightforward.
But due to how the Ruby gem path works, upgrading means system gems will now be placed in the /usr/lib/ruby/gems/3.3.0 directory (instead of 3.2.0), reason why AUR packages will break as they will still look in the old directory for the old gems, and those will be removed in the update process.
I tried upgrading today and I get the following error:
:: Proceed with installation? [Y/n] y
(102/102) checking keys in keyring [--------------------------------------------------------------] 100%
(102/102) checking package integrity [--------------------------------------------------------------] 100%
(102/102) loading package files [--------------------------------------------------------------] 100%
(102/102) checking for file conflicts [--------------------------------------------------------------] 100%
error: failed to commit transaction (conflicting files)
ruby-erb: /usr/bin/erb.lock exists in filesystem
lolcat: /usr/bin/lolcat.lock exists in filesystem
ruby-debug: /usr/bin/rdbg.lock exists in filesystem
ruby-rake: /usr/bin/rake.lock exists in filesystem
ruby-typeprof: /usr/bin/typeprof.lock exists in filesystem
ruby-bundler: /usr/bin/bundle.lock exists in filesystem
ruby-bundler: /usr/bin/bundler.lock exists in filesystem
ruby-diff-lcs: /usr/bin/htmldiff.lock exists in filesystem
ruby-diff-lcs: /usr/bin/ldiff.lock exists in filesystem
ruby-rspec-core: /usr/bin/rspec.lock exists in filesystem
ruby-term-ansicolor: /usr/bin/term_cdiff.lock exists in filesystem
ruby-term-ansicolor: /usr/bin/term_colortab.lock exists in filesystem
ruby-term-ansicolor: /usr/bin/term_decolor.lock exists in filesystem
ruby-term-ansicolor: /usr/bin/term_display.lock exists in filesystem
ruby-term-ansicolor: /usr/bin/term_mandel.lock exists in filesystem
ruby-term-ansicolor: /usr/bin/term_snow.lock exists in filesystem
Errors occurred, no packages were upgraded.
I understand there is a Ruby upgrade that is part of this update. Are there any specific manual steps to take? Sounds like I need to remove some type of .lock file.
You will need to rebuild any AUR Python packages that install files to site-packages or link to 
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.
2024-10-15