I am unable to play videos of type mp4, avi, mov and possibly unable to play video at all. VLC could not decode Format „h264“ (H264 - MPEG-4 AVC (part 10)).
The current VLC version is 3.0.21, a re-install yields the same version, i.e. in Manjaro that is the latest version. I observe: if I install VLC in Windows or Ubuntu, I get 3.0.32; with 3.0.32 everything works fine.
Q1: why is 3.0.32 unavailable in Manjaro?
Q2: From the VLC Homepage I could download vlc-3.0.23.tar.xz. Is it recommendable to install VLC 3.23 from the tar.xz file? Or is there a possible disadvantage?
Q3: How do I install from tar.xz file?
Is there an official recommendation how to solve my problem?
I’m not sure what the problem is with VLC - Manjaro does have 3.0.21 - reinstalling won’t change the repositories.
I can’t say much more - I use MPV, but had no issues with either…
But when you said ‘unable to play video at all’ you gave a very specific issue 'VLC could not decode Format „h264“ (H264 - MPEG-4 AVC (part 10))` which doesn’t point to ‘unable to play video at all’ as that looks like a very specific file.
On Manjaro, vlc 3.0.21-32 doesn’t necessarily mean you have an older version than 3.0.32.
The version format for Manjaro is the actual upstream version of VLC (3.0.21) and the -32 is the package revision including backported fixes and tweaks.
So unless you have specific features, you should focus on troubleshooting the H264 issue. This came up before when VLC packages were split up, and it was fixed by installing the meta-package vlc-plugins-all.
VLC is inherited from Arch – version 3.0.21-32 is available in all branches, and Arch repositories; until Arch changes that, Manjaro has little option than to wait; just like you.
$ mbn info vlc -q
Branch : archlinux
Name : vlc
Version : 3.0.21-32
Repository : extra
Build Date : Thu 27 Nov 2025 02:10:06
Packager : Christian Heusel <gromit@archlinux.org>
Branch : unstable
Name : vlc
Version : 3.0.21-32
Repository : extra
Build Date : Thu 27 Nov 2025 02:10:06
Packager : Christian Heusel <gromit@archlinux.org>
Branch : testing
Name : vlc
Version : 3.0.21-32
Repository : extra
Build Date : Thu 27 Nov 2025 02:10:06
Packager : Christian Heusel <gromit@archlinux.org>
Branch : stable
Name : vlc
Version : 3.0.21-32
Repository : extra
Build Date : Thu 27 Nov 2025 02:10:06
Packager : Christian Heusel <gromit@archlinux.org>
It is recommended to install VLC from the official Manjaro repositories; given the current available versions, unfortunately 3.0.21-32 is the only option.
The option to build (version 4.0.0) via the AUR exists; however, I believe that might be still in development:
VLC 3.0.23 is available as a Flatpak:
flatpak search vlc
flatpak install vlc
I will not venture into this because it seems likely your problems with VLC are limited to your environment; your User account, perhaps – I am currently using VLC (from the official Manjaro repo) with no issues such as you have described.
Please create a new User account for testing purposes – reboot, and login to the new account, and verify whether the same issues persist – this will help to rule out local issues.
Edit:- An afterthought…
Let’s also rule out the possibility of missing plugins;
Please provide the output of:
I concur. The issue is most likely local to the OPs setup, and they are asking the wrong question… and the direction they appear to be taking will likely cause them additional grief.
VLC works on both my testing installs, without any issues. It also works without issue on my partner’s stable install, and on my ‘media’ computer, which is running with stable.
I invoked “pacman -S vlc-plugins-all” (proposal from @molski) to make sure that I have got all the plugins. However, that did not solve my problem.
Next I followed the proposal of @soundofthunder; I logged in as a different user. VLC worked as desired. So I copied the vlcrc file to the .config/vlc folder of my userid.
because the issue was strongly suspected to be local to the environment.
As it happens, this was indeed true, which in turn led the OP to follow instructions given and work the problem, now confident that the issue was specific to their User account.
Lolz now you’re confused. The advice was to simply:
So this verified that it was USER data - so then (not being a complete numpty) they decided to import that .config file as one that works… though simply deleting the existing file (or renaming mv vlcrc vlcrc-borked would have been nicer - then after starting vlc, getting a new config, you could do a meld and see what’s actually the issue).