×

[Testing Update] 2024-11-13 – Kernels, Calamares, MHWD, KDE Gear, Firefox, Thunderbird – Testing Updates

Manjaro

[Testing Update] 2024-11-13 – Kernels, Calamares, MHWD, KDE Gear, Firefox, Thunderbird – Testing Updates


Hello community, here we have another set of package updates.

Current Promotions

Recent News

Previous News
Finding information easier about Manjaro

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
  • Calamares updates
    • we fixed the BTRFS issue we had with a workaround
  • Manjaro Hardware Detection update
    • we removed legacy framebuffer code
    • hardware database is now tagged with YYMMDD version
  • KDE Gear 24.08.3
  • Firefox 132.0.2
  • Thunderbird 128.4.2
  • Opensearch 2.18.0

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:

555 release feedback & discussion – Linux – NVIDIA Developer Forums
550.78 release feedback & discussion thread – Linux – NVIDIA Developer Forums

Python 3.12 info

:information_source: You will need to rebuild any AUR Python packages that install files to site-packages or link to libpython3.11.so. :information_source:

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

:warning: 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.

Get our latest daily developer images now from Github: Plasma, GNOME, XFCE. You can get the latest stable releases of Manjaro from CDN77.

Our current supported kernels

  • linux419 4.19.323
  • linux54 5.4.285
  • linux510 5.10.229
  • linux515 5.15.171
  • linux61 6.1.116
  • linux66 6.6.60
  • linux610 6.10.14 [EOL]
  • linux611 6.11.7
  • linux612 6.12.0-rc7
  • linux61-rt 6.1.112_rt43
  • linux66-rt 6.6.53_rt44
  • linux610-rt 6.10.2_rt14

Package Changes (Wed Nov 13 07:57:24 CET 2024)

  • testing core x86_64: 9 new and 9 removed package(s)
  • testing extra x86_64: 1531 new and 1514 removed package(s)
  • testing multilib x86_64: 10 new and 10 removed package(s)

Overlay Changes

  • testing core x86_64: 28 new and 31 removed package(s)
  • testing extra x86_64: 110 new and 117 removed package(s)

A list of all package changes can be found here

  • No issue, everything went smoothly
  • Yes there was an issue. I was able to resolve it myself.(Please post your solution)
  • Yes i am currently experiencing an issue due to the update. (Please post about it)

Check if your mirror has already synced:



1 Like

Known issues and solutions

This is a wiki post; please edit as necessary.
Please, consider subscribing to the Testing Updates Announcements RSS feed

Please RTFT (Read This Fine Thread) first before reporting the same issues over and over again!

Note: Do not forget to review your .pacnew files:

:arrow_right: 2024-11-13

v86d has been dropped from Manjaro repositories and is no longer required for mhwd

Re: Unstable Update MHWD disussion

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.

More info about that in the Linux mailing list

2024-10-20

Kernel 6.10 has been marked [EOL] on kernel.org

sddm login problems with multiple monitors
  • bug report
  • login only works on secondary monitor
  • switching sddm theme to maldives works around the issue

2024-09-13

:warning: Linux 6.9 is EOL

Linux 6.9 is EOL and has been removed from the repos.

Suggestion is to install latest LTS; i.e.,

sudo mhwd-kernel -i linux66
System freeze on suspend

A feature in systemd 256 freezing a user session when suspending may freeze the system.

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:

[Service]
Environment="SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=false"

– Power management/Suspend and hibernate – ArchWiki

KDE Plasma hangs on Shutdown, Restart and Logout

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

Previous testing threads:

If you use QEMU with EFI emulation (e.g. for Windows guests), Arch has changed UEFI images for virtual servers to 4M version and changed its filename.

Package: edk2-ovmf
See: Remove 2MB images (75700bae) · Commits · Arch Linux / Packaging / Packages / edk2 · GitLab



1 Like

There is a post-upgrade message:

I get this error

error: failed to prepare transaction (could not satisfy dependencies)
:: installing expat (2.6.4-1) breaks dependency ‘expat=2.6.3’ required by lib32-expat



1 Like

Users should be advised to update with pacman and then remove v86d.

Updating with pamac will update v86d from the AUR, but it is no longer needed.



7 Likes

How do you know it’s not needed anymore ?

It was previously required by mhwd, but they removed the dependency and dropped v86d from the Manjaro repos.



3 Likes

When it is listed orphan.

v86d has been dropped from Manjaro repositories and is no longer required for mhwd

Re: Unstable Update MHWD disussion

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

If Check for updates option is not enabled, pamac GUI would only update repository packages

After this update mhwd was not working but no issues with mhwd-kernel or mhwd-gpu

$ mhwd -l
Error: Following directories do not exist:
> /var/lib/mhwd/db/usb
> /var/lib/mhwd/local/usb

Solved by creating directories /var/lib/mhwd/db/usb and /var/lib/mhwd/local/usb

3 posts were split to a new topic: Can’t update due to expat dependency

Would it be possible to make systemd-256.8.1 available (currently in unstable)?
This potentially fixes system resume issues: 2321268 – systemctl freeze hangs when a user-session VM is running, never thaws the user session on system resume

There is no such version. I assume you meant 256.8-1?
You can always switch branches until that arrives in testing if resume is that important for your workflow.



2 Likes

I receive the following errors:

error: failed to commit transaction (conflicting files)
mhwd-db: /var/lib/mhwd/db/pci/graphic_drivers/hybrid-amd-nvidia-470xx-prime/MHWDCONFIG exists in filesystem
mhwd-db: /var/lib/mhwd/db/pci/graphic_drivers/hybrid-amd-nvidia-prime/MHWDCONFIG exists in filesystem
mhwd-db: /var/lib/mhwd/db/pci/graphic_drivers/hybrid-intel-nvidia-390xx-bumblebee/MHWDCONFIG exists in filesystem
mhwd-db: /var/lib/mhwd/db/pci/graphic_drivers/hybrid-intel-nvidia-470xx-prime/MHWDCONFIG exists in filesystem
mhwd-db: /var/lib/mhwd/db/pci/graphic_drivers/hybrid-intel-nvidia-prime/MHWDCONFIG exists in filesystem
mhwd-db: /var/lib/mhwd/db/pci/graphic_drivers/nvidia-390xx/MHWDCONFIG exists in filesystem
mhwd-db: /var/lib/mhwd/db/pci/graphic_drivers/nvidia-470xx/MHWDCONFIG exists in filesystem
mhwd-db: /var/lib/mhwd/db/pci/graphic_drivers/nvidia/MHWDCONFIG exists in filesystem
mhwd-db: /var/lib/mhwd/db/pci/graphic_drivers/video-linux/MHWDCONFIG exists in filesystem
mhwd-db: /var/lib/mhwd/db/pci/graphic_drivers/video-modesetting/MHWDCONFIG exists in filesystem
mhwd-db: /var/lib/mhwd/db/pci/graphic_drivers/video-virtualmachine/MHWDCONFIG exists in filesystem
mhwd-db: /var/lib/mhwd/db/pci/graphic_drivers/xf86-video-rendition/MHWDCONFIG exists in filesystem
mhwd-db: /var/lib/mhwd/db/pci/graphic_drivers/xf86-video-s3/MHWDCONFIG exists in filesystem
mhwd-db: /var/lib/mhwd/db/pci/graphic_drivers/xf86-video-sisusb/MHWDCONFIG exists in filesystem
mhwd-db: /var/lib/mhwd/db/pci/graphic_drivers/xf86-video-vesa/MHWDCONFIG exists in filesystem
mhwd-db: /var/lib/mhwd/db/pci/graphic_drivers/xf86-video-voodoo/MHWDCONFIG exists in filesystem
mhwd-db: /var/lib/mhwd/db/pci/network_drivers/broadcom-wl/MHWDCONFIG exists in filesystem
mhwd-db: /var/lib/mhwd/db/pci/network_drivers/r8168/MHWDCONFIG exists in filesystem
mhwd-db: /var/lib/mhwd/db/pci/network_drivers/rt3562sta/MHWDCONFIG exists in filesystem
mhwd-db: /var/lib/mhwd/db/pci/network_drivers/slmodem/MHWDCONFIG exists in filesystem



Source link