Bug#923494: Please Recommend and dlopen libsdl2 rather than depending on it

> Am 21.07.2019 um 21:58 schrieb Josh Triplett : > >> On July 21, 2019 11:38:03 AM PDT, James Cowgill wrote: >> Hi, >> >>> On 12/03/2019 12:44, Reinhard Tartler wrote: >>> On Tue, Mar 12, 2019 at 8:36 AM Carl Eugen Hoyos >> <mailto:

Bug#923494: Please Recommend and dlopen libsdl2 rather than depending on it

2019-03-12 18:48 GMT+01:00, Josh Triplett : > On Tue, Mar 12, 2019 at 08:25:55AM -0400, Reinhard Tartler wrote: >> I think this should address the issue. Any objections to this approach? > > This would work perfectly for me, and I would then avoid installing > ffplay on my servers. I was

Bug#923494: Please Recommend and dlopen libsdl2 rather than depending on it

2019-03-12 13:25 GMT+01:00, Reinhard Tartler : > In a headless installation that is used for transcoding and streaming, > such dependencies, like on X11, wayland, etc. may not be desirable. Funny that you mention X11 and wayland: Both are still dependencies of FFmpeg after your patch, no?

Bug#923494: Please Recommend and dlopen libsdl2 rather than depending on it

Please show the dependencies of (at least) libavutil and libavcodec with your approach and maybe compare them to what sdl needs: While the list may become smaller I wonder if it this would really solve the described issue.

Bug#923494: Please Recommend and dlopen libsdl2 rather than depending on it

> What might work is disabling the avdevice outdev AND > moving 'ffplay' to its own binary package. Before suggesting this, I would prefer the OP to test. I still do not entirely believe that this fixes his issue. Carl Eugen

Bug#923494: Please Recommend and dlopen libsdl2 rather than depending on it

2019-03-10 23:21 GMT+01:00, Reinhard Tartler : > On Sat, Mar 9, 2019 at 2:51 PM Carl Eugen Hoyos wrote: > >> Could you test the configure option "--disable-outdev=sdl2"? >> Your report indicates it should fix your issue, I am not convinced but >> if it fixes

Bug#923494: Please Recommend and dlopen libsdl2 rather than depending on it

Hi! Could you test the configure option "--disable-outdev=sdl2"? Your report indicates it should fix your issue, I am not convinced but if it fixes your issue, Debian should consider using it as the device is mostly a (cheap) debug feature. Please report back, Carl Eugen

Bug#904052: ffmpeg: FTBFS on hurd-i386: wrong value for --target-os at configure

Hi! I believe the correct fix is to completely remove --target-os from the configure line, it should only be used for cross-compilation. Carl Eugen

Bug#493705: FFmpeg uses text relocations on i386

(Since two bugs were reopened and the status was set to "forwarded":) Note that there will definitely be no "fix" within FFmpeg, simply because the FFmpeg developers do not believe that there is a bug that can be fixed. If Debian believes there is an issue, it can be fixed quickly: Just add

Bug#884232: ffmpeg: CVE-2017-17555

This is not a bug in FFmpeg: aubio initializes libswresample with 2 channels and then passes data that contains just one channel. That cant really work or how could it ? swresample has no knowledge about what is in the array except what it is told There are multiple ways to

Bug#882384: ffmpeg: Gratuitous valgrind log

2017-11-25 5:41 GMT+01:00 Kingsley G. Morse Jr. : > Hi Carl, > >> Nearly all messages seem to relate to melt, not FFmpeg. > > Thanks for your informed thoughts. > >> Can you reproduce any issues with ffmpeg (the executable)? >> >> The crc issue surprises me a little: Can you

Bug#882598: libavutil55: segfault after upgrade

Hi! I created FFmpeg ticket #6861, thank you for the report! https://trac.ffmpeg.org/ticket/6861 Carl Eugen

Bug#882384: ffmpeg: Gratuitous valgrind log

Hi! Nearly all messages seem to relate to melt, not FFmpeg. Can you reproduce any issues with ffmpeg (the executable)? The crc issue surprises me a little: Can you produce different output files if you use the valgrind option --malloc-fill? Carl Eugen

