Red Hat Bugzilla – Bug 1286365
[abrt] libva-utils: object_heap_destroy(): vainfo killed by SIGFPE
Last modified: 2016-12-20 11:22:54 EST
Description of problem:
Simply run vainfo. Output is
libva info: VA-API version 0.38.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib64/dri/nouveau_drv_video.so
libva info: Found init function __vaDriverInit_0_38
Failed to open VDPAU backend libvdpau_nouveau.so: cannot open shared object file: No such file or directory
Floating point exception (core dumped)
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (8 frames)
#0 object_heap_destroy at object_heap.c:275
#1 destroy_heap at vdpau_driver.c:138
#3 vdpau_common_Terminate at vdpau_driver.c:159
#4 vdpau_Terminate_Current at vdpau_driver_template.h:537
#5 vdpau_Initialize_Current at vdpau_driver_template.h:563
#6 __vaDriverInit_0_38 at vdpau_driver.c:317
#7 va_openDriver at va.c:296
#8 vaInitialize at va.c:559
Potential duplicate: bug 1184785
Created attachment 1099925 [details]
Created attachment 1099926 [details]
Created attachment 1099927 [details]
Created attachment 1099928 [details]
Created attachment 1099929 [details]
Created attachment 1099930 [details]
Created attachment 1099931 [details]
Created attachment 1099932 [details]
Created attachment 1099933 [details]
Created attachment 1099934 [details]
Created attachment 1099935 [details]
Created attachment 1099936 [details]
This affects many other components. Shotwell, tracker-extract, and totem all crash with a similar backtrace when confronted with any of a wide variety of video files. This makes those components essentially unusable.
*** Bug 1278434 has been marked as a duplicate of this bug. ***
*** Bug 1279220 has been marked as a duplicate of this bug. ***
This seems to have stopped happening after installing the mesa-vdpau-drivers package, but I still should not be getting SIGFPE in other components when mesa-vdpau-drivers is not installed. If it is mandatory, it should be a mandatory dependency of the RPMs in question—otherwise everything should degrade gracefully.
yeah, but mesa-vdpau-driver is only one drivers pack (for nouveau, radeon, etc).
but not for intel and other vdpau bridge (nvidia), best is to have them installed by default to avoid to rely on weird runtime computation, but then the question become is the nouveau vaapi backend works for all card ? This is not the case for mine on f22 (it should work but crash) and f23 vdpau isn't supported on DRI3 with PRIME yet...
The other side of the problem is to have vainfo fixed when there is no or a broken backend. Can you report the problem upstream directly ?
Can you check if you can reproduce with libva-1.6.2 ?
I meant, with mesa-vdpau-drivers isn't installed ?
Currently in updates-testing
dnf updtate --enablerepo=updates-testing libva\*
I’ll try that in a week or so when I’m back at the machine—first to reproduce the original problem by removing the mesa vdpau driver, then installing the mentioned update.
Looks like I already got libva-1.6.2-1 as an update in the main updates channel. I didn’t really want to downgrade, so I did not start by reproducing the original problem with 1.6.1; instead, I just removed mesa-vdpau-driver and ran vainfo again. Sadly, the FPE still occurs.
Comments, and link to this bug, added to an existing upstream bug at https://bugs.freedesktop.org/show_bug.cgi?id=75959
Permalink to problem for 1.6.2: https://retrace.fedoraproject.org/faf/problems/bthash/?bth=9d622bbd608b0697e362e4c2124a8b50c742d7be
*** Bug 1277242 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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'
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 23 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.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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
Thank you for reporting this bug and we are sorry it could not be fixed.