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
You will need to rebuild any AUR Python packages that install files to site-packages or link to libpython3.12.so.
Print a list of of packages that have files in /usr/lib/python3.12/ :
pacman -Qoq /usr/lib/python3.12/
Rebuild them all at once:*
pamac build $(pacman -Qoq /usr/lib/python3.12)
Use rebuild-detector to see if anything else needs to be rebuilt:
checkrebuild
* It’s recommended to clean your build cache first with pamac clean --build-files
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.
We’d like to raise awareness about the rsync security release version 3.4.0-1 as described in our advisory ASA-202501-1.
An attacker only requires anonymous read access to a vulnerable rsync server, such as a public mirror, to execute arbitrary code on the machine the server is running on. Additionally, attackers can take control of an affected server and read/write arbitrary files of any connected client. Sensitive data can be extracted, such as OpenPGP and SSH keys, and malicious code can be executed by overwriting files such as ~/.bashrc or ~/.popt.
We highly advise anyone who runs an rsync daemon or client prior to version 3.4.0-1 to upgrade and reboot their systems immediately. As Arch Linux mirrors are mostly synchronized using rsync, we highly advise any mirror administrator to act immediately, even though the hosted package files themselves are cryptographically signed.
All infrastructure servers and mirrors maintained by Arch Linux have already been updated.
Kernel 6.11 and 4.19 has been marked End Of Life (EOL) on kernel.org
2024-11-27
Partial Cinnamon 6.4 updates
Linux Mint is currently preparing Cinnamon 6.4. The Arch Maintainers went ahead and released some Cinnamon packages which got already tagged 6.4. However, it seems this will break your installation of your Cinnamon desktop. We will monitor the situation and might downgrade to 6.2 packages if needed, before we do a stable branch update. Your feedback regarding Cinnamon overall is highly appreciated.
If pamac GUI options Enable AUR support and Check for updates are enabled, users should check the package list before agreeing to update and un-check AUR packages
2024-11-01
KVM default behavior change on module loading in kernel 6.12
In kernel 6.12, KVM initializes virtualization on module loading by default. This prevents VirtualBox VMs from starting. In order to avoid this, either add kvm.enable_virt_at_load=0 parameter into kernel command line or unload the corresponding kvm_XXX module. Initial support for 6.12 kernel series was added with Virtualbox 7.1.4.
Pamac crashed (or at least the UI did), during the update but everything appears to have updated (I restarted after noting 0% CPU usage). Will update post after updating laptops…
I really don’t care if popups, windows, or whatever this is appears over my rarely used activities. So I would rather not install an extension for something so trivial. I still see text while searching, which would be more of a problem. So the only problem that is apparent, is the pasted warning notification. But I have a feeling these changes may be needed moving forward.
Can anyone confirm?
The wiki post the popup references says to change these environment variables.
Long time stable/testing user here with very little to report during the last, uh, two years? Great job!
This time though there is somethong to write here about; I have the same pop-up as Molski is having, and keyboard layout reverts from Finnish to English at every reboot - but only on one out of my four systems. Haven’t yet had time to debug further.
Based on others’ posts, as I was also not utilizing virtual keyboards, I chose to uninstall Fcitx completely and haven’t experienced problems thereafter. I’m using KDE.
I am not sure it was the update, but I could not add an app to autostart. I ended up creating a launch script for the app, then also creating an appropriate desktop file that autostart requires. It worked after that.
How do I make sure that I have English and Russian so that I can switch
between them as before and the keyboard shortcuts always work?
Easiest way is to uninstall fcitx5. You don’t need an input method to type English and Russian, regular keyboard layouts are absolutely enough. Input methods are relevant for languages that have way more characters than keys (think Chinese or Japanese where you have thousands of different characters that you need to be able to type). Without fcitx5, you can just use Plasma’s keyboard layout configuration and it will remember the layouts.
If you do want to have fcitx5 installed, you need to configure everything in fcitx5 which is rather more complicated than the plasma default because it does so much more. fcitx5 needs to take over the keyboard configuration from Plasma so that switching between languages works with input methods. There is a separate System settings module for fcitx5 (kcm-fcitx5), and you will probably also want kimpanel through which you can setup fcitx5 as well. If you do, you can just ignore the keyboard configuration in Plasma itself; it will not apply.
cwo 2025-02-15 12:27:58 UTC
Then your options are as outlined in comment #12. Either uninstall fcitx5 if you do not actually need it, or use fcitx5 to configure your layouts and switching, not Plasma’s keyboard settings in System Settings > Keyboard. fcitx5 takes over keyboard layouts when it’s started, and replaces it with the ones configured in fcitx5 so that it can function properly. We know this is not optimal, but at the moment you cannot use Plasma’s Keyboard layout configuration if you’re also using fcitx5, it will be regularly overwritten. (You can install kcm-fcitx5 if you want to configure fcitx5 in System Settings, but it will not appear in the Keyboard settings; it’s under Language & Time as “Input Method”).
And if you do use fcitx5, make sure you have fcitx5-configtool installed so you can set up your keyboard layouts. The fcitx5 wiki may also be useful - something I posted in the Stable Updates thread:
It is getting a little confusing having 2 open Testing Update threads, especially as the 2025-02-19 Testing Update included a Plasma bugfix update from 6.3.0 to 6.3.1, which means some issues here may already be fixed. So, I think I will close off this thread.
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.
2025-02-17
