[Testing Update] 2022-12-04 - Kernels, Systemd, Mesa, GNOME

Hello community,

Another testing branch update with some usual package updates for you. I’ll be in Asia for couple of months, so expect responses and updates at a different time slot as usual.

Recent News:

Notable Package Updates:

  • Some of our Kernels got updated
  • A few Gnome 43.2 updates trickled in
  • Mesa is now maintained by Manjaro and won’t ship with patent encumbered codecs.
  • Systemd got downgraded again to v251.8 due to regressions found in v252 series
  • 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 Announcement topics are off-topic and will be flagged, moved or removed without warning.

Info about GNOME 43

GNOME 43 is here! :partying_face:

New in Manjaro GNOME:

Lonely leftover orphan packages that have been removed from the Arch / Manjaro repositories:

  • adwaita-maia
  • dynamic-wallpaper-editor
  • firefox-gnome-theme-maia
  • gtkhash-nautilus
    (Not compatible with Nautilus 43)
  • manjaro-dynamic-wallpaper
  • manjaro-gdm-tweak
  • nautilus-terminal
    (Not compatible with Nautilus 43 & EOL)

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.267
  • linux54 5.4.225
  • linux510 5.10.157
  • linux515 5.15.81
  • linux519 5.19.17 [EOL]
  • linux60 6.0.11
  • linux61 6.1.0rc7
  • linux515-rt 5.15.79_rt54
  • linux60-rt 6.0.5_rt14

Package changes (Sun Dec 4 07:41:24 CET 2022)

  • testing community x86_64: 400 new and 395 removed package(s)
  • testing core x86_64: 20 new and 20 removed package(s)
  • testing extra x86_64: 90 new and 90 removed package(s)
  • testing kde-unstable x86_64: 374 new and 374 removed package(s)
  • testing multilib x86_64: 12 new and 12 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:

4 Likes

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: 2022-12-04

python-cairo 1.23.0-2 update requires manual intervention

The python-cairo package prior to version 1.23.0-2 was missing the compiled python module. This has been fixed in 1.23.0-2, so the upgrade will need to overwrite the untracked pyc file that was created. If you receive this error

python-cairo: /usr/lib/python3.10/site-packages/cairo/__pycache__/__init__.cpython-310.pyc exists in filesystem

when updating, use

pacman -Syu --overwrite /usr/lib/python3.10/site-packages/cairo/__pycache__/\*

to perform the upgrade.

2022-11-08

Pop Shell issues with Xorg session with Mutter 43.1 (fixed with mutter 43.1-1.0)

Gnome 43 (X11) GTK4 windows failed to render · Issue #1541 · pop-os/shell · GitHub

Windows not updated after non-interactive resize on X11 (#6054) · Issues · GNOME / gnome-shell · GitLab

2022-10-28

signature from "Manjaro Build Server <build_at_manjaro_dot_org>" is unknown trust

Seems our signing key for our Build Server had the 2022-10-28 as expire date set when generated. This is now fixed for chroot builds and fresh as also current existing installs via manjaro-keyring 20221028-4 Simply update your system to get that package, which got pushed to all our branches.

2022-10-27

Kernel 6.1-rc# might break backlight control on old/weird laptops

2022-10-18

Firefox 106.0 may have issues with screen sharing on GNOME with Wayland

2022-09-23

Nvidia 3060RTX cards may have issues with the 515.76 driver (fixed with 520.56.06)
Removing python2 from the repositories

2022-09-23 - Jelle van der Waa

Python 2 went end of life January 2020. Since then we have been actively cutting down the number of projects depending on python2 in our repositories, and we have finally been able to drop it from our distribution. If you still have python2 installed on your system consider removing it and any python2 package.

If you still require the python2 package you can keep it around, but please be aware that there will be no security updates. If you need a patched package please consult the AUR, or use an unofficial user repository.*

Arch Linux - News: Removing python2 from the repositories

* Note: Unofficial user repositories are not supported

2022-08-27

Changes with Back In Time packages
  • backintime has been renamed to backintime-qt
  • backintime-cli has been renamed to backintime

After replacing backintime-cli with backintime, you will need to install backintime-qt manually if you want the Qt frontend installed again.

2022-08-23

electron12, electron13, electron14 & electron16 have been dropped to the AUR

Unsupported Electron packages have been dropped from the official repos to the AUR. They no longer receive security updates and nothing in the repos depend on them.

If you have AUR packages depending on those versions, install the binary version from the AUR to replace them; i.e., electron16-bin.

See FS#75490 - electron12, electron13, electron14, electron16 are unsupported and vulnerable packages

End of Support for 15.x.y and 16.x.y

Electron 15.x.y and 16.x.y has reached end-of-support. As per Electron’s new 8-week cadence, we were supporting the latest four versions of Electron until May 2022. With this Electron 19 release, we’ll return to supporting the latest three major versions, as well as the alpha, beta, and nightly releases.

Release electron v19.0.0 · electron/electron · GitHub

2022-08-12

element-desktop dependency error (fixed with 1.11.4)
error: failed to prepare transaction (could not satisfy dependencies)
:: installing electron (20.0.0-1) breaks dependency 'electron19' required by element-desktop

The upstream package was already flagged out of date (it needs to be rebuilt against latest electron).

Workaround for now:

sudo pacman -Syy electron electron19 --asdeps
sudo pacman -Su

2022-08-04

Glibc 2.36 update will break EasyAntiCheat within Proton (should be fixed with glibc 2.36-2)

Temporary workaround for now is to use the flatpak version of steam:

sudo pacman -S flatpak --needed --noconfirm
sudo flatpak install com.valvesoftware.Steam -y

You can use flatseal (another flatpak app) to grant it access to your existing game library so you don’t have to re-download your games (add the game library install path under “Other files” under “Filesystem”).

sudo flatpak install com.github.tchx84.Flatseal -y

For advanced users (not recommended by us): patched glibc and lib32-glibc are available here. They remove the commit that broke EAC.

2022-07-27

Fixed: Pamac shows archlinux-keyring (20220713-2) and manjaro-keyring (20220514-2) as orphans
sudo pacman -D --asexplicit archlinux-keyring manjaro-keyring

Resolved: w/ base 3-2 Revert changes:

sudo pacman -D --asdeps archlinux-keyring manjaro-keyring

2022-07-16

wxWidgets 3.2 update may need manual intervention

Packages have been renamed from wxgtk- to wxwidgets-. The GTK2 frontend is no longer provided. If you have wxgtk2 installed, the upgrade will fail with:

In such case, uninstall wxgtk2 first and then proceed with the upgrade.

2022-07-13

Linux518: could not insert 'amd_pstate': No such device

With Kernel 5.18.11 there was added a regression to AMD P-State driver preventing it from loading.

2022-07-08

Wireplumber 0.4.11 may crash for GDM users

Currently there is an issue with 0.4.11 and GDM crashing on boot-up. More in the upstream bugtracker issue: wireplumber segfault: system boot and could see in my dmesg (#305) · Issues · PipeWire / wireplumber · GitLab

2022-06-07

Locale file changes

C.UTF8 locale is now included in glibc:

Credits @diabonas for this change. Systemd wants us to include C.UTF8 by default and it seems the locale may be in included by glibc upstream in the future. To fix building and avoid nasty fixing in devtools, we include the locale in the package. See systemd/systemd#23252 (comment) FS#74864 : [systemd] >= 251 breaks devtools' locale

There is a pacsave for /etc/locale.conf as it has been removed from the filesystem package.

UPDATE: With filesystem 2022.06.08-2, it will automatically restore /etc/locale.conf if it did not already exist.

There is a pacnew for /etc/locale.gen. Please review it and regenerate your locale if necessary.

i have theses message error after systemd V251.8 return

Journal file /var/log/journal/e1d2ad259a0c4b3494932a11ddd42221/system@0005eefd1c25dcbe-bc30fa3cea777cf1.journal~ uses an unsupported feature, ignoring file.
Use SYSTEMD_LOG_LEVEL=debug journalctl --file=/var/log/journal/e1d2ad259a0c4b3494932a11ddd42221/system@0005eefd1c25dcbe-bc30fa3cea777cf1.journal~ to see the details.

your log have been written with with 252 . Not really strange if 251 found “unsupported feature” error

Mesa is now maintained by Manjaro and won’t ship with patent encumbered codecs .

So in this case, no more H.264 and H.265 hardware acceleration? Any possibility to still get the hardware acceleration?

Damn, that’s a bummer.
Would not have thought this would affect a european (german based) company let alone the manjaro distro as a community project. :disappointed:


edit:
“downgrading” to arch’s packages re-enabled hardware acceleration as they’re including support in their builds:

1 Like

if possible use avc1 ( AV1 )
i use under Firefox , an extension enhanced-h264ify
==> you can block ( H264 , VP8 , VP9 , AV1 ) , keep AV1

for another usage ( compression video ) this is different

Isn’t AVC1 H264? and isn’t AV1 hardware decoder only available on latest video cards (and not the same as H264)? None of what you wrote makes sense to me regarding the issue. I may be misunderstanding something, I guess.

1 Like

AVC1 = AVC = H264

3 Likes

Yeah, right, and indeed, AV1 is only available on recent graphic cards AV1 - Wikipedia

1 Like

AV1 is open free royalties

from before :
"What is notable and significant in this case is that these patents only apply to corporations with a presence in the US. In other words, these patent rights do not apply in Europe, where the software patent law differs.

As a result, Linux distributions headquartered outside the US or entirely community-driven, with no commercial purpose, are not subject to the risk of infringing on these patent rights."

"First and foremost, it should be stated that this problem will only affect users with AMD-based systems. Why? Because AMD entirely relies on Mesa for these codecs.

Users using an Intel GPU will be unaffected because either “intel-media-driver” or “libva-intel-driver” already provides VA-API (Video Acceleration API) hardware decoding without requiring Mesa.

At the same time, NVIDIA users can also rest easy because there is a proprietary driver that, by default, supports the codecs mentioned above."

1 Like

Mesa is now maintained by Manjaro and won’t ship with patent encumbered codecs

Is there any information available what “tangible” impact this move will have on the average Manjaro user - for all those who aren’t following the video codec developments in detail?
Will this break anything, for example will youtube / [insert-favourite-streaming-service] / [insert-video-conferencing-platform] stop working?

2 Likes

If I’ve read this article correctly (regarding Fedora and OpenSUSE dropping same CODECS), and if it applies here in similar fashion it means these formats will now be decoded by the CPU rather than the GPU, save for Nvidia GPU users using proprietary drivers and Intel GPU users and will have a bigger impact on battery life for laptop users.

7 Likes

Good grief! I don’t want to go back to Ubuntu after all these years with Manjaro, esp due to the nature of this problem.

Edit: OK, I am not affected by this, lucky break.

Thank you for the article link.
It provides important and clear information.

totem doens’t play videos, smplayer works.

1 Like

Can you elaborate? Why aren’t you affected by the new mesa without patent encumbered codecs?

1 Like

Can you elaborate? Why aren’t you affected by the new mesa without patent encumbered codecs?

Maybe because of these statements from this article linked by @2old4gaming?

First and foremost, it should be stated that this problem will only affect users with AMD-based systems. […]

Users using an Intel GPU will be unaffected […]

[…] NVIDIA users can also rest easy because there is a proprietary driver that, by default, supports the codecs mentioned above.

If that is indeed the case it would be nice to clearly communicate that in the Manjaro announcement. Because the originally linked article about patent encumbered codecs does not make it really clear who is affected and to what extend.

@2old4gaming’s linked article also claims:

As a result, Linux distributions headquartered outside the US or entirely community-driven, with no commercial purpose, are not subject to the risk of infringing on these patent rights.

Not sure if that is true but wouldn’t Manjaro fall into that category?

3 Likes

I’ve found this even more clear:

What is notable and significant in this case is that these patents only apply to corporations with a presence in the US. In other words, these patent rights do not apply in Europe, where the software patent law differs.

Linux distros based outside of the US are not threatened with potential consequences for infringed patent rights applicable in the US.

2 Likes

Yes, let’s not import that ■■■■ here, please

1 Like