Fedora 35 + vlc: can't play videos or wrong colors
Linux - DesktopThis forum is for the discussion of all Linux Software used in a desktop context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
but nothing changed. At the end of this page there is:
Code:
You need to enable EPEL on RHEL or compatible distributions like CentOS before you enable RPM Fusion for EL. See the fedoraproject wiki for instruction how to enable EPEL
but nothing changed. At the end of this page there is:
Code:
You need to enable EPEL on RHEL or compatible distributions like CentOS before you enable RPM Fusion for EL. See the fedoraproject wiki for instruction how to enable EPEL
In our experience, heap corruption bugs are application bugs in the vast majority of cases, and not bugs in the glibc memory allocator. glibc updates occasionally expose additional application bugs because of changes in heap layout.
The mention of glibc stands out to me, and I would venture a careful guess: version mismatch? System up-to-date? How did you install VLC?
I installed fedora 35 few days ago from the DVD with the iso image.
After the installation, I run (as root): "dnf update" to update everything.
Then I started going over the diff between the previous Fedora version (32) list of packages
and the new OS list, performing "dnf install ..." for programs I need which are not
installed by default. Among them was: "dnf install vlc".
Before reading your reply I experimented with "vlc" settings reharding HW acceleration.
By default, it was "auto".
When I changed to "None": vlc could play videos (mkv/mp4), CPU usage of core was 40%-50% (AMD Phenom X4, video card: ATI FireGL V5600).
When I changed it to "VA-API video decoder": same failure as in "auto" mode.
When I changed it to "VDPAU video decoder" or "VA-API video decoder via DRM": could play, same CPU usage as without HW acceleration.
If in these two "acceleration" modes the CPU usage was like without any acceleration then can I assume, that they're really
not accelerating anything?
My video card is quite old (my PC had been intially built in 2009 and CPU/mainboard/graphic card are still of the same model, although they'be been replaced
without changing models), can it be the avaliable video drivers stopped supporting too old cards?
The file path you gave "/usr/lib64/dri/r600_drv_video.so" is a binary file and looking in the /etc/X11 directory I don't see anything that looks like card-related
info but maybe I missed something. What file is the one you showed the contents of?
r600* file that I quoted comes from your first code box post 1.
Leaping ahead, do you have that pathway and file?
2) Leaping ahead....you might want to look at your /var/log/Xorg*log and upload it as a txt file
I have to use root powers to view mine, so convert yours to something visible to local user before uploading it.
3) report your
Code:
inxi -Gxxx
output please
In particular only some video chipsets support certain things. Such as VDPAU
After setting in "vlc" the HW acceleration to "auto" (to cause it to fail)
and re-running
vlc Aviation_odd_ducks.mkv
which failed just as before, I checked again the log files: there was no change in their
timestamps, that is: the vlc crash didn't write anything into them.
lines 91-214 list chipsets and yours seems to fall to 186 = Gemini Mobility Radeon HD 2600 XT, ATI FireGL V5600
suggesting a laptop.
line 233 is a match to inxi product ID 958c.
lines 457-8 give us
RADEON(0): [DRI2] DRI driver: r600 & RADEON(0): [DRI2] VDPAU driver: r600
line 505 = RADEON(0): Setting screen physical size to 1016 x 317
-> I have not asked, so first my command output is
Code:
NOT OP
xdpyinfo | grep -B 2 resolution
screen #0:
dimensions: 1920x1080 pixels (508x285 millimeters)
resolution: 96x96 dots per inch
this matches my Xorg log entry for AMDGPU(0): Setting screen physical size to 508 x 285
Your modelines show up look ok until I spotted line 410 = RADEON(0): Output DVI-1: Strange aspect ratio (708/268), consider adding a quirk
-> but you do not seem to be using 708x268 so me thinks we can ignore that line
############################
EEK Just found something not sure what to do but ....
Quote:
line 505 RADEON(0): Setting screen physical size to 1016 x 317
INXI .............s-size: 508x318mm
hmmmm I think we need to see
Code:
xdpyinfo | grep -B 2 resolution
but still not sure what to do with the mismatch......leaping ahead, you might need to force a resolution in an xorg config file
they are native as package name contains fc= Fedora Core
Quote:
As for xwayland: that's what my F35+KDE system uses by default.
That is not what I asked. You appear to claim you are logging into Xorg and showing me an Xorg log.
If you were booting into wayland, you do not need an Xorg config file, nor a log.
Please read your Fedora wiki or whatever on how to login to KDE running on Wayland.
It might be as simple as disabling autologin, then on reboot choose wayland in some pulldown in your display manager.
I have logged into sway, on Tinycore in a very different way and vlc runs on sway which runs on Wayland.
2) your xpdyinfo screen size conflicts with line 505.
that is why I want you to try wayland.
Do you now understand?
there is something wrong with your Xorg setup, this is resolved by running wayland which avoids/evades Xorg
First, I had another problem which turned out to be caused by running xwayland ("-geometry" switch disappeared from "konsole").
Second, I have a konsole with "top" automatically start and during the first few seconds after login
I saw there "Xwayland" running.
I looked at the "Xorg" files because aus9 mentioned it.
Since, as I understand, it's either "Xwayland" or "Xorg" then it seems in my case it's "Xwayland"
and the "Xorg" is irrelevant.
Lets review, if you claim you did not change your display manager settings, so you have always logged into something
Then your inxi command shows at post 7
if your Xorg log shows your current boot up time.....You are on Xorg. If on the other hand, timestamp is an old timestamp.....you are on Wayland and sorry for any confusion
4) in post 7 you posted Xorg log and it claims
Quote:
Log file: "/var/log/Xorg.0.log", Time: Sun May 8 14:39:06 2022
in my browser, I am 8 hrs ahead of London, GMT, UTC so your post was May 9 0313 hours
5) There are independent ways of checking via commands if you are on wayland or xorg
try some of these please and report
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
