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.
Kernel 6.11 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.
Just an addition to Mesa 24.3.1, which I was already using.
Especially for AMD GPU users. The recent Linux firmware update 20241210, included numerous amdgpu fixes that addressed stability issues with 7800/7900 graphics cards amongst others, see kernel/git/firmware/linux-firmware.git - Repository of firmware blobs for use with the Linux kernel
Without it my system crashed randomly (amdgpu 0000:0d:00.0: [drm] ERROR flip_done timed out) on 24.3.1, no problems with 24.2.8.
Maybe helpful for other amdgpu users, to install linux-firmware-git if crashes happen.
$ blueman-adapters
Traceback (most recent call last):
File "/usr/bin/blueman-adapters", line 43, in <module>
app = blueman_adapters = BluemanAdapters(args.adapter, args.socket_id)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.12/site-packages/blueman/main/Adapter.py", line 57, in __init__
check_bluetooth_status(_("Bluetooth needs to be turned on for the adapter manager to work"), bmexit)
File "/usr/lib/python3.12/site-packages/blueman/Functions.py", line 67, in check_bluetooth_status
if not applet.GetBluetoothStatus():
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.12/site-packages/gi/overrides/Gio.py", line 374, in __call__
result = self.dbus_proxy.call_sync(self.method_name, arg_variant,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
gi.repository.GLib.GError: g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Remote peer disconnected (4)
$
Fehler: Der Vorgang konnte nicht durchgeführt werden (In Konflikt stehende Dateien)
/usr/lib/modules/6.12.4-1-MANJARO/extramodules/Module.symvers existiert in »linux612-acpi_call« und »linux612-virtualbox-host-modules«
/usr/lib/modules/6.13.0-rc2-1-MANJARO/extramodules/Module.symvers existiert in »linux613-acpi_call« und »linux613-virtualbox-host-modules«
blueman-applet[2586]: segfault at 7bed42ae7a29 ip 00007beb0aee8741 sp 00007ffd18455a98 error 4 in libgobject-2.0.so.0.8200.3[3a741,7beb0aeba000+38000] likely on CPU 10 (core 5, socket 0)
I see this on two different machines, one AMD one Intel.
But even more strange - it only happens with certain flatpaks like vscode or chrome. Their dependencies installed fine.
I read in the announcements here that the mesa driver v3.111 is included. Recently there was a serious problem in connection with mesa 3.11 and graphics cards from the RX 570 / 580 series. Is this also to be feared here and should I (RX 580 here) set the mesa 3.11 to ignore for now?
@Scruggs
If your card is running fine, I would skip 24.3.1, especially on KDE as you posted yourself. Actually three patches are in, but I still can manage to crash the gpu in complex scenarios on gnome (e.g. flatpaks which use ffmpeg)