Version-Release number of selected component: gstreamer1-1.9.1-1.fc24 Additional info: reporter: libreport-2.7.1 backtrace_rating: 4 cmdline: /usr/libexec/gstreamer-1.0/gst-plugin-scanner -l crash_function: init_context_defaults executable: /usr/libexec/gstreamer-1.0/gst-plugin-scanner global_pid: 2577 kernel: 4.6.3-300.fc24.x86_64 pkg_fingerprint: EE78 8F49 5250 AEF3 pkg_vendor: (none) reproducible: Not sure how to reproduce the problem runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 init_context_defaults at libavcodec/options.c:142 #3 avcodec_alloc_context3 at libavcodec/options.c:163 #4 gst_ffmpeg_cfg_install_property at gstavcfg.c:732 #5 gst_ffmpegvidenc_class_init at gstavvidenc.c:225 #6 type_class_init_Wm at gtype.c:2241 #7 g_type_class_ref at gtype.c:2956 #8 gst_element_register at gstelementfactory.c:243 #9 gst_ffmpegvidenc_register at gstavvidenc.c:1015 #10 plugin_init at gstav.c:158 #11 gst_plugin_register_func at gstplugin.c:523
Created attachment 1180419 [details] File: backtrace
Created attachment 1180420 [details] File: cgroup
Created attachment 1180421 [details] File: core_backtrace
Created attachment 1180422 [details] File: dso_list
Created attachment 1180423 [details] File: environ
Created attachment 1180424 [details] File: limits
Created attachment 1180425 [details] File: maps
Created attachment 1180426 [details] File: mountinfo
Created attachment 1180427 [details] File: namespaces
Created attachment 1180428 [details] File: open_fds
Created attachment 1180429 [details] File: proc_pid_status
Created attachment 1180430 [details] File: var_log_messages
*** Bug 1357002 has been marked as a duplicate of this bug. ***
*** Bug 1358178 has been marked as a duplicate of this bug. ***
One of the dupes mentions that reinstalling ffmpeg fixed the crash, another mentioned removing gstreamer1-libav
The removal of gstreamer1-libav fixed the problem in my case. As soon as I reinstall it, the problem comes again, but my gstreamer1-libav library comes from rpmfusion: gstreamer1-libav x86_64 1:1.8.2-1.fc24 fedora-HandBrake 229 k Maybe thats the real reason.
Installing ffmpeg or gstreamer-ffmpeg in my F24 does not have any effect. Only gstreamer1-libav reproduces the problem.
Olivier, according to the repo name of your gstreamer1-libav package, it does not come from rpmfusion, but from negativo17's repositories. That's exactly the same repo I used when seeing this crash. However, I uninstalled all the ffmpeg/gstreamer packages and then installed them again (and rebooted a few times in the meantine), and virt-manager no longer crashes for me. I have the same gstreamer1-libav version as you do, from same repo. I don't know how to explain that.
I'm not able to avoid the crashes if lib installed. Will try that later and if I got any new info I report it here. Thanks for helping
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.