On 2017-07-22 14:40:48, Vadim Zhukov <[email protected]> wrote:
>
> Yes, I see problems, too. I suspect some problems with gstreamer,
> though - do you see gst-plugin-scanner crash when starting qutebrowser
> with --debug?
>
Unfortunatly, I don't. I ran "qutebrowser --debug" inside of a
/usr/bin/script session and the resulting output was 6,281 lines
long.
I get no hits grepping for "gst-plugin-scanner", "gst", "plugin",
"scanner", or "gstreamer".
In case it's relevant, I have the following gstreamer packages
installed:
% pkg_info -a | grep gst
clutter-gst-3.0.24 clutter GStreamer integration library
gstreamer-0.10.36p10 framework for streaming media
gstreamer-plugins-base-0.10.36p15 base elements for GStreamer
gstreamer1-1.12.2 framework for streaming media
gstreamer1-plugins-bad-1.12.2 bad elements for GStreamer
gstreamer1-plugins-base-1.12.2 base elements for GStreamer
gstreamer1-plugins-good-1.12.2 good elements for GStreamer
gstreamer1-plugins-libav-1.12.2 ffmpeg elements for GStreamer
gstreamer1-plugins-pulse-1.12.2 pulseaudio(1) element for GStreamer
gstreamer1-plugins-ugly-1.12.2 ugly elements for GStreamer
gstreamer1mm-1.8.0p2 C++ bindings for GStreamer
Is there anything else I can do to help debug this?
--
Bryan
