[Stable Update] 2024-07-16 - Kernels, Firefox, Thunderbird, Nvidia, Systemd, LibreOffice

Announcements Stable 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: Get 3 months extra

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

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.317
  • linux54 5.4.279
  • linux510 5.10.221
  • linux515 5.15.162
  • linux61 6.1.98
  • linux66 6.6.39
  • linux68 6.8.12 [EOL]
  • linux69 6.9.9
  • linux610 6.10.0
  • linux61-rt 6.1.83_rt28
  • linux66-rt 6.6.35_rt34
  • linux67-rt 6.7_rt6

Package changes (Sat Jul 13 18:48:34 CEST 2024)

  • stable core x86_64: 84 new and 85 removed package(s)
  • stable extra x86_64: 4445 new and 4642 removed package(s)
  • stable multilib x86_64: 52 new and 52 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:

17 Likes
2

Known issues and solutions

This is a wiki post; please edit as necessary.
Please, consider subscribing to the Stable 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-07-16

2024-07-01

The sshd service needs to be restarted after upgrading to openssh-9.8p1

2024-07-01 - Robin Candau

After upgrading to openssh-9.8p1, the existing SSH daemon will be unable to accept new connections (see Can't login after openssh 9.8p1-1 upgrade, MUST restart sshd (#5) · Issues · Arch Linux / Packaging / Packages / openssh · GitLab).
When upgrading remote hosts, please make sure to restart the sshd service using systemctl try-restart sshd right after upgrading.

We are evaluating the possibility to automatically apply a restart of the sshd service on upgrade in a future release of the openssh-9.8p1 package.

– Arch Linux - News: The sshd service needs to be restarted after upgrading to openssh-9.8p1

Virtual machines using libvirt have no internet if the host uses UFW

This is a known bug. “Workaround” is to change the firewall with firewalld or to disable UFW.
Another easier workaround is to edit /etc/libvirt/network.conf, and add

firewall_backend = "iptables"

2024-05-29

:warning: Linux 6.8 is EOL

Linux 6.8 is EOL and will - at some point - be removed from the repo.

If you use Linux 6.8 and Nvidia or inside a virtual machine, it is of great importance, that you install Linux 6.6 or Linux 6.9 to avoid driver problems.

sudo mhwd-kernel -i linux66

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.

:arrow_right: 2024-05-13

:warning: Linux 6.7 is EOL
Linux 6.7 is EOL and will - at some point - be removed from the repo.

If you use Linux 6.7 and Nvidia or inside a virtual machine, it is of great importance, that you install Linux 6.6 to avoid driver problems.

sudo mhwd-kernel -i linux66
Python interpreter upgrade

If you have a lot of pip/AUR packages to upgrade to Python 3.12, read this.

If you installed python312 from the AUR, you need to uninstall it before running this update.

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.

If you use KDE you better logout of your session and do the update via Pacman or Pamac in tty.

Helper script to reset plasma Manjaro-Plasma-Reset/manjaro-plasma-reset.sh at main - wonky/Manjaro-Plasma-Reset - Codeberg.org @liinux-aarhus
Also I would, before the update:

  • make a Timeshift snapshot if you ain’t got no recent one.
  • ( export content of widgets like your radio stations in Advanced Radio Player or your Podcasts in Kasts or any podcatcher as a backup )
  • make a fresh boot, but before that even:
  • System Settings > Appearance > Global Theme > set to Breath and tick both options for defaults
  • You might go to the hamburger menu in System Settings and look what changes you made away from default by selecting: Highlight Changed Settings and see if you want to make the effort to get back more defaults
  • System Settings > Workspace > Startup and Shutdown: SDDM defaults and Desktop Session: Start with empty session
  • disable all user-installed widgets that are still on your desktop, panels and even lock screen or wallpaper (e.g. Active Blur)
  • Export your custom shortcuts or mouse gestures in SS> Workspace > Shortcuts
  • Reboot, Timeshift snapshot, reboot
  • then do not log in, do the update via tty (CTRL+ALT+F3, same with F2 gets you back)
  • reboot, login, check through System Settings
  • reboot again
  • enjoy 8)

