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-02
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:
After reboot, instead logging in to Plasma Wayland (as it was set since long, long time ago), system automatically logged in to X11 session.
As usual, I had issues with finding the SDDM autologin option in KDE settings, but I was able to find it by search and it turned out that autologin was turned off and my kdewallet password was deleted. So basically, my session configs were wiped out by this update.
I changed the settings back to my previous ones (wayland automatic login, kdewallet with empty password so it would be opened automatically) and after reboot it works as it should.
Feel free to use whatever you comfortable with. We’ll stay on X11 by default for several months (half of a year maybe?) and then switch as well I think.
“We’ll break some things adopting a new technology because not doing so is “so backwards”. If you want to un-break them switch back to the working technology.”
X11 bugs are no longer fixed, and KDE team added and fixed many things in Plasma 6 only for Wayland, plus the experience on Wayland is much faster and smoother, especially on intel iGPUs.
Well, that was possibly an exaggeration on my part, but when I saw the SDDM settings defaulted to “no autologin” (weirdly, it autologged after reboot), didn’t remember the type of session, I assumed that the config was gone or defaulted.
I only noticed the changed, because I don’t have scaling on X11, because I don’t use it, so everything became tiny, so my first thought was, what session am I on. Checked the KDE info and it was X11, which it shouldn’t be based on my configs.
Anyway, I minor issue, but still a surprise.
I think that Manjaro don’t expect how many KDE users switched to Wayland already. I did a year ago, still being on hybrid setup with Nvidia - it worked well, since the desktop was rendered by Intel anyway. Now I’m on AMD laptop, so it also works as it supposes to do.
This is bad news for all Intel users. At least I would expect a small explanation in the update announcement how to stick to Wayland after updating.
Also, we are talking about testing branch, not stable. Shouldn’t we focussed here on bug fixing of latest technolgy? If only Nvidia is affected why not helping those how to stick to X11?
Again, is this really relevant for testing branch? I could understand this for stable branch.
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-02
