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
Notable Package Updates
Kernels got updated
including new firmwares
Systemd is at 256.1 which brings a lot of new features
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.
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.
The following issue emerged after the Testing update of 2024-06-11 and is still here. It does not dissapear after this very last update. I use KDE Plasma 6.0.5.
My Videocard is rather old Radeon 7750 with 2Gb RAM. Graphic processor VERDE.
Mesa drivers 24.1.1 and 24.2 (git version) does not let me use Wayland session at all. My monitor blinks, the picture is highly distorted and teared off apart, and Manjaro returns back to password and login screen. If I choose X11 session, everything goes OK. What shall I do with this card to make use of Wayland? Shall I just restore some good old Timeshift image, shall I wait for the new mesa driver or what? Any ideas how to make Wayland session work again?
Look for the section that would show where you’re logging in and subsequent Wayland/rendering failures. I wouldn’t expect you to post the whole log, it might even help you troubleshoot it yourself or paste only the necessary section.
THANKS A LOT for advices and step by step instructions!!!
I did not change any settings fo kcmshell6… I have non-free video-driver installed, I suppose. How to remove it? UPDATE: I HAVE NOT non-free video driver!
In journal there are A LOT of red lines concerning wayland session and in particular it is stated about the kwin_wayland failure
kwin_wayland[782]: segfault at 0 ip 0000000000000000 sp 00007fffd6e2aeb8 error 14 in k>
june 20 21:12:36 b-manjaro kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6.
kwin_wayland_drm: drmSetClientCap for Atomic Mode Setting failed.
/usr/bin/signal-desktop existe en el sistema de archivos (in english, file exists in the filesystem)
And this happens with almost all the applications. First appears with wine, then with webapps, now signal and tesseract. I think the problem is not with those packages
Don’t do that. If you want to overwrite the files to force the update there are parameters for pacman to do that. if you use a script to execute a sudo rm $everythingYouPassToItcommand it could lead to a disaster possibly.
Search the forum for the error message in english.
I was having this issue yesterday. (And, as an aside, to read more of your log, add | less at the end of your command in your tty shell, and you’ll be able to scroll through in a vim-like interface)
I managed to fix it by blacklisting the simpledrm kernel module and reconfiguring the kernel.
Oddly, after booting into a wayland session, removing the blacklist simpledrm, and reconfiguring the kernel again, I was able to continue logging into my wayland kde 6.0.5 session. Perhaps the successful startup bumped something into place?
Confirm that there is an error related to simpledrm in your logfile though, before going through this exercise. A better fix may be some method of explicitly telling the wayland session which video driver it should use, but I was content after reaching my solution after several hours of tinkering. I am using an nvidia card rather than an AMD card, but the symptoms were exactly as you said.
blacklisting simpledrm was done by sudo cat "blacklist simpledrm" > /etc/modprobe.d/blacklist-simpledrm.conf
followed by sudo mkinitcpio -P
and can be undone by sudo rm /etc/modprobe.d/blacklist-simpledrm.conf
and another sudo mkinitcpio -P
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-06-20