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.
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.
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”.
KDE Session auto login can't be re-enabled for X11
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
MPV crashes on a Meteorlake system when trying to use hardware acceleration.
[vd] Looking at hwdec h264-vaapi...
[vo/gpu] Loading hwdec drivers for format: 'vaapi'
[vo/gpu] Loading hwdec driver 'vaapi'
[vo/gpu/vaapi] Using EGL dmabuf interop via GL_EXT_EGL_image_storage
[vo/gpu/vaapi] Trying to open a x11 VA display...
[vo/gpu/vaapi] Trying to open a wayland VA display...
[vo/gpu/vaapi/vaapi] libva: VA-API version 1.22.0
[vo/gpu/vaapi/vaapi] libva: Trying to open /usr/lib/dri/iHD_drv_video.so
[vo/gpu/vaapi/vaapi] libva: Found init function __vaDriverInit_1_22
[vo/gpu/vaapi/vaapi] libva: va_openDriver() returns 0
[vo/gpu/vaapi/vaapi] Initialized VAAPI: version 1.22
[vo/gpu/vaapi] Going to probe surface formats (may log bogus errors)...
[statusline] AV: 00:00:11 / 02:07:46 (0%) A-V: 0.000zsh: segmentation fault (core dumped) mpv -v RO.mkv
dmesg
74.383331] vo[4364]: segfault at 779352204000 ip 0000779371790907 sp 000077934a9feab8 error 7 in libc.so.6[16c907,779371648000+171000] likely on CPU 3 (core 12, socket 0)
[ 74.383341] Code: 3e 19 08 00 01 74 9c 83 f9 c0 0f 87 7e fe ff ff c5 fe 6f 4e 20 48 29 fe 48 83 c7 3f 49 8d 0c 10 48 83 e7 c0 48 01 fe 48 29 f9 <f3> a4 c4 c1 7e 7f 00 c4 c1 7e 7f 48 20 c5 f8 77 c3 0f 1f 84 00 00
wow, I thought last testing update was looking good at 95% smooth/self-fixed; but 100% smooth with 35 voters this time!? kinda feels like stable will be getting an update soon
Hi, I have an issue with sway (1.10) / wayland. There seem to be several issues reported on the swaywm repo Issues · swaywm/sway · GitHub. I downgraded to sway 1.9 and it works again.
The issue is that in a dual monitor setup one monitor is duplicated after one monitor is turned of and on again.