Bug#872503: ffmpeg: armhf SIGBUS in ff_diff_pixels_armv6 running winff autopkgtest

Michael has committed a patch that is supposed to fix this crash: http://ffmpeg.org/pipermail/ffmpeg-cvslog/2017-August/108709.html Thank you for the useful report! Carl Eugen

Bug#872503: ffmpeg: armhf SIGBUS in ff_diff_pixels_armv6 running winff autopkgtest

I suspect this is a regression since 31326143 (when the function was added). Carl Eugen

Bug#872503: ffmpeg: armhf SIGBUS in ff_diff_pixels_armv6 running winff autopkgtest

Hi! Is this issue still reproducible with current FFmpeg git head? Carl Eugen

Bug#872517: ffmpeg: CVE-2017-7206: heap-based buffer over-read in embed libav

Hi! > the following vulnerability was published for libav > (which is embed in ffmpeg). This is not true. Please provide valgrind or asan output (both show the issue easily for some avconv releases) for any affected FFmpeg version or close this issue. Carl Eugen

Bug#856100: libav-tools : concat Protocol not found

Hi! Several similar bugs (features missing from avconv in Debian) were closed as "fixed" when Debian switched to FFmpeg: How is this report different? As an alternative, this could be reassigned to "libav-doc". Thank you, Carl Eugen

Bug#839941: whishlist ffmpeg

Hi! I wonder if "confirmed" is really the right status: There is absolutely no way that this can be fixed within Debian, the license of the necessary header files is certainly not compatible with any open-source license. I suggest to close as wont-fix or invalid. Carl Eugen

Bug#851026: ffmpeg: FTBFS: ffconf.bVIjAhhQ.c:2: undefined reference to `dlopen'

The relevant lines in the build log are afaict: src/libavformat/chromaprint.c: In function 'write_packet': src/libavformat/chromaprint.c:113:1: error: control reaches end of non-void function [-Werror=return-type] } ^ The function looks like this: static int write_packet(AVFormatContext *s,

Bug#831591: ffmpeg: kodi crash

Hi Bálint! > I went throught the unclassified bugs and set the > proper state to help tracking them. This bug (#831591) and #832364 contain neither backtrace nor bisect. Note that they most likely have to be fixed in Kodi, FFmpeg will (afaict) not break ABI once more for the 3.1 release

Bug#831591: ffmpeg: kodi crash

Hi! > Knowing what broke could be > interesting for FFmpeg devs It would most likely be even more interesting for the Kodi developers: We currently assume that there is an unknown bug in Kodi... > > Slightly related: More that half of the open tickets > > concerning FFmpeg in Debian either

Bug#831591: ffmpeg: kodi crash

Hi Bálint! > I don't have the test file. In this case I suggest to close the relevant tickets: We cannot reproduce, there is no backtrace and no bisect. Since FFmpeg has made three point releases with the ABI that is apparently incompatible with (old) Kodi, it is very unlikely that it will be

Bug#831591: ffmpeg: kodi crash

Hi! > 2016-08-24 22:55 GMT+02:00 Carl Eugen Hoyos <ceho...@ag.or.at>: > > > > First, please understand that so far, no ABI breakage between > > FFmpeg 3.0 and FFmpeg 3.1 was found, only the usage of > > non-public api (that we decided to work-around for 3.1.1). &

Bug#831591: ffmpeg: kodi crash

Hi! First, please understand that so far, no ABI breakage between FFmpeg 3.0 and FFmpeg 3.1 was found, only the usage of non-public api (that we decided to work-around for 3.1.1). Am I correct that no backtrace was provided for this issue? But even with a backtrace, I fear a bisect may be

Bug#833722: ffmpeg: can hear music but no sound/dialogs from movie

Hi! How can the issue you see be reproduced? Is it a regression? The console output does not necessarily look FFmpeg-related: Why do you believe that the issue can be fixed within FFmpeg? Carl Eugen

Bug#591904: libavcodec52: text relocations on AMD64

Hi! This bug was fixed upstream some time before the issue was reported to Debian: http://git.videolan.org/?p=ffmpeg.git;a=commitdiff;h=3d05c1fb Please reassign or close, Carl Eugen

Bug#831529: libavcodec57: broken option parsing with LANGs with decimal mark different from .

Hi! Please someone test attached patch, I cannot reproduce on any of my systems. Thank you, Carl Eugen diff --git a/libavcodec/vaapi_encode_h264.c b/libavcodec/vaapi_encode_h264.c index 979cf37..5bed4e4 100644 --- a/libavcodec/vaapi_encode_h264.c +++ b/libavcodec/vaapi_encode_h264.c @@ -1323,10

Bug#831909: gstreamer coredumps when playing wavs since the libavcodec upgrade

Thank you for the backtrace! Could you check if removing some or all entries from vaapi_encode_h264_defaults in libavcodec/vaapi_encode_h264.c fixes the issue? I was unable to quickly find the vaapi source file containing the option strings and I don't have a cpu with vaapi capabilities.

Bug#831909: gstreamer coredumps when playing wavs since the libavcodec upgrade

If the issue is reproducible, please someone test if it disappears once you recompile GStreamer against the installed libavcodec headers.

Bug#831591: ffmpeg: kodi crash

Kodi reports "FFmpeg version: 3.0.1-3": Could somebody test if the crash disappears after Kodi gets recompiled against current FFmpeg?

Bug#591904: libavcodec52: text relocations on AMD64

Is this still reproducible? Why is this an issue? I don't remember that this was ever reported upstream (text relocations on x86-32 are reported on a regular basis). Carl Eugen

Bug#493705: ffmpeg-debian: Libraries have text relocations

Same as for #528080: This will not be fixed in FFmpeg upstream, so I suggest to close as wont-fix. Carl Eugen

Bug#528080: ffmpeg-debian: ffmpeg still has shlib-with-non-pic-code lintian errors

Different FFmpeg developers have explained repeatedly (including recently) that this will not be fixed within FFmpeg, so I suggest to close this bug report as wont-fix. Carl Eugen

Bug#624436: libavcodec52: Fails to read an ogg video (DRI failure)

This bug report looks incomplete: No backtrace, disassembly and register dump and no sample: Please close. Carl Eugen

Bug#591832: mplayer: hangs on playing ogv (vp3) video with "Invalid frame duration value"

I cannot reproduce this issue with current MPlayer, I suspect this was fixed years ago: Please close this ticket. Carl Eugen

Bug#677035: libavcodec52: SEGV when encoding video

This issue was fixed five years ago in FFmpeg, please close this bug.

Bug#609271: segfault when loading some jpeg files

Please close this ticket as no sample was ever provided. Carl Eugen

Bug#625944: libavcodec52: JPEG produced with Intel JPEG lib loaded upside-down

This issue was fixed five years ago in FFmpeg, please close. Carl Eugen

Bug#797965: bs1770gain somehow "destroys" gapless playback on (at least) lame encoded MP3s

Hi! If you want me to forward this bug to other FFmpeg developers, please: * Provide sample(s) that allow to reproduce the issue and * The ffmpeg command line that allows to reproduce the issue together with the complete, uncut console output and * explain what is wrong with the output file.

Bug#823098: ffmpeg: autopkgtests failing: aac probing failed

Hi! I sent a patch that probably fixes this issue, very short transport streams were never auto-detected by FFmpeg. http://ffmpeg.org/pipermail/ffmpeg-devel/2016-May/193698.html Possible workarounds are to increase the audio length with "sine=d=0.2" or to set an explicit audio bitrate of 128k

Bug#810224: /usr/bin/avconv: ogg format: unable to use pass and quality? options together

On Friday 26 February 2016 10:42:14 pm you wrote: > Hi Carl, > > On Thu, 25 Feb 2016 13:55:52 +0100 Carl Eugen Hoyos <ceho...@ag.or.at> > > wrote: > > Hi! > > > > When encoding with FFmpeg, you can either use fixed quality or fixed > > bitrate (size),

Bug#797963: bs1770gain: support writing Apple SoundCheck tags

Hi! Please provide a sample so I can open an enhancement request in the FFmpeg bug tracker. Thank you, Carl Eugen

Bug#811519: vlc: avio plugin leaks file content

Can this bug be closed if no additional information gets added? Thank you, Carl Eugen

Bug#797965: bs1770gain somehow "destroys" gapless playback on (at least) lame encoded MP3s

Hi! If I understand correctly, no sample and no command line including complete, uncut console output was ever provided for this bug report. If this is correct, please close as needs-more-information. Thank you, Carl Eugen

Bug#819266: ffmpeg: rtmp is broken

On Friday 25 March 2016 07:19:35 pm you wrote: > Package: ffmpeg > Version: 7:2.8.6-1+b2 > Severity: normal > something about rtmp is broken in ffmpeg as shipped in Debian. > For example, the Revision RTMP streams > do not work in either MPV or VLC. >

Bug#810224: /usr/bin/avconv: ogg format: unable to use pass and quality? options together

Hi! When encoding with FFmpeg, you can either use fixed quality or fixed bitrate (size), if you decide to use fixed bitrate, two-pass encoding improves the output quality. It makes no sense to use two-pass constant quality encoding, the result of using two contradicting options is undefined.

Bug#815673: ffmpeg: VP9 seek broken in ffplay

On Tuesday 23 February 2016 03:43:50 pm you wrote: > I have encoded a video as VP9 using ffmpeg with the following settings > and I am unable to seek forward in the video (tested with mpv and > ffplay). This bug in libvpx is being fixed by setting a more useful default for maximum key frame

Bug#814807: ffmpeg: FTBFS on mips

Hi! I am looking at http://git.videolan.org/?p=ffmpeg.git;a=shortlog;h=refs/tags/n2.8.6 but I don't see a commit that may have affected roq audio encoding or muxing. Are you able to test 2.8.5 with gcc-5_5.3.1-7 or 2.8.6 with gcc-5_5.3.1-6? Carl Eugen

Bug#809955: mplayer: FTBFS with libpng16

Hi! Please just remove the build dependency for libpng from MPlayer: There is no file for which the libpng decoder is used by default when running MPlayer and the existing default decoder ffpng is supposed to support more files than MPlayer's libpng decoder. Carl Eugen

Bug#798189: rtmp inside m3u don't supported anymore

Hi! I believe this is FFmpeg ticket #4797, thank you for the sample CNN.m3u that I attached there! https://trac.ffmpeg.org/ticket/4797 The samples WTV-9.m3u and twIT.m3u work fine here, I cannot reproduce an issue for them. Carl Eugen

Bug#798189: rtmp inside m3u don't supported anymore

Hi! > I have widely used m3u playlists contained http live streams as well as > rtmp ones. But after upgrading from 6:11.4-2 to 7:2.7.2-2 version only http > supported How can I reproduce this issue? Carl Eugen

Bug#789254: This sample seems not to be processable by FFmpeg

Hi! On Mon, 22 Jun 2015, Peter Belkner wrote: if (0!=*got_packet) { av_packet_rescale_ts(pkt,cc-time_base,st-time_base); + // where do the magic factor 0.5 come from? + pkt-dts=1; + pkt-pts=1; + pkt-duration=1; if (ffsox_stream_interleaved_write(so,pkt)0) {

Bug#789254: This sample seems not to be processable by FFmpeg

On Sunday 21 June 2015 10:28:55 pm Peter Belkner wrote: What BS1770GAIN does is best approximated by the following FFmpeg command (copying the video stream, transcoding the audio stream into FLAC and muxing both into a MKV container): $ ffmpeg -i sample/20030213-cvs.mpeg -vcodec copy

Bug#692876: Debian bug report 692876

Hi! On Mon, 18 Mar 2013, Paul Gevers wrote: On 18-03-13 00:53, Carl Eugen Hoyos wrote: On 17-03-13 10:33, Carl Eugen Hoyos wrote: I would like to test, could you provide the sample test.avi ? http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=5;filename=test.avi;att=1;bug=692876 I tried