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
Notable Package Updates
Kernels
umu-launcher 1.1.4
python
haskell
Additional Info
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:
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.
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.
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
Wayland Plasma: 6.11 kernel working fine, 6.12 freeze before showing GUI.
stu 18 13:19:07 amiga-forever sddm[1801]: Failed to read display number from pipe
stu 18 13:19:09 amiga-forever sddm[1801]: Failed to read display number from pipe
stu 18 13:19:11 amiga-forever sddm[1801]: Failed to read display number from pipe
stu 18 13:19:11 amiga-forever sddm[1801]: Could not start Display server on vt 2
stu 18 13:20:35 amiga-forever dbus-broker-launch[1440]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
Same here. On 6.12 kernel + plasma wayland, the external display is not detected and defaults to builtin. I’m on a laptop with integrated Intel graphics and discreet Nvidia graphics card if that makes a difference.
Same problem with 6.12, that is, the computer hangs before showing the GUI, but works with 6.11 (i am using x11). Two monitor configuration. A switch to sddm maldives theme (that solves the login problem with two monitors) does not help here.
The sddm login problem seems to be related to an error in Qt 6.8.0 (and has already been solved in the upcoming Qt. 6.8.2). Is this error, which seems due to a failure to correctly identify monitors, related?
I don’t think it’s related to the sddm problem directly, I see a kernel stacktrace in the logs, which indicates some problem while loading the nvidia driver:
$ journalctl --no-hostname --boot -1 --dmesg
[...]
Nov 18 21:15:34 kernel: ------------[ cut here ]------------
Nov 18 21:15:34 kernel: WARNING: CPU: 12 PID: 1069 at drivers/gpu/drm/drm_file.c:312 drm_open_helper+0x134/0x150
Nov 18 21:15:34 kernel: Modules linked in: qrtr snd_usb_audio snd_usbmidi_lib snd_ump snd_rawmidi snd_seq_device mc mousedev joydev nls_iso8859_1 vfat fat amd_atl intel_rapl_msr intel_rapl_common snd_hda_codec_realtek snd_hda_codec_generic snd_hda_scodec_component snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi kvm_amd snd_hda_codec snd_hda_core kvm eeepc_wmi snd_hwdep spd5118 crct10dif_pclmul asus_wmi snd_pcm polyval_clmulni r8169 polyval_generic platform_profile snd_timer sp5100_tco i8042 ghash_clmulni_intel realtek sparse_keymap snd mdio_devres sha1_ssse3 serio soundcore libphy rapl rfkill i2c_piix4 ccp k10temp pcspkr i2c_smbus wmi_bmof gpio_amdpt gpio_generic mac_hid uinput i2c_dev sg crypto_user dm_mod loop nfnetlink ip_tables x_tables nvidia_uvm(POE) nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) hid_generic ext4 crc32c_generic crc16 mbcache jbd2 crc32_pclmul crc32c_intel sha512_ssse3 sha256_ssse3 aesni_intel gf128mul nvme crypto_simd cryptd nvme_core drm_ttm_helper sr_mod usbhid cdrom ttm video
Nov 18 21:15:34 kernel: nvme_auth wmi
Nov 18 21:15:34 kernel: CPU: 12 UID: 0 PID: 1069 Comm: systemd-logind Tainted: P OE 6.12.0-1-MANJARO #1 32dc06bea0fd7130d8be952d6bb18de76389ab19
Nov 18 21:15:34 kernel: Tainted: [P]=PROPRIETARY_MODULE, [O]=OOT_MODULE, [E]=UNSIGNED_MODULE
Nov 18 21:15:34 kernel: Hardware name: PCSpecialist Amd Am5/PRIME X670-P, BIOS 3024 08/02/2024
Nov 18 21:15:34 kernel: RIP: 0010:drm_open_helper+0x134/0x150
Nov 18 21:15:34 kernel: Code: 5d 41 5c e9 d9 12 79 00 48 89 df e8 96 92 fe ff 85 c0 0f 84 7a ff ff ff 48 89 df 89 44 24 04 e8 22 fa ff ff 8b 44 24 04 eb d1 <0f> 0b b8 ea ff ff ff eb c8 b8 ea ff ff ff eb c1 b8 f0 ff ff ff eb
Nov 18 21:15:34 kernel: RSP: 0018:ffff9f2682377850 EFLAGS: 00010246
Nov 18 21:15:34 kernel: RAX: ffffffffc056e360 RBX: ffff8edb767761a8 RCX: 0000000000000000
Nov 18 21:15:34 kernel: RDX: ffff8edb5b238000 RSI: ffff8edb767761a8 RDI: ffff8edb5e5bfd40
Nov 18 21:15:34 kernel: RBP: ffff8edb5e5bfd40 R08: 0000000000000800 R09: ffff8edb40269ad0
Nov 18 21:15:34 kernel: R10: 00000000000000e2 R11: 0000000000000002 R12: ffff8edb5e712000
Nov 18 21:15:34 kernel: R13: ffffffffc056e360 R14: 00000000ffffffed R15: ffff9f2682377b3c
Nov 18 21:15:34 kernel: FS: 00007819e4584900(0000) GS:ffff8ee29da00000(0000) knlGS:0000000000000000
Nov 18 21:15:34 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Nov 18 21:15:34 kernel: CR2: 00007819e47f86f0 CR3: 000000010aba2000 CR4: 0000000000f50ef0
Nov 18 21:15:34 kernel: PKRU: 55555554
Nov 18 21:15:34 kernel: Call Trace:
Nov 18 21:15:34 kernel: <TASK>
Nov 18 21:15:34 kernel: ? drm_open_helper+0x134/0x150
Nov 18 21:15:34 kernel: ? __warn.cold+0x93/0xf6
Nov 18 21:15:34 kernel: ? drm_open_helper+0x134/0x150
Nov 18 21:15:34 kernel: ? report_bug+0xff/0x140
Nov 18 21:15:34 kernel: ? handle_bug+0x58/0x90
Nov 18 21:15:34 kernel: ? exc_invalid_op+0x17/0x70
Nov 18 21:15:34 kernel: ? asm_exc_invalid_op+0x1a/0x20
Nov 18 21:15:34 kernel: ? drm_open_helper+0x134/0x150
Nov 18 21:15:34 kernel: ? srso_alias_return_thunk+0x5/0xfbef5
Nov 18 21:15:34 kernel: drm_open+0x73/0x110
Nov 18 21:15:34 kernel: drm_stub_open+0x9b/0xd0
Nov 18 21:15:34 kernel: chrdev_open+0xb0/0x230
Nov 18 21:15:34 kernel: ? __pfx_chrdev_open+0x10/0x10
Nov 18 21:15:34 kernel: do_dentry_open+0x14c/0x4a0
Nov 18 21:15:34 kernel: vfs_open+0x2e/0xe0
Nov 18 21:15:34 kernel: path_openat+0x82e/0x12e0
Nov 18 21:15:34 kernel: ? __memcg_slab_post_alloc_hook+0x211/0x3a0
Nov 18 21:15:34 kernel: ? seq_open+0x2b/0x70
Nov 18 21:15:34 kernel: ? srso_alias_return_thunk+0x5/0xfbef5
Nov 18 21:15:34 kernel: ? kmem_cache_alloc_noprof+0x2c5/0x2f0
Nov 18 21:15:34 kernel: do_filp_open+0xc4/0x170
Nov 18 21:15:34 kernel: do_sys_openat2+0xae/0xe0
Nov 18 21:15:34 kernel: __x64_sys_openat+0x55/0xa0
Nov 18 21:15:34 kernel: do_syscall_64+0x82/0x190
Nov 18 21:15:34 kernel: ? srso_alias_return_thunk+0x5/0xfbef5
Nov 18 21:15:34 kernel: ? path_lookupat+0x96/0x1a0
Nov 18 21:15:34 kernel: ? srso_alias_return_thunk+0x5/0xfbef5
Nov 18 21:15:34 kernel: ? filename_lookup+0xde/0x1d0
Nov 18 21:15:34 kernel: ? srso_alias_return_thunk+0x5/0xfbef5
Nov 18 21:15:34 kernel: ? __kmalloc_cache_noprof+0x11c/0x310
Nov 18 21:15:34 kernel: ? srso_alias_return_thunk+0x5/0xfbef5
Nov 18 21:15:34 kernel: ? __check_object_size+0x1f8/0x210
Nov 18 21:15:34 kernel: ? srso_alias_return_thunk+0x5/0xfbef5
Nov 18 21:15:34 kernel: ? mntput_no_expire+0x4a/0x260
Nov 18 21:15:34 kernel: ? srso_alias_return_thunk+0x5/0xfbef5
Nov 18 21:15:34 kernel: ? do_readlinkat+0xc5/0x180
Nov 18 21:15:34 kernel: ? srso_alias_return_thunk+0x5/0xfbef5
Nov 18 21:15:34 kernel: ? syscall_exit_to_user_mode+0x37/0x1c0
Nov 18 21:15:34 kernel: ? srso_alias_return_thunk+0x5/0xfbef5
Nov 18 21:15:34 kernel: ? do_syscall_64+0x8e/0x190
Nov 18 21:15:34 kernel: ? srso_alias_return_thunk+0x5/0xfbef5
Nov 18 21:15:34 kernel: ? do_syscall_64+0x8e/0x190
Nov 18 21:15:34 kernel: ? srso_alias_return_thunk+0x5/0xfbef5
Nov 18 21:15:34 kernel: ? srso_alias_return_thunk+0x5/0xfbef5
Nov 18 21:15:34 kernel: ? syscall_exit_to_user_mode+0x37/0x1c0
Nov 18 21:15:34 kernel: ? srso_alias_return_thunk+0x5/0xfbef5
Nov 18 21:15:34 kernel: ? do_syscall_64+0x8e/0x190
Nov 18 21:15:34 kernel: ? srso_alias_return_thunk+0x5/0xfbef5
Nov 18 21:15:34 kernel: ? __memcg_slab_free_hook+0xf7/0x140
Nov 18 21:15:34 kernel: ? srso_alias_return_thunk+0x5/0xfbef5
Nov 18 21:15:34 kernel: ? kmem_cache_free+0x3fa/0x450
Nov 18 21:15:34 kernel: ? srso_alias_return_thunk+0x5/0xfbef5
Nov 18 21:15:34 kernel: ? srso_alias_return_thunk+0x5/0xfbef5
Nov 18 21:15:34 kernel: ? syscall_exit_to_user_mode+0x37/0x1c0
Nov 18 21:15:34 kernel: ? srso_alias_return_thunk+0x5/0xfbef5
Nov 18 21:15:34 kernel: ? do_syscall_64+0x8e/0x190
Nov 18 21:15:34 kernel: ? srso_alias_return_thunk+0x5/0xfbef5
Nov 18 21:15:34 kernel: ? syscall_exit_to_user_mode+0x37/0x1c0
Nov 18 21:15:34 kernel: ? srso_alias_return_thunk+0x5/0xfbef5
Nov 18 21:15:34 kernel: ? do_syscall_64+0x8e/0x190
Nov 18 21:15:34 kernel: ? srso_alias_return_thunk+0x5/0xfbef5
Nov 18 21:15:34 kernel: ? do_syscall_64+0x8e/0x190
Nov 18 21:15:34 kernel: ? srso_alias_return_thunk+0x5/0xfbef5
Nov 18 21:15:34 kernel: entry_SYSCALL_64_after_hwframe+0x76/0x7e
Nov 18 21:15:34 kernel: RIP: 0033:0x7819e471a2e3
Nov 18 21:15:34 kernel: Code: 83 e2 40 75 52 89 f0 f7 d0 a9 00 00 41 00 74 47 80 3d 90 3d 0e 00 00 74 62 89 da 4c 89 e6 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 0f 87 81 00 00 00 48 8b 55 b8 64 48 2b 14 25 28
Nov 18 21:15:34 kernel: RSP: 002b:00007ffe78772ad0 EFLAGS: 00000202 ORIG_RAX: 0000000000000101
Nov 18 21:15:34 kernel: RAX: ffffffffffffffda RBX: 0000000000080902 RCX: 00007819e471a2e3
Nov 18 21:15:34 kernel: RDX: 0000000000080902 RSI: 00006099208f4110 RDI: 00000000ffffff9c
Nov 18 21:15:34 kernel: RBP: 00007ffe78772b40 R08: 0000000000000000 R09: 0000000000000020
Nov 18 21:15:34 kernel: R10: 0000000000000000 R11: 0000000000000202 R12: 00006099208f4110
Nov 18 21:15:34 kernel: R13: 0000000000000001 R14: 0000000000000008 R15: 0000000000000001
Nov 18 21:15:34 kernel: </TASK>
Nov 18 21:15:34 kernel: ---[ end trace 0000000000000000 ]---
Also, for me the sddm login works with the newer themes (breeze, breath, …) when fully switching sddm to wayland, as described in the arch wiki:
/etc/sddm.conf.d/10-wayland.conf:
With 6.12 as a kernel, I see some graphical fragments/artefacts - especially in firefox. Seems rather like an upstream issue, but I wanted to mention it here. On 6.11 I have no issues.
Gnome, Wayland, Amd Laptop (GPU, mesa drivers).
I can post more if required; I am just stressed job-wise, so might take some time.
I’m late reporting a regression introduced with 6.12rc7 but i’ve needed long for sorting out the root case of the problem…I first thought its a kernel regression and the kernel bisect costs me a few days before I recognized that it’s a specific problem of the manjaro kernel.
The patches:
are killing the capacitive touchbar and keyboard backlight of my Dell XPS13 9350 (2024 lunar lake version) after the first suspend.
Removing this patches from the kernel build resolves my Problems.
With Kernel 6.12 I can no longer start my Virtual Machines. I get the following error message (although I did not activate AMD-V in the Processor tab and the same setting works in Kernel 6.10):
Blockquote
VirtualBox can’t enable the AMD-V extension. Please disable the KVM kernel extension, recompile your kernel and reboot (VERR_SVM_IN_USE).
Switched to testing branch, updated using TTY, in general no problems, in the morning I switched to kernel 6.12 (rebooted the laptop after). A few minutes ago I noticed that some new updates are available and this is the output when I tried to yay it:
> yay
:: Synchronizing package databases...
core is up to date
extra is up to date
multilib is up to date
:: Searching AUR for updates...
:: Searching databases for updates...
-> Packages not in AUR: electron33-bin
:: 6 packages to upgrade/install.
6 extra/libxnvctrl 550.127.05-1 -> 550.135-1
5 extra/linux611-nvidia 550.127.05-5 -> 550.135-1
4 extra/linux612-nvidia 550.127.05-2 -> 550.135-1
3 extra/mhwd-nvidia 550.127.05-1 -> 550.135-1
2 extra/nvidia-settings 550.127.05-1 -> 550.135-1
1 extra/nvidia-utils 550.127.05-1 -> 550.135-1
==> Packages to exclude: (eg: "1 2 3", "1-3", "^4" or repo name)
-> Excluding packages may cause partial upgrades and break systems
==>
Sync Explicit (5): linux611-nvidia-550.135-1, linux612-nvidia-550.135-1, nvidia-settings-550.135-1, nvidia-utils-550.135-1, libxnvctrl-550.135-1
Sync Dependency (1): mhwd-nvidia-550.135-1
:: Synchronizing package databases...
core is up to date
extra is up to date
multilib is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: installing nvidia-utils (550.135-1) breaks dependency 'nvidia-utils=550.127.05' required by lib32-nvidia-utils
-> error installing repo packages
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-11-18