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: New Manjaro search engine is available | Blog
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.
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!
2024-05-23
2024-05-18
Shutdown and Wifi Issues on some AMD systems (including framework)
Problem: Kernel updates 6.1.91-1 and 6.6.31-1 break shutdown and suspend/resume on the Framework 16 (Ryzen 7 7840HS, no GPU). Kernel 6.6 also seems to break wifi
Workaround: Downgrading back to 6.1.90-1 and 6.6.30-2 restores functionality. It has also been reported that kernel 6.9 does not have these issues.
No plasma interface with kernel 6.9 + Nvidia gpu + Wayland
If you encouter a black screen with no inteface after login in, it’s probably a problem with simpledrm loading.
To solve it add nvidia_drm.fbdev=1 to /etc/default/grub
in the line begining with GRUB_CMDLINE_LINUX=" .
Verify that you also have nvidia_drm.modeset=1 in the same line.
Then exec sudo update-grub
Also, verify that you have nvidia_drm in /etc/mkinitcpio.conf in the MODULES= or HOOKS= line.
Exemple :
The default KDE Plasma session has been changed to X11
As of Plasma 6, KDE decided to make Wayland the default. However, since issues were discovered, we have reverted the default to X11. Users are free to choose whichever works best for them.
2024-03-23
Konsole font rendering issue
if you use manjaro-zsh-config on Plasma 6,
please check your Font settings in Konsole:
Konsole: Open Settings → Edit Current Profile → Appearance,
click Select Font and select MesloLGS NF Regular.
issues with auto-mount of ntfs filesystem using Kernel 6.8
The kernel changed default ntfs driver from FUSE one to ntfs3.
These two are not fully compatible, mainly as far as mount options go. If you have custom mount options in the fstab (or any other application, such as VeraCrypt) they need to be changed.
Symptoms:
Mount fails with: Device or resource busy
DMesg reports: Can't open blockdev
Solution:
Migrate your mount options. For me the changes were:
This looks like a graphical issue. Mesa got updated, so I suspect it may be at fault here.
Strangely, I can’t repeat this bug on every video (or after FF reboot). At first, I was sure it is a part of the video, then I noticed it on another one, and then I realized that this is a glitch. Never had it before, so that’s something new.
Getting collisions when switching from the latest stable release to the latest testing release:
:: installing icu (75.1-1) breaks dependency 'libicui18n.so=74-64' required by electron27
:: installing icu (75.1-1) breaks dependency 'libicuuc.so=74-64' required by electron27
:: installing icu (75.1-1) breaks dependency 'libicuuc.so=74-64' required by harfbuzz-icu
:: installing icu (75.1-1) breaks dependency 'icu<75' required by manjaro-settings-manager
:: installing icu (75.1-1) breaks dependency 'libicuuc.so=74-64' required by raptor
:: installing icu (75.1-1) breaks dependency 'libicui18n.so=74-64' required by texlive-bin
:: installing icu (75.1-1) breaks dependency 'libicuuc.so=74-64' required by texlive-bin
:: installing icu (75.1-1) breaks dependency 'libicui18n.so=74-64' required by thunderbird
:: installing icu (75.1-1) breaks dependency 'libicuuc.so=74-64' required by thunderbird
In addition, I am getting a dependency resolution issue for lib32-libjpeg-turbo:
warning: cannot resolve "libjpeg-turbo=3.0.3", a dependency of "lib32-libjpeg-turbo"
:: The following package cannot be upgraded due to unresolvable dependencies:
lib32-libjpeg-turbo
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-05-23