post-install:

  • look for Plasma 6 replacements for your widgets after the install
  • in case you have Github-installed theming: uninstall the KDE5-version of klassy, install the Plasma 6 version of klassy, maybe reinstall lightly

(greetings, @1efaf7d71a8637c6800a , PS: these are just my thoughts; I didn’t do this update yet!)

How to fix `plasma-firewall` error in System Settings GUI when running `ufw`

Open /usr/lib/kde_ufw_plugin_helper.py and change the first line from #!/usr/bin/python3.11 to #!/usr/bin/python3.12. This fixed the issue for me immediately and makes sense since Manjaro is currently on Python 3.12.

Xfce has inconsistent themes for Qt applications

Qt 6 is now default but some apps are still using Qt 5
To restore the look of QT apps after this update

pamac install kvantum-qt5

Manjaro-settings-manager has light theme instead of dark

2024-04-04

DKMS fails for v4l2loopback on 6.8 kernel

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

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-03-06

gnome-keyring: ssh component is not included

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

2024-02-21

plymouth update may cause black screens

With a newer version of plymouth than 22.02.122 you may experience an unbootable system with a black screen. This might be due to not having early KMS enabled. If you have an Nvidia GPU you could set nvidia_drm.modeset=1 nvidia_drm.fbdev=1 to the kernel parameters in your bootloader config to avoid the need of KMS. However, with Wayland around the corner, KMS will be needed.

To “fix” the current problem, we have downgraded plymouth once again to have more time to find a proper solution to migrate most of your installations to a working state with newer plymouth versions.

sudo pacman -Syuu

Those who don’t have issues can enjoy the newer version of plymouth.

Directions for adding kms to your system configuration and how you can help troubleshooting by providing some sysinfo, read more → Black Screen with Plymouth - Cause and Solution

polkit update might remove your local modified config

With polkit 124-1 there were changes made to etc/pam.d/polkit-1. So check if you made local changes to the file. See also: https://www.reddit.com/r/archlinux/comments/19bnj0i/comment/kit2v33/

bashrc-manjaro is now merged into bash
  • Yes, replace bashrc-manjaro with bash
  • Please also compare your:
    /etc/bash.bashrc
    with the generated
    /etc/bash.bashrc.pacsave
    and retrofit all of your customisations as there was no .pacnew file generated.
  • Same goes for /etc/skel/.bashrc
pacman and pacman-contrib changes

pacman-contrib is now split out from pacman. If you have anything installed that depends on pacman-contrib, update (after you finished the Release Update) with:

sudo pacman -Syu pacman-contrib

2024-01-13

Initramfs image can be bigger on 6.7 kernel due to Nvidia GSP Boot firmware

We all known that kernel 6.7 is very feature rich. One of the features is the inclusion of Nvidia’s GSP Boot firmware into Initramfs. However this will increase your image by 150 MB and the fallback image might be 240 MB in size. A way would be to remove kms from mkinitcpio.conf and redo your initramfs images. A discussion regarding that can be found at Arch Gitlab: kms hook increases the initramfs size heavily starting with 6.7 kernel (#238) · Issues · Arch Linux / Mkinitcpio / mkinitcpio · GitLab

To reduce size add fallback_options="-S autodetect -S kms" to /etc/mkinitcpio.d/linux67.preset

Making dbus-broker our default D-Bus daemon

2024-01-09 - Jan Alexander Steffens

We are making dbus-broker our default implementation of D-Bus, for improved performance, reliability and integration with systemd.

For the foreseeable future we will still support the use of dbus-daemon, the previous implementation. Pacman will ask you whether to install dbus-broker-units or dbus-daemon-units. We recommend picking the default.

For a more detailed rationale, please see our RFC 25.

– Arch Linux - News: Making dbus-broker our default D-Bus daemon

In some cases, however it is better to keep the legacy way. Here are some examples: Dbus-broker warnings

Previous stable update threads:

2 Likes
3

Thanks for the update announcement.

Upgrading now, after changing mirrors to ones which actually bother to sync without too much procrastination! I’ll report back after this has finished. :+1:

So far:

error: failed retrieving file 'cuda-12.5.1-1-x86_64.pkg.tar.zst' from manjaro.kurdy.org : HTTP server doesn't seem to support byte ranges. Cannot resume

We’ll see what happens.
———
Upgrade seems to have gone well. Will see what the cuda stuff is all about.

Note I did get a notification after rebooting: New kernel available, please upgrade … but it is up to date? 6.6.39-1-MANJARO

1 Like
4 
nano-syntax-highlighting: local (2020.10.10+10+g1aa64a8-2) is newer than extra (2020.10.10-2)

EDIT:
installed was manjaro (2023) and new is (2024) archlinux, at us to force false downgrade but only after update :unamused:

5

Check with @oberon or @Yochanan why the overlay package got dropped.

6

Was hoping for kde 6.1 but this is good

4 Likes
7

After upgrading, my external screen is not receiving any input and is not visible under the Display options. I’m on a laptop with i7-13700H and Nvidia RTX4050 graphics

8

Can’t perfom update, Pamac gives a conflict error:
Bildschirmfoto vom 2024-07-16 10-17-49

Using sudo pacman -Syyu:

:: Paketdatenbanken werden synchronisiert …
 core                  139,1 KiB   994 KiB/s 00:00 [----------------------] 100%
 extra                   7,9 MiB  15,8 MiB/s 00:01 [----------------------] 100%
 multilib              145,9 KiB   879 KiB/s 00:00 [----------------------] 100%
:: Vollständige Systemaktualisierung wird gestartet …
Abhängigkeiten werden aufgelöst …
Nach in Konflikt stehenden Paketen wird gesucht …
Warnung: removing 'pulseaudio-17.0-3' from target list because it conflicts with 'pipewire-pulse-1:1.2.1-1'
Fehler: Nicht auflösbare Paketkonflikte gefunden
Fehler: Vorgang konnte nicht vorbereitet werden (In Konflikt stehende Abhängigkeiten)
:: paprefs-1.2-2 and pipewire-pulse-1:1.2.1-1 are in conflict

I had to remove paprefs, the update worked fine after that. I dont’t need it anymore, so that’s ok for me.

3 Likes
9

Using manjaro gnome.
Update run well using pamac. But after restart got a black screen. No infos on screen, ESC do nothing, can’t got a terminal using ALT CTRL F2.
Any help appreciated

10

Had the same warning and in addition i could not uninstall nano.
Had to remove nano-syntax-highlighting before i could remove nano itself.

11

Hi,
On the whole, the update went fine. However, on my desktop updating the kernel to 6.10-01 led to my only being able to boot into a black screen -TTY was available and fully functional, but nothing else -I didn’t even see the mouse cursor, much less my SDDM login screen.
I’ve rolled back to the previous kernel, am writing this using the same machine.
No problems at all on my Vexia portablet, which doesn’t have NVidia graphics -so I strongly suspect it’s an issue with kernel support for my GPU (NVIDIA GeForce GT 710 [Discrete]). I’m using video-nvidia-470xx for a driver.

Attaching fastfetch output:

image
image691Ă—560 67.2 KB

I’ve no idea what to do to get kernel 6.10 to run with graphics, so for the time being I’m stuck with my workaround of using an older kernel.

Thanks for any input.

Thanks

12

I guess the nvidia drivers you’re using do not support the newer kernel.
You have 2 options:

  • use an older kernel
  • update the nvidia drivers (ensure they support your GPU)
13

No issue with nano-syntax-highlighting here (it doesn’t get updated), so I guess it’s fixed.

14

No issues. thanks guys.

15

Cheers; I’d kind of expected as much, and I’ve confirmed it by switching to the free driver instead -which is less smooth, however.
Right now I’m running 6.10-01 with the nouveau driver; for non-gaming purposes it seems to be running fine if a tad sluggish with some of my animations. Video playback works.
Still on X11 right now -I’ll be giving Wayland a try in a sec.

–

On Wayland now -Nouveau seems to be working better with Plasma than the proprietary driver did when I last checked out Wayland, and way better than it does with X11.

–
Conclusion: Yes, the issue lies with the compatibility of video-nvidia-470xx with kernel 6.10.0-1 . For the time being, using the free driver or an older kernel seem to be the best workaround.

16

got this error:

intel-oneapi-basekit-2024.1.0.596-3-x86_64 downloading…

checking keyring…

checking package integrity…

error: intel-oneapi-basekit: signature from “Torsten Keßler tpkessler@archlinux.org” is invalid

:: File /var/cache/pacman/pkg/intel-oneapi-basekit-2024.1.0.596-3-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
any advice?

1 Like
17

My Thinkpad T460 had no wifi after rebooting. Fortunately a second reboot cured the problem. (Using latest LTS Kernel 6.6.39-1)

18

During update, I noticed some error when upgrading my plymouth theme:

[ALPM] upgraded plymouth-theme-manjaro-elegant-hidpi (2.0-2 -> 2.0-3)
[ALPM-SCRIPTLET] Theme=manjaro-elegant-hidpi
[ALPM-SCRIPTLET] ==> ERROR: No presets found in /etc/mkinitcpio.d

However, it seems that image were built successfully.

[ALPM] running '90-mkinitcpio-install.hook'...
[ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux66.preset: 'default'
[ALPM-SCRIPTLET] ==> Using default configuration file: '/etc/mkinitcpio.conf'
[ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-6.6-x86_64 -g /boot/initramfs-6.6-x86_64.img
[ALPM-SCRIPTLET] ==> Starting build: '6.6.39-1-MANJARO'
[ALPM-SCRIPTLET]   -> Running build hook: [base]
[ALPM-SCRIPTLET]   -> Running build hook: [udev]
[ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
[ALPM-SCRIPTLET]   -> Running build hook: [microcode]
[ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[ALPM-SCRIPTLET]   -> Running build hook: [kms]
[ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[ALPM-SCRIPTLET]   -> Running build hook: [keymap]
[ALPM-SCRIPTLET]   -> Running build hook: [consolefont]
[ALPM-SCRIPTLET] ==> WARNING: consolefont: no font found in configuration
[ALPM-SCRIPTLET]   -> Running build hook: [block]
[ALPM-SCRIPTLET]   -> Running build hook: [mdadm_udev]
[ALPM-SCRIPTLET] Custom /etc/mdadm.conf file will be used in initramfs for assembling arrays.
[ALPM-SCRIPTLET]   -> Running build hook: [zfs]
[ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[ALPM-SCRIPTLET]   -> Running build hook: [plymouth]
[ALPM-SCRIPTLET]   -> Running build hook: [resume]
[ALPM-SCRIPTLET] ==> Generating module dependencies
[ALPM-SCRIPTLET] ==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.6-x86_64.img'
[ALPM-SCRIPTLET]   -> Early uncompressed CPIO image generation successful
[ALPM-SCRIPTLET] ==> Initcpio image generation successful

After rebooting, the Plymouth theme still appeared as normal. I wonder if this is something I need to worry about.

19

Not all extramodules built for 6.10 kernel. See the errors here: https://github.com/manjaro-kernels/linux610/releases/download/6.10.0-1/linux-6.10.0-1-logs.zip

1 Like
20

Main update went fine, but subsequently I installed the new kernel and it couldn’t use my Ethernet controller. I suspect that’s because of the extramodules failures mentioned by philm.

Rebooted on the old kernel, everything OK. No doubt a new version of 6.10 will arrive before too long.