[Testing Update] 2024-05-25 - Mesa 24.0.8, Gitlab 17.01

Announcements Testing Updates
, ,
1

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

Current Promotions

  • Find out all about our current Gaming Laptop the Hero with Manjaro pre-installed from Spain!
  • Protect your personal data, keep yourself safe with Surfshark VPN: 85% OFF + 2 mo. FREE

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: New Manjaro search engine is available | Blog

image

Notable Package Updates

Additional Info

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.314
  • linux54 5.4.276
  • linux510 5.10.217
  • linux515 5.15.159
  • linux61 6.1.91
  • linux66 6.6.31
  • linux68 6.8.10
  • linux69 6.9.1
  • linux61-rt 6.1.83_rt28
  • linux66-rt 6.6.30_rt30
  • linux67-rt 6.7_rt6

Package Changes (Fri May 24 16:26:16 CEST 2024)

  • testing core x86_64: 42 new and 42 removed package(s)
  • testing extra x86_64: 807 new and 800 removed package(s)
  • testing multilib x86_64: 18 new and 18 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)
0 voters

Check if your mirror has already synced:

3 Likes
2

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!

:arrow_right: 2024-05-25

2024-05-18

Shutdown Issues on some AMD systems (including framework)
  • Problem: Kernel updates 6.1.91-1 and 6.6.31-1 break shutdown and suspend/resume on the Framework 16 (Ryzen 7 7840HS, no GPU).
  • Workaround: Downgrading back to 6.1.90-1 and 6.6.30-2 restores functionality. It has also been reported that kernel 6.9 does not have these issues.
  • Issue tracking: framework forums

2024-05-14

No plasma interface with kernel 6.9 + Nvidia gpu + Wayland

If you encouter a black screen with no inteface after login in, it’s probably a problem with simpledrm loading.

To solve it add nvidia_drm.fbdev=1 to /etc/default/grub
in the line begining with GRUB_CMDLINE_LINUX=" .
Verify that you also have nvidia_drm.modeset=1 in the same line.
Then exec sudo update-grub

Also, verify that you have nvidia_drm in /etc/mkinitcpio.conf in the MODULES= or HOOKS= line.
Exemple :

MODULES=(nvidia nvidia_modeset nvidia_uvm nvidia_drm)

If it was not present, then run sudo mkinitcpio -P after adding it.

2024-05-08

Qemu: MacOS is not bootable with 9.0

Due to a bug MacOS is not bootable with 9.0: [9.0.0] qemu breaks mac os vm (#2334) · Issues · QEMU / QEMU · GitLab
Workaround: remove virtio-serial and org.qemu.guest_agent.0 from libvirt XML until bug will be fixed.

2024-05-02

The default KDE Plasma session has been changed to X11

As of Plasma 6, KDE decided to make Wayland the default. However, since issues were discovered, we have reverted the default to X11. Users are free to choose whichever works best for them.

2024-03-23

Konsole font rendering issue

if you use manjaro-zsh-config on Plasma 6,
please check your Font settings in Konsole:

Konsole: Open Settings → Edit Current Profile → Appearance,
click Select Font and select MesloLGS NF Regular.

2024-03-16

Plasma 6 issues with Manjaro themes & tools

Prepare for a Plasma 6 release (#2) · Issues · Release plan / KDE · GitLab

DKMS fails for v4l2loopback on 6.8 kernel

DKMS fails for v4l2loopback on 6.8 kernel (#2) · Issues · Arch Linux / Packaging / Packages / v4l2loopback · GitLab

New version of kvantum does not support QT5 theme

Install new package kvantum-qt5 for QT5 theme support
required for manjaro-settings-manager and audacious

pamac install kvantum-qt5

If Theme shows wrong colors:

cd $HOME; ln -s .profile .xprofile

Manjaro-settings-manager has light theme instead of dark

issues with auto-mount of ntfs filesystem using Kernel 6.8

The kernel changed default ntfs driver from FUSE one to ntfs3.
These two are not fully compatible, mainly as far as mount options go. If you have custom mount options in the fstab (or any other application, such as VeraCrypt) they need to be changed.

Symptoms:
Mount fails with: Device or resource busy
DMesg reports: Can't open blockdev

Solution:
Migrate your mount options. For me the changes were:

  • allow_other → umask=000
  • default_permissions → [drop]
  • user_id=1000 → uid=1000
  • group_id=1000 → gid=1000

2024-02-23

gnome-keyring: ssh component is not included

ssh component is not included (#3) · Issues · Arch Linux / Packaging / Packages / gnome-keyring · GitLab

Previous testing threads:

3

Was the default Plasma session changed again, this time to wayland?
Is this intentional? Last change note I see here is about changing it to X11.

4 
error: glibc-locales: signature from "Frederik Schwan <frederik.schwan@linux.com>" is invalid
:: File /var/cache/pacman/pkg/glibc-locales-2.39+r52+gf8e4623421-1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n]

Removing it and re-downloading presents the same PGP error again.
The update can not be run.

Edit 2 days later…
Seems like Manjaro does not care that they have unsigned packages in their repo.
WARNING WARNING WARNING!!!
The package glibc-locales does NOT HAVE A VALID SIGNATURE IN THE MANJARO REPO!
The package has a valid key on arch stable and works perfectly fine.

Thank you for the suggestion @CGA but removing the package and redownload was obv the first thing I did.
The only “solution” you have is uninstall the package and run the update.
I tried that, and got a new keyring, and after update tried to reinstall the package. It is still invalid with the same GPG error.

1 Like
5

I had the same error with another package the update before this. Rm -rf /var/cache/pacman/pkg/*solved it.

6

No idea if intentional or not but a number of users reported the same issue in the Unstable thread.

7

The update switched me to Wayland when I rebooted. WTF? Maybe because I did a warm reboot? Anyway, back to x11.

8

Since I was already on Wayland, this wasn’t the issue for me, but I have autologin which was disabled, and I had to set it again.

Although I love Plasma, having autologin setting in LOOK section (under SDDM display settings) is a huge mistake. I always have problem to find it, because it’s so illogically placed.

1 Like
9

The plasma-workspace version 6.0.5-0.1 that was pushed intermittently caused browsers not to start anymore when called from the workspace. Tested with both 6.0.5-0 and 6.0.5-1.0 and it works without issue.

11

Odd choice for “notable package update” for a desktop distro - almost nobody will have a gitlab server running on manjaro.

1 Like
12