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ā.
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:
Just ran the update as it has been a few hours since any packages were synced to Testing. Successfully rebooted & logged into Plasma without any issues.
I do have one concern regarding a possible typo in /etc/makepkg.conf.d/rust.conf.pacnew.
There is a new, uncommented line: RUSTFLAGS="-Cforce-frame-pointers=yes", which is replacing the commented line #RUSTFLAGS="-C opt-level=3". Should the new line actually be RUSTFLAGS="-C force-frame-pointers=yes", with a space between the -C and force-frame-pointers=yes?
After the update, several GNOME extensions didnāt work. In āExtensionsā, the message shown is (I translate to English from my language) āThe installed version of this extension is incompatible with the current version of GNOME (undefined). This extension has been disabledā
This was the case for Dash to panel, which I use since forever. However, I was able to update the extension from https://extensions.gnome.org
so result :
i ended update , rebuild kernels and reboot in early morning
i get systemd-dump with lightdm-gtk-greeter , screen black with ā-ā on upper top left
solution :
try to end update , nothing
try to restart / start lightdm nothing
then go back to branch Stable and apply pacman -Syyuu
xfce login & nvidia return
Today after switching to testing branch, I tried to upgrade my system but got following error message:
Starting full system upgradeā¦
resolving dependenciesā¦
error: could not open file /var/lib/pacman/local/diffutils-3.10-1/desc: No such file or directory
looking for conflicting packagesā¦
error: failed to prepare transaction (could not satisfy dependencies)
:: installing pacman (7.0.0.r3.g7736133-2.0) breaks dependency ālibalpm.so=14ā required by libpamac
Any help will be highly appreciated.
I just did some searching on the web, and it looks like you are correct. The ā-Cā flag can be used with or without a space. For example, this text on Codegen Options - The rustc book:
Features from multiple -C target-feature options are combined.
Multiple features can be specified in a single option by separating them with commas - -C target-feature=+x,-y.
If some feature is specified more than once with both + and -, then values passed later override values passed earlier.
For example, -C target-feature=+x,-y,+z -Ctarget-feature=-x,+y is equivalent to -C target-feature=-x,+y,+z.
I added the space to my /etc/makepkg.conf.d/rust.conf.pacnew last night when I did my system update. I think Iāll just leave it as-is - it shouldnāt affect anything.
I use āGlobalā mirror, which seems to be fully updated. Libpamac was installed from āextra.ā Reverting to Stable branch does not help, by the way.
If i remember correctly was the culprit paru from aur when i got this same message a while ago from not satisfied dependencies. Uninstalled it for now; and the update went through.
Note that there are three pacnews: 
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-02