Description of problem: vdpauinfo gets a segmentation fault. The Fedora version is 33, and the video controller is the on-board graphics of the Intel i7-8550U CPU. Output of lspci -nn | grep VGA: 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) Version-Release number of selected component (if applicable): vdpauinfo-1.4-1.fc33.x86_64 How reproducible: Every time I've tried it. Steps to Reproduce: 1. Run vdpauinfo. 2. Watch it produce numerous lines of output, and 3. It ends with a "Segmentation fault (core dumped)". Actual results: More than 100 lines of output, then "Segmentation fault (core dumped)". Expected results: I'm honestly not certain what the precise output of this command should be. Additional info: The last few lines of output before faulting are: attribute name sup min max ----------------------------------------------------- BACKGROUND_COLOR - CSC_MATRIX - NOISE_REDUCTION_LEVEL - SHARPNESS_LEVEL - LUMA_KEY_MIN_LUMA - LUMA_KEY_MAX_LUMA -
vdpauinfo-1.4-1.fc33.x86_64 doesn't segfault with me. You have to be more verbose on your config and do provides a stacktrace: https://fedoraproject.org/wiki/StackTraces
Created attachment 1812207 [details] vdpauinfo backtrace Indeed, and it does not segfault for me on an older CPU running Fedora 34. I'm happy to oblige with more verbosity. Please see if the attached file is enough. The debuginfo package concept is new to me, so let me know if I should grab more.
Seems like you are using libvdpau-va-gl, but this component shouldn't be used if you can use a native vaapi backend. Is there any situation where you really need to use the VDPAU over your native VA-API backend ? About you trace, I don't see the segfault, does it mean the segfault cannot be reproduced under gdb ? Also can you reproduce the segfault with vdpauinfo downgraded to the default vdpauinfo version in f33 (dnf downgrade vdpauinfo) ?
Nicolas, I'm afraid you've gone beyond my knowledge base. I assumed that this command would fail gracefully if it was not appropriate for this hardware or combination of libraries. You're right about the segfault. I had wrongly assumed the backtrace would have that. This is the tty output from the time of the segfault: ... (redacted) ... LUMA_KEY_MIN_LUMA - LUMA_KEY_MAX_LUMA - [Thread 0x7fffee80a640 (LWP 11606) exited] [Thread 0x7fffef00b640 (LWP 11605) exited] [Thread 0x7fffef80c640 (LWP 11604) exited] [Thread 0x7ffff000d640 (LWP 11603) exited] Thread 1 "vdpauinfo" received signal SIGSEGV, Segmentation fault. 0x00007ffff6333578 in unlink_block (info=0x5555559004e0) at ../src/util/ralloc.c:286 286 if (info->parent->child == info) After that was a message starting with "Missing separate debuginfos", listing more than a dozen packages. Would it be useful to load those and re-run?
> Nicolas, I'm afraid you've gone beyond my knowledge base. I assumed that this command would fail gracefully if it was not appropriate for this hardware or combination of libraries. True. Still, I'm not reproducing on two of my hardware, so it might be something else. Using debuginfo would be still useful, but please try to downgrade to the previous vdpauinfo to see if you can reproduce. This will help to narrow the issue.
I was able to downgrade from vdpauinfo-1.4-1.fc33.x86_64 to vdpauinfo-1.0-16.fc33.x86_64. The behavior was the same.
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
@stan Are you using Wayland with vdpau ? (I've missed that you are using libvdpau-va-gl wrapper), so it could be possible that the issue is there. (is it unmodified fedora's libvdpau-va-gl ?) and why are you using vdpau when native vaapi should be used instead ? Please re-open if you can reproduce with newer Fedora. Thanks.
Nicolas, I'm not using Wayland. Instead, I'm using the xfce spin, with Xorg. In a sense, this problem is fixed, because although the version of vdpauinfo is still 1.4-1, there is no longer a segmentation fault, but rather the following error, which I've seen on my other systems: X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 152 (GLX) Minor opcode of failed request: 5 (X_GLXMakeCurrent) Serial number of failed request: 48 Current serial number in output stream: 48
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.