[Stable Update] 2022-12-06 - Kernels, Mesa, Plasma, Cinnamon, Nvidia, LibreOffice, Pipewire, Virtualbox

Announcements Stable Updates
,
138

@Zesko @MirceaKitsune @zbe @Begemoth

Here is a more accurate test, based on what @Begemoth corrected me on. (Because YouTube videos don’t necessarily use AVC or HEVC, as they are shifting towards more open codecs. Hence, YouTube videos are not good tests.)

Let this video play for at least 5 to 10 minutes, longer if possible.

Preferably in fullscreen.

Keep an eye on CPU temperatures (all cores and/or composite) throughout.

Keep an eye on CPU usage (all cores and/or composite) throughout.

Repeat the same exact thing after applying the Stable Updates and rebooting.

The video is nearly 1GB in size, but it’s a high bitrate and resolution, and uses HEVC. It will be a good test on whether or not your GPU is using hardware-accelerated decoding.

A better test would be with a 4K video, but the size would be very large.

Here’s a 4K video that is 3 GB if you want to really give this a proper test:

https://drive.google.com/uc?id=1sRvHcH_BSVGELaPb2p_FFjXd53Mzl94L&export=download

Not just CPU temps and usage, but also how “smoothly” does it play?

139

Little correction: h265 isn’t supported by browsers, just not able to play that codec.

We can use vainfo (terminal command), it shows which codecs you can accelerate and by what. That is mine, for example, with mesa-git:

изображение
изображение1908×1456 365 KB

If you have AMD graphics and mesa from Manjaro repo, you will see output from this post. :unamused:

1 Like
140

well, it still is you just need a distro that hasn’t disabled the feature or compile it where it has. And so far as compiling Manjaro is probably one of the easiest.

141

I was getting an issue with window positioning in kwin wayland. The window rules did not work. Deleting old rules and creating them again solved the issue

142

Not gonna spend that much time on it, was just curious to test it to some extent. Did the first one in both VLC and Dragon Player: Only between 5% and 10% CPU usage, so basically same as Youtube in Firefox.

1 Like
143
2 Likes
144

On my Dell Ultrabook the kernel 6.1 fails to boot. Solution was fallback to 6.0. No other issues so far.

145

But,but, but… I can vote for only 1 computer. It doesn’t let me vote for the others

1 Like
146

Thanks.
Have a clonezilla image to redo system partition.

147

This batch of updates seems to have severely crippled pulseaudio … having to restart the pulseaudio server every few minutes after the audio completely dies, then restart VLC, reload a YouTube video, etc, until the audio dies again, sometimes just from pausing YouTube or VLC playback. See this related thread:

1 Like
148

You do know that ketnel is still in its rc phase, don’t you?

149

@winnie, @MirceaKitsune, @Begemoth

VLC, mpv, SMPlayer,Firefox and Chromium based browsers … use the dependence ffmpeg by default. I think ffmpeg supports H264 and H265 encoding and decoding. They do not need to use mesa.

Edit://
ffmpeg uses mesa for AMD GPU: Hardware/VAAPI – FFmpeg
I will test it later when I’m at home.

1 Like
150

If you check how ffmpeg deals with hardware acceleration for encode/decode you will see that for AMD it uses va-api provided by mesa, that in this update was disabled for h264 and h265. Intel and NVIDIA are unaffected as they use different code/package.
The amdgpu-pro driver might be unaffected too but I haven’t researched it, so I don’t know.

151

To check whether hardware acceleration is currently running during playback (as root/sudo)
cat /sys/kernel/debug/dri/0/amdgpu_pm_info | grep VCN:

I’m still trying to figure out the reasoning for this change.

  • Neither intel open source driver nor mesa driver is being developed by manjaro team, but included in manjaro repositories.
  • Also, this won’t block anyone from encoding and decoding streams (so using MPEG-LA intellectual property) in software,
  • Neither driver contains any patented code or logic, and only provides an API to EXTERNAL hardware that implements the function, that is developed, manufactured by legal companies, and bought and installed by the user or machine manufacturer. Not manjaro team.
  • And the machine itself is being used by the user, and the user holds responsibility how it is using it. Not manjaro (or any other distro) team.

Isn’t it ironic, that large companies use free open source encoders like x265 to deliver often paid and copyrighted content to users who are going to be not allowed to decode it on expensive proprietary hardware they paid for?

4 Likes
152

Hi,

I don’t now if it’s link. It happened for me too with this update on a MSI laptop running on wayland and battery during the update.

Ctrl+alt+F3 (or other one) didn’t help but cap still respond.

I wait a few and hard reboot.

Wish You well

153

I noticed that now system monitor plasma-systemmonitor does not display GPU (Nvidia gtx1060) informations anymore; eg the sensors for temperature, memory and gpu frequency, gpu usage and vram usage are all at zero.
I suspected the GPU was somehow not detected or something like it but nvidia-smi --loop shows the GPU is correctly utilized and all of the related sensors work.
Just reporting here as before the update it was working correctly (Manjaro KDE, kernel 5.15.81, X11)

2 Likes
154

This is the second update that borked by Anki flatpak install somehow

Anki starting...
Initial setup...
Preparing to run...
Qt warning: qglx_findConfig: Failed to finding matching FBConfig for QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1, alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::NoProfile) 
Qt warning: qglx_findConfig: Failed to finding matching FBConfig for QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1, alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::NoProfile) 
Qt fatal: Could not initialize GLX

Re-installing fixes it, but shouldn’t flatpaks be pretty immune to getting broken by system updates? Doesn’t make sense to me.

2 Likes
155

I’m having the same issue as well, plasma-systemmonitor is unable to display any of the sensors/usage stats of my graphics card (Nvidia RTX3070Ti) but other programs such as Nvidia control panel, mangohud, etc are able to display these usage statistics just fine. I’m running kernel 6.0.11-1-MANJARO and Nvidia driver version 525.60.11

It was also working just fine for me before the update, do we just need to wait for a plasma update, or is something else missing?

1 Like
156

I cant find this stable update with my Laptop… with my PC it showed up.

They both using the same Kernel (5.15) and almost everything is identical.

I updated the mirrors with sudo pacman-mirrors --fasttrack but Laptop just showed up to date in the Pamac UI :scream:

I just created a Topic:

1 Like
157

Whats new since the Update

Airplay2 works great with raop-discover and raop.encryption.type = "auth_setup" :heart_eyes:
Tested with KEF-LSX

Firefox coredump systemd-coredump[2164]: [🡕] Process 2126 (firefox) of user 1000 dumped core :shushing_face:

1 Like