Manjaro is a company. Arch is not.
Disclaimer: I was not involved in this decision as I am part of the community, not the company
Ok, fair enough. 
I guess there might be different opinions in the team.
But in particular if that’s the decision of a company, the continued availability of software decoding (please, correct me if I’m wrong) for the very same codecs makes it either look like a very half-cooked decision or a somewhat insincere/incomplete explanation.
AFAIK the relevant patents only concern GPU decoding.
Tried solution suggested by @marlop, but did not work for me ecen though compile and install worked.
So downgraded mesa with the list @Yochanan suggested above. That didn’t work either.
So downgraded mesa with the list @oneno suggested above with lib32 packages and worked!
$ vainfo
Trying display: wayland
Trying display: x11
vainfo: VA-API version: 1.16 (libva 2.16.0)
vainfo: Driver version: Mesa Gallium driver 22.2.3 for AMD CAICOS (DRM 2.50.0 / 5.15.81-1-MANJARO, LLVM 14.0.6)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple : VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main : VAEntrypointVLD
VAProfileVC1Advanced : VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264Main : VAEntrypointVLD
VAProfileH264High : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc
Same on second machine...
$ vainfo
Trying display: wayland
Trying display: x11
vainfo: VA-API version: 1.16 (libva 2.16.0)
vainfo: Driver version: Mesa Gallium driver 22.2.4 for AMD ARUBA (DRM 2.50.0 / 5.15.81-1-MANJARO, LLVM 14.0.6)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple : VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc
After downgrade:
$ vainfo
Trying display: wayland
Trying display: x11
vainfo: VA-API version: 1.16 (libva 2.16.0)
vainfo: Driver version: Mesa Gallium driver 22.2.3 for AMD ARUBA (DRM 2.50.0 / 5.15.81-1-MANJARO, LLVM 14.0.6)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple : VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main : VAEntrypointVLD
VAProfileVC1Advanced : VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileNone : VAEntrypointVideoProc
$
2 posts were split to a new topic: Konsolerc already exists in filesystem
so yeah there has to be linux 6.0. But since I am not quite aware of things like [EOL] and rt54 and r14, I thought of asking here. I know my question was stupid but I would be grateful if I was educated on these things.
My original being : is stable update receiving 6.0 kernel or is it still in version 5 ?
rt means “Experimental” (the actual word I don’t right now, but that’s what it boils down to; rc is “Release Candidate”, EOL is “End of Life”, thus about to lose support. Unless you know exactly what you’re doing, stay away from kernels with letters in their version numbers -they’re for testing, and may well give you a headache.
rt is Real Time
1 Like
As long as you don’t have the hardware that module’s needed for, you don’t need to worry.
I deleted some modules for hardware I don’t have and I get warnings like this for them.
On the other hand, if you do have that hardware, you need to find the module in the package manager and install it.
Maybe it’s shown because of the kms hook?
I have merged the mkinitcpio.conf
—> [SOLVED] Latest mkinitcpio giving errors... / Pacman & Package Upgrade Issues / Arch Linux Forums
I will ignore it
Try adding ibt=off to kernel parameters. It helped for me (Intel 9th gen)
@pheiduck If you’re running qemu on Intel hardware, that’s worth trying I guess.
firefox still doesn’t work (sometimes)…
This is worrying news, to say the least…
@direc85 thanks I am a AMD 
User 
And my issue is solved:
1 Like
This seems to be a fairly widespread issue, and does seem to be on the KDE side of things. I’m going to keep an eye on this bug report, but figured I would share this for you or anyone else with this issue who is looking for more info.
Can also confirm i’m seeing this. Restart pulse audio works until the next crash. Last noticed it after leaving and rejoining a Zoom meeting.
ERROR:pulse_util.cc(350)] pa_operation is nullptr
ThinkPad X1 Carbon 7th, 5.15.81-1-MANJARO
driver=sof-audio-pci-intel-cnl
manjaro is trying to associate thier operating system with retailers of machines, this may be why they are being so cautious, apart from that i dont know
1 Like
I’m still downloading the update (1.7GB) and it’s taking uncharacteristically long (almost 4 hours in total). The update is slow but uninterrupted, which leads me to suspect that something somewhere is rate limiting it. Do you know if any Manjaro mirrors do that?
I updated a laptop today, that also had 1.7 GB of updates, but it was done fairly quickly.
You sure you are not building an AUR package, like Python2 or Ceph-libs?
No it’s definitely the download based on the log. It finished after almost 5 hours. I’ll changed to another mirror in case this one is overloaded. I was also suprised because I had updates of similar size and none of them took this long.
CPU usage of playing videos in the browsers has always been way too high compared to a dedicated video player - even when backed by GPU decoding. Especially Firefox with its multiple processes involved (looking at you Isolated Web Content).
But it’s not a Linux problem. Chrome on Windows sucks at it as well.
Also YouTube uses VP9 per default (see Stats for nerds in the YouTube context menus) which is royalty-free and doesn’t appear to use H264/H265.
I have not experienced a difference in smoothness and I still see the GPU being utilized when playing videos.