[Testing Update] 2023-11-10 - Kernels, KDE Gear, NVIDIA, LibreOffice, LXQt, PipeWire, Phosh

Hello community,

Another testing branch update with some usual package updates for you.

image
Get the lastest SoftMaker Office with ChatGPT buillt-in. You will find our Special Offer here!

Recent News:

  • 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!
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:

  • All Kernels got a refresh
  • October Linux Firmware updates
  • Pre-compiled extramodules based on zfs-dkms 2.2.0-2 got readded for 4.19 up to 6.6 regular Manjaro-Kernels
    • please report any issues with those if you have some.
    • as an alternative we recommend to use zfs-dkms directly, which now supports kernels up to 6.6 series
  • KDE Gear 23.08.3 got released
  • changes in JDK / JRE 21 packages
    • see Known Issues below for more info
  • NVIDIA 545.29.02
  • LibreOffice 7.5.8
  • last Qt5 based LXQt release got added 1.4.0
  • Pipewire 0.3.84
  • Phosh 0.33.0
  • Firefox 119.0.1 and Thunderbird 115.4.2
  • Usual KDE-git, Haskell and Python updates

Additional Info

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.297
  • linux54 5.4.259
  • linux510 5.10.199
  • linux515 5.15.137
  • linux61 6.1.60
  • linux65 6.5.9
  • linux66 6.6.0
  • linux61-rt 6.1.59_rt16
  • linux64-rt 6.4.6_rt8
  • linux65-rt 6.5.2_rt8

Package Changes (Mon Oct 30 14:50:11 CET 2023)

  • testing core x86_64: 21 new and 21 removed package(s)
  • testing extra x86_64: 114 new and 112 removed package(s)
  • testing kde-unstable x86_64: 60 new and 58 removed package(s)
  • testing multilib x86_64: 6 new and 6 removed package(s)

A list of all differences you may find 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:

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!

:arrow_right: 2023-11-10

Nvidia 545 drivers might have issues

:information_source: Due to various issues including non working backlights on some machines, the NVIDIA 545 series feature branch drivers have been downgraded to the 535 series production branch drivers.

If you are having no issues with the 545 series, there is nothing to do. If you are, you can downgrade to the 535 series with pamac update --enable-downgrade or sudo pacman -Syuu.

So far we know about these issues the Nvidia 545 driver series has:

If you experience similar or new issues please run sudo usr/bin/nvidia-bug-report.sh and post either in an already given post or create a new one, including your generated nvidia-bug-report.log.gz for Nvidia to fix the issue: Linux - NVIDIA Developer Forums

Changes in JDK / JRE 21 packages may require manual intervention

2023-11-02 - Frederik Schwan

We are introducing a change in JDK/JRE packages of our distro. This is triggered from the way a JRE is build in modern versions of Java (>9). We are introducing this change in Java 21.

To sum it up instead of having JDK and JRE packages coexist in the same system we will be making them conflict. The JDK variant package includes the runtime environment to execute Java applications so if one needs compilation and runtime of Java they need only the JDK package in the future. If, on the other hand, they need just runtime of Java then JRE (or jre-headless) will work.

This will (potentially) require a manual user action during upgrade:

  • If you have both JDK and JRE installed you can manually install the JDK with pacman -Sy jdk-openjdk && pacman -Su and this removes the JRE related packages.
  • If you have both JRE and JRE-headless you will need to choose one of them and install it manually since they would conflict each other now.
  • If you only have one of the JDK/JRE/JRE-headless pacman should resolve dependencies normally and no action is needed.

At the moment this is only valid for the upcoming JDK 21 release.

Arch Linux - News: Incoming changes in JDK / JRE 21 packages may require manual intervention

2023-10-21

Mechanical HDDs may not spin-down properly on shutdown

There might be a regression introduced with 6.6.0-rc4 which got also backported to 6.1.59 and 6.5.8 Kernels. There is a discussion with the author of the offending patch ongoing here.

ZFS package changes

ZFS extramodules; i.e., linuxXX-zfs, have been dropped from the repos. There have been recent difficulties building them and no one on the Manjaro Team uses ZFS.

Please install zfs-dkms instead. You will to need to manually remove the old 2.1.13 extramodule package(s) first to install the new 2.2.0 packages; i.e., with linux61:

sudo pacman -R linux61-zfs && sudo pacman -Syu zfs-dkms
Restarting gnome-shell using Alt+F2 and entering R, causes a crash

FS#79884 : [gnome-shell] Restarting gnome-shell using Alt+F2 and entering R, causes a crash

GNOME Extensions that target older GNOME versions will not work in GNOME 45

It is recommended to remove all third-party extensions before updating, then install the compatible versions after updating and rebooting. All Most extensions in the Manjaro repos are already updated.

2023-10-05

glibc-locales update requires manual intervention

If you had the old glibc-locales package from the extra repo installed, the update to the new core package will need manual intervention:

 sudo pacman -Syu glibc-locales --overwrite /usr/lib/locale/\*/\*

2023-09-27

Changes to default password hashing algorithm and umask settings

2023-09-22 - David Runge

With shadow >= 4.14.0, Arch Linux’s default password hashing algorithm changed from SHA512 to yescrypt [1].

Furthermore, the umask [2] settings are now configured in /etc/login.defs instead of /etc/profile.

This should not require any manual intervention.

Reasons for Yescrypt

The password-based key derivation function (KDF) and password hashing scheme yescrypt has been chosen due to its adoption (readily available in libxcrypt, which is used by pam [3]) and its stronger resilience towards password cracking attempts over SHA512.

Although the winner of the Password Hashing Competition [4] has been argon2, this even more resilient algorithm is not yet available in libxcrypt [5][6].

Configuring yescrypt

The YESCRYPT_COST_FACTOR setting in /etc/login.defs is currently without effect, until pam implements reading its value [7]. If a YESCRYPT_COST_FACTOR higher (or lower) than the default (5) is needed, it can be set using the rounds option of the pam_unix [8] module (i.e. in /etc/pam.d/system-auth).

General list of changes

  • yescrypt is used as default password hashing algorithm, instead of SHA512
  • pam honors the chosen ENCRYPT_METHOD in /etc/login.defs and does not override the chosen method anymore
  • changes in the filesystem (>= 2023.09.18) and pambase (>= 20230918) packages ensure, that umask is set centrally in /etc/login.defs instead of /etc/profile

[1] yescrypt - scalable KDF and password hashing scheme

[2] umask(1p) — Arch manual pages

[3] PAM - ArchWiki

[4] https://www.password-hashing.net/

[5] https://github.com/besser82/libxcrypt/pull/113

[6] Add support for Argon2 by maandree · Pull Request #150 · besser82/libxcrypt · GitHub

[7] pam_unix: Support reading YESCRYPT_COST_FACTOR from /etc/login.defs · Issue #607 · linux-pam/linux-pam · GitHub

[8] pam_unix(8) — Arch manual pages

Arch Linux - News: Changes to default password hashing algorithm and umask settings

2023-09-06

filesystem and bashrc-manjaro pacnews

With the filesystem 2023.09.03-1 and bashrc-manjaro 5.1.016-3 updates there may be pacnews for the following files if you have local modifications:

  • /etc/shells
  • /etc/bash.bashrc

This would be a good time to test @Ste74’s new manjaro-pacnew-checker program. See Check and manage pacnew files for more info.

2023-08-25

ansible-core >= 2.15.3-1 update may require manual intervention

2023-08-19 - Robin Candau

As of ansible-core 2.15.3, upstream moved documentation and examples to a separate dedicated repository (see the related changelogs).
This means that, starting from version 2.15.3 the ansible-core package will stop shipping documentation and a default configuration example under /etc/ansible/ansible.cfg.

Regarding the documentation, it is available online: https://docs.ansible.com/
As for the configuration file, as explained in the wiki, a base config can be generated with the following command:

ansible-config init --disabled > ansible.cfg

After updating from ansible-core <= 2.15.2-1 to >= 2.15.3-1, everyone using a custom global Ansible configuration file stored under /etc/ansible/ansible.cfg will have their configuration saved as a pacsave file.
To restore it, run the following command:

mv /etc/ansible/ansible.cfg.pacsave /etc/ansible/ansible.cfg

Arch Linux - News: ansible-core >= 2.15.3-1 update may require manual intervention

2023-08-04

Possible glibc 2.38 posix_memalign regression

There seems a performance regression of posix_memalign in Glibc-2.38. More info here: 30723 – Poor posix_memalign performance with long free lists

Workarounds:

You can try another malloc like mimalloc or jemalloc as workaround. Install mimalloc and start mpv with:

LD_PRELOAD=/usr/lib/libmimalloc.so mpv

or

LD_PRELOAD=/usr/lib/libjemalloc.so mpv

For folks that dont want to change things too much … an apparent workaround is to set a lowish cache size:

mkdir -p ~/.config/mpv && printf '\ndemuxer-max-bytes=50MiB\ndemuxer-max-back-bytes=25MiB\n' | tee -a ~/.config/mpv/mpv.conf
budgie-desktop >= 10.7.2-6 update requires manual intervention

When upgrading from budgie-desktop 10.7.2-5 to 10.7.2-6, the package mutter43 must be replaced with magpie-wm, which currently depends on mutter. As mutter43 conflicts with mutter, manual intervention is required to complete the upgrade.

First remove mutter43, then immediately perform the upgrade. Do not relog or reboot between these steps.

pacman -Rdd mutter43
pacman -Syu

Previous testing threads:

I had installed jdk-openjdk, jdk-openjdk and jdk-openjdk-headless. pacman -Syu jdk-openjdk didn’t work for me. I had to use pacman -Sy jdk-openjdk to update the jdk and remove both jres. Afterwards I was able to proceed with the update.

9 Likes

had the same issue, but did the answer did not appear to me, before I resolved the issue also myself, but used pacman -S instead (which is more unsecure than your solution…). After that, everything went throguh.

Btw, the new kernel release of linux66 solved an issue I had with my realtek wifi (rtw_8852be). It was a linux (mainline kernel) issue, so no issue with manjaro patches or so.

Same for me. Solved with # pacman -Sy jdk-openjdk then # pacman -Syu

You got it backwards: -S is perfectly fine, -Sy can lead to partial upgrades.

2 Likes

Nvidia 545.29.02 + linux61 or linux66 : no backlight !

$ inxi -G
Graphics:
  Device-1: NVIDIA GM206M [GeForce GTX 965M] driver: nvidia v: 545.29.02
  Display: x11 server: X.Org v: 21.1.9 driver: X: loaded: nvidia
    gpu: nvidia,nvidia-nvswitch resolution: 1920x1080~60Hz
  API: EGL v: 1.5 drivers: nvidia,swrast
    platforms: gbm,x11,surfaceless,device
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 545.29.02
    renderer: NVIDIA GeForce GTX 965M/PCIe/SSE2

Bootlog:

nov. 10 14:00:49 Tuxedo kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  545.29.02  Thu Oct 26 21:21:38 UTC 2023
…
nov. 10 14:00:50 Tuxedo systemd-backlight[448]: nvidia_0: Failed to write system 'brightness' attribute: Invalid argument
…
nov. 10 14:00:50 Tuxedo systemd[1]: Failed to start Load/Save Screen Backlight Brightness of backlight:nvidia_0.
nov. 10 14:00:51 Tuxedo systemd-backlight[595]: nvidia_0: Failed to write system 'brightness' attribute: Invalid argument
$ systemctl status systemd-backlight@backlight\:nvidia_0.service 
× systemd-backlight@backlight:nvidia_0.service - Load/Save Screen Backlight Brightness of bac>
     Loaded: loaded (/usr/lib/systemd/system/systemd-backlight@.service; static)
     Active: failed (Result: exit-code) since Fri 2023-11-10 14:09:09 EAT; 1min 0s ago
       Docs: man:systemd-backlight@.service(8)
    Process: 2384 ExecStart=/usr/lib/systemd/systemd-backlight load backlight:nvidia_0 (code=>
   Main PID: 2384 (code=exited, status=1/FAILURE)
        CPU: 22ms

nov. 10 14:09:09 Tuxedo systemd[1]: Starting Load/Save Screen Backlight Brightness of backlig>
nov. 10 14:09:09 Tuxedo systemd-backlight[2384]: nvidia_0: Failed to write system 'brightness>
nov. 10 14:09:09 Tuxedo systemd[1]: systemd-backlight@backlight:nvidia_0.service: Main proces>
nov. 10 14:09:09 Tuxedo systemd[1]: systemd-backlight@backlight:nvidia_0.service: Failed with>
nov. 10 14:09:09 Tuxedo systemd[1]: Failed to start Load/Save Screen Backlight Brightness of >
nov. 10 14:09:09 Tuxedo systemd[1]: systemd-backlight@backlight:nvidia_0.service: Start reque>
nov. 10 14:09:09 Tuxedo systemd[1]: systemd-backlight@backlight:nvidia_0.service: Failed with>
nov. 10 14:09:09 Tuxedo systemd[1]: Failed to start Load/Save Screen Backlight Brightness of >
lines 1-16/16 (END)
$ LANG=C journalctl -xeu systemd-backlight@backlight:nvidia_0.service
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ The unit systemd-backlight@backlight:nvidia_0.service has entered the 'failed' state with result 'exit-code'.
Nov 10 14:14:46 Tuxedo systemd[1]: Failed to start Load/Save Screen Backlight Brightness of backlight:nvidia_0.
░░ Subject: A start job for unit systemd-backlight@backlight:nvidia_0.service has failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A start job for unit systemd-backlight@backlight:nvidia_0.service has finished with a failure.
░░ 
░░ The job identifier is 3137 and the job result is failed.
Nov 10 14:14:46 Tuxedo systemd[1]: systemd-backlight@backlight:nvidia_0.service: Start request repeated too quickly.
Nov 10 14:14:46 Tuxedo systemd[1]: systemd-backlight@backlight:nvidia_0.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support

trouble on suspend screen / lock screen ,
screen stays black , i have to restart lighdm.service in TTY to get login Xfce

pamac update failed due to changes in JDK/JRE packages

Error: Failed to prepare transaction:
conflicting dependencies:
- jdk-openjdk and jre-openjdk are in conflict

Resolved by installing jdk-openjdk before updating:

pamac install jdk-openjdk --no-upgrade; pamac update --no-aur
1 Like

Upgrading from bleachbit (4.4.2-4) to bleachbit (4.6.0-1) resulted in following errors:

Exception while running operation 'system': 'No closing quotation'
Traceback (most recent call last):
  File "/usr/share/bleachbit/Worker.py", line 345, in run_operations
    for _dummy in self.clean_operation(operation):
  File "/usr/share/bleachbit/Worker.py", line 159, in clean_operation
    for cmd in backends[operation].get_commands(option_id):
  File "/usr/share/bleachbit/Cleaner.py", line 385, in get_commands
    if filename.endswith('.desktop') and Unix.is_broken_xdg_desktop(filename):
                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/share/bleachbit/Unix.py", line 497, in is_broken_xdg_desktop
    if __is_broken_xdg_desktop_application(config, pathname):
       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/share/bleachbit/Unix.py", line 425, in __is_broken_xdg_desktop_application
    execs = shlex.split(config.get('Desktop Entry', 'Exec'))
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/shlex.py", line 315, in split
    return list(lex)
           ^^^^^^^^^
  File "/usr/lib/python3.11/shlex.py", line 300, in __next__
    token = self.get_token()
            ^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/shlex.py", line 109, in get_token
    raw = self.read_token()
          ^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/shlex.py", line 191, in read_token
    raise ValueError("No closing quotation")
ValueError: No closing quotation

Resolved by reverting to previous bleachbit (4.4.2-4) version.


Moderator edit: In the future, please use proper formatting: [HowTo] Post command output and file content as formatted text

Yes. Intervention was required. But it was an easy fix.

The same for me. Had to uninstall, and than update took place via Konsole.

2 Likes

Same backlight problem here with an RTX3070.
And I couldn’t modify the laptop backlight power.

something wrong with Xfce & kernel and nvidia, on logout / login or on screen suspend
try to open new session , very long and screen stay black ,

only way , login TTY and restart lightdm.service

@stephane if you use Nvidia 545 driver series it might be expected to behave that way. Seems it is a bad driver so far …

philm: Seems it is a bad driver so far …

yeah, here problems too:
Falkon is flickering (whole tab and address bar) like hell; so it`s mostly unusable for now. Steam also flickering but not that much, that you can’t use it (but don’t know the stable version; I’m on beta).
Also it happens that the game The Dark Mod has some flickering going on (it’s openGL and but playable).
Then on dxvk side i 'm getting some black stripes (not the white stripes, that would be better :guitar::wink: ) in games likes middle earth, prey, race room (looks pretty funny though, like watching old VHS Cassettes; but not that i recommend; driving more in the vegetable then on the street :oncoming_automobile: :sweat_smile:)
Tested kernel 6.1 / 6.5 and 6.6 still the same issue. My testing suite is on gnome (w/ wayland) so also i disabled all extensions, but…
With x11 i’m getting no black stripes, but also it’s bucking around…
(on my stable kde installation works all fine with nvidia 535 driver)

:information_source: Due to various issues including non working backlights on some machines, the NVIDIA 545 series feature branch drivers have been downgraded to the 535 series production branch drivers.

If you are having no issues with the 545 series, there is nothing to do. If you are, you can downgrade to the 535 series with pamac update --enable-downgrade or sudo pacman -Syuu.

2 Likes