Help with the version of MX KDE officially released by the Development Team.
When asking for help, use Quick System Info from MX Tools. It will be properly formatted using the following steps.
1. Click on Quick System Info in MX Tools
2. Right click in your post and paste.
OK--it's using the current 535 Nvidia driver to supply graphics, which certainly supports those codecs with the GTX 1050 card. I missed that and assumed it was using the Intel iGPU. So no wonder vainfo borked, since we want the result of "vdpauinfo" for the Nvidia graphics (example output below). I wonder if the Intel integrated GPU is fully disabled in the BIOS, since we see this:
Oh, yeah, I forget to mention that Ungoogled chromium is a Flatpak application unlike the other applications, so it may work because it run on it's own dependencies.
j2mcgreg wrote: Tue May 06, 2025 8:34 am
@ostrog wrote:
I have no problem playing that video.
Your QSI shows that you have a VPN installed. Can you access and run any of these problem videos after disabling the VPN.
I think you misunderstood me. We are talking primarily about local files, so accessing the videos is not the problem.
I drag and drop the local video into my browser and this is the error I get: "No video with supported format and MIME type found."
yep all that looks normal.
and you also can't play that big bunny video you linked, correct? at least in vlc?
Yes, not only in VLC but in Librewolf and Celluloid too.
Celluloid doesn't even open. In terminal it outputs this error:
celluloid: error while loading shared libraries: libavcodec.so.59: cannot open shared object file: No such file or directory
Stevo wrote: Tue May 06, 2025 12:19 pm
OK--it's using the current 535 Nvidia driver to supply graphics, which certainly supports those codecs with the GTX 1050 card. I missed that and assumed it was using the Intel iGPU. So no wonder vainfo borked, since we want the result of "vdpauinfo" for the Nvidia graphics (example output below). I wonder if the Intel integrated GPU is fully disabled in the BIOS, since we see this:
vdpauinfo
display: :0 screen: 0
API version: 1
Information string: G3DVL VDPAU Driver Shared Library version 1.0
Video surface:
name width height types
-------------------------------------------
420 16384 16384 NV12 YV12
422 16384 16384 UYVY YUYV
444 16384 16384 Y8U8V8A8 V8U8Y8A8
420_16 16384 16384 P010 P016
422_16 16384 16384
444_16 16384 16384
Decoder capabilities:
name level macbs width height
----------------------------------------------------
MPEG1 --- not supported ---
MPEG2_SIMPLE 3 65536 4096 4096
MPEG2_MAIN 3 65536 4096 4096
H264_BASELINE 52 65536 4096 4096
H264_MAIN 52 65536 4096 4096
H264_HIGH 52 65536 4096 4096
VC1_SIMPLE 1 65536 4096 4096
VC1_MAIN 2 65536 4096 4096
VC1_ADVANCED 4 65536 4096 4096
MPEG4_PART2_SP 3 65536 4096 4096
MPEG4_PART2_ASP 5 65536 4096 4096
DIVX4_QMOBILE --- not supported ---
DIVX4_MOBILE --- not supported ---
DIVX4_HOME_THEATER --- not supported ---
DIVX4_HD_1080P --- not supported ---
DIVX5_QMOBILE --- not supported ---
DIVX5_MOBILE --- not supported ---
DIVX5_HOME_THEATER --- not supported ---
DIVX5_HD_1080P --- not supported ---
H264_CONSTRAINED_BASELINE 0 65536 4096 4096
H264_EXTENDED --- not supported ---
H264_PROGRESSIVE_HIGH --- not supported ---
H264_CONSTRAINED_HIGH --- not supported ---
H264_HIGH_444_PREDICTIVE --- not supported ---
VP9_PROFILE_0 --- not supported ---
VP9_PROFILE_1 --- not supported ---
VP9_PROFILE_2 --- not supported ---
VP9_PROFILE_3 --- not supported ---
HEVC_MAIN 186 139264 8192 4352
HEVC_MAIN_10 186 139264 8192 4352
HEVC_MAIN_STILL --- not supported ---
HEVC_MAIN_12 --- not supported ---
HEVC_MAIN_444 --- not supported ---
HEVC_MAIN_444_10 --- not supported ---
HEVC_MAIN_444_12 --- not supported ---
AV1_MAIN --- not supported ---
AV1_HIGH --- not supported ---
AV1_PROFESSIONAL --- not supported ---
Output surface:
name width height nat types
----------------------------------------------------
B8G8R8A8 16384 16384 y NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 P010 P016 A8I8 I8A8
R8G8B8A8 16384 16384 y NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 P010 P016 A8I8 I8A8
R10G10B10A2 16384 16384 y NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 P010 P016 A8I8 I8A8
B10G10R10A2 16384 16384 y NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 P010 P016 A8I8 I8A8
Bitmap surface:
name width height
------------------------------
B8G8R8A8 16384 16384
R8G8B8A8 16384 16384
R10G10B10A2 16384 16384
B10G10R10A2 16384 16384
A8 16384 16384
Video mixer:
feature name sup
------------------------------------
DEINTERLACE_TEMPORAL y
DEINTERLACE_TEMPORAL_SPATIAL -
INVERSE_TELECINE -
NOISE_REDUCTION y
SHARPNESS y
LUMA_KEY y
HIGH QUALITY SCALING - L1 y
HIGH QUALITY SCALING - L2 -
HIGH QUALITY SCALING - L3 -
HIGH QUALITY SCALING - L4 -
HIGH QUALITY SCALING - L5 -
HIGH QUALITY SCALING - L6 -
HIGH QUALITY SCALING - L7 -
HIGH QUALITY SCALING - L8 -
HIGH QUALITY SCALING - L9 -
parameter name sup min max
-----------------------------------------------------
VIDEO_SURFACE_WIDTH y 48 4096
VIDEO_SURFACE_HEIGHT y 48 4096
CHROMA_TYPE y
LAYERS y 0 4
attribute name sup min max
-----------------------------------------------------
BACKGROUND_COLOR y
CSC_MATRIX y
NOISE_REDUCTION_LEVEL y 0.00 1.00
SHARPNESS_LEVEL y -1.00 1.00
LUMA_KEY_MIN_LUMA y
LUMA_KEY_MAX_LUMA y
No, I only use the iGPU for a dual monitor setup to save some system resources. That's why I activated it in the BIOS settings.
vdpauinfo outputs this:
Just mentioning that the linked Blender video works in all expected ways over here. Accessing the link with Librewolf, then downloading a local copy (Save video as...), opening the local copy with VLC, dragging the local copy into Librewolf, dragging the local copy into Reaper, etc. etc. Everything opens and shows the video as expected. I don't have any codec funny business installed on this system :), just the usual stuff, i.e. mx-codecs, ffmpeg, and the latest VLC available from the repo. Librewolf 138.0.1.
Ah, you have a "libavcodec.so.59: cannot open shared object file: No such file or directory" error there; see if you indeed don't have the libavcodec59 package installed. You will need to uncheck the "hide library and developer packages" in MXPI. If you don't have this codec, install it and try again.
dolphin_oracle wrote: Wed May 07, 2025 9:56 am
the apt policy information shows it installed
Heh, I gloriously missed that xD. But yeah, it's quite odd this shows a "No such file or directory" error if it's indeed there. Might be interesting to peek into /usr/lib/x86_64-linux-gnu, and see if the actual file is where it's supposed to be. There should be a libavcodec.so.59 symlink and the actual library file it's pointing at. In any case, a reinstall is good to try, yep.
dolphin_oracle wrote: Wed May 07, 2025 9:56 am
the apt policy information shows it installed, but might be worth reinstalling it.
I uninstalled it in MXPI and it removed 31 package along. I should have reinstalled in with the reinstall feature of Synpatic. But after reinstalling the packages it works on all 3 softwares.
Thank you very much.
dolphin_oracle wrote: Wed May 07, 2025 9:56 am
the apt policy information shows it installed, but might be worth reinstalling it.
I uninstalled it in MXPI and it removed 31 package along. I should have reinstalled in with the reinstall feature of Synpatic. But after reinstalling the packages it works on all 3 softwares.
Thank you very much.
Hey that's great! A bit of a mystery how it got to that state, not being found on the file system level while still showing that it's already installed. I'd almost go as far as saying... if some other library / random thing starts behaving in a similar fashion, without any obvious change in the system, it's time to start backing up your data. Just in case.
(Of course, anything important should be backed up in any case so ... yeah.)
dolphin_oracle wrote: Wed May 07, 2025 9:56 am
the apt policy information shows it installed
Heh, I gloriously missed that xD. But yeah, it's quite odd this shows a "No such file or directory" error if it's indeed there. Might be interesting to peek into /usr/lib/x86_64-linux-gnu, and see if the actual file is where it's supposed to be. There should be a libavcodec.so.59 symlink and the actual library file it's pointing at. In any case, a reinstall is good to try, yep.
Well, unfortunatly it's too late now, I already reinstalled it. As you said these 2 files are in there now.
ostrog wrote: Wed May 07, 2025 11:13 am
Well, unfortunatly it's too late now, I already reinstalled it. As you said these 2 files are in there now.
Good that everything is in working order now. Btw, about that MXPI / Synaptic reinstalling tidbit: to my understanding, if you select a package that shows already installed in MXPI and still click on "Install", that will basically reinstall the package.
so ... yeah.)