[Bug 730159] Re: ffmpeg library configuration mismatch

2018-06-29 Thread Veron Rado
@John. No problem. The ffmpeg devloper's argument doesn't seem too robust. I'd guess the proposal rejection might not be set in stone. If enough people reasoned with them they might change their minds. -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 730159] Re: ffmpeg library configuration mismatch

2018-06-27 Thread JohnWashington
@Veron, yes, I'm sorry if it seemed I was critical of your help, my "Shoot the messenger" was aimed at @Reinhart who didn't bother yet (?) in 2011 to patch it. Your link to https://trac.ffmpeg.org/ticket/7211 is interesting. They make a good point, hide by default will make their job harder.

[Bug 730159] Re: ffmpeg library configuration mismatch

2018-06-27 Thread Veron Rado
Sorry, I should've checked before posting. '-show_banner' has been rejected by ffmpeg https://trac.ffmpeg.org/ticket/7211 ** Bug watch added: FFmpeg Trac bug tracker #7211 https://trac.ffmpeg.org/ticket/7211 -- You received this bug notification because you are a member of Ubuntu Bugs, which

[Bug 730159] Re: ffmpeg library configuration mismatch

2018-06-27 Thread Veron Rado
I hope you don't think I'm rejecting VanillaMozilla's insights. I'm just a user suffering from this issue too... see #13 above. I agree '-show-banner' would be preferable. Why don't you file a bug at the ffmpeg bug tracker requesting it? https://trac.ffmpeg.org/ (Leave a note here if you do.)

[Bug 730159] Re: ffmpeg library configuration mismatch

2018-06-25 Thread JohnWashington
@Veron: thank you. But, as with all workarounds, the users need to know the workaround exists. I find it very sad to see insights such as VanillaMozilla gives rejected. Shoot the messenger. @Reinhart: we have to disagree on what an "average user" is. Certainly the kind of beginner I sometimes

[Bug 730159] Re: ffmpeg library configuration mismatch

2018-06-25 Thread Veron Rado
Apparently there is a built-in workaround for this in ffmpeg since 2013! Simply use the '-hide_banner' option. I came across it here https://superuser.com/a/1045060. You are all very welcome :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed

[Bug 730159] Re: ffmpeg library configuration mismatch

2017-12-17 Thread VanillaMozilla
Please, I hope you DO fix it. I understand the reluctance to remove a needed message, but I would hope the spuriousness could be removed. Programs like ffmpeg and avconv are used simply because they are darned useful. They often accomplish in seconds what front end apps can't do at all.

[Bug 730159] Re: ffmpeg library configuration mismatch

2017-04-22 Thread Reinhard Tartler
Well, the warning is printed whenever you use a copy of the 'ffmpeg' binary with a copy of libavcodec (or any other library provided by the ffmpeg source package) that has been built with a different configuration. Which is the whole point of the 'libavcodec-extra*' packages: Enable additional

[Bug 730159] Re: ffmpeg library configuration mismatch

2017-04-22 Thread JohnWashington
I love it. #2 above: "... I didn't bother yet to patch it out." Written over 6 years ago. Brings a whole new meaning to the word "yet"! ;) And #12: "That it, people needs to..." As if the average user understands such advice, much less ever visits launchpad. Please try to make Ubuntu fit for

[Bug 730159] Re: ffmpeg library configuration mismatch

2017-04-22 Thread Veron Rado
** Changed in: ffmpeg-extra (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/730159 Title: ffmpeg library configuration mismatch To manage notifications

[Bug 730159] Re: ffmpeg library configuration mismatch

2017-04-20 Thread Veron Rado
No, that's not it. I'm on 16.10 clean install and I get the warning too. I installed: ffmpeg (version 7:3.0.5-0ubuntu0.16.10.1) and ubuntu-restricted-extras (version 65) I don't have libavcodec-ffmpeg-extra56 I have libavcodec-extra57 Example of the warning I get: $ ffmpeg ffmpeg version

[Bug 730159] Re: ffmpeg library configuration mismatch

2017-03-28 Thread dino99
That it, people needs to clean their system, purge package instead of simple removal (to avoid old settings left behind) and glance at wiki/howto/... to understand the difference between bugs.launchpad and forum. Closing again that useless report. ** Changed in: ffmpeg-extra (Ubuntu)

[Bug 730159] Re: ffmpeg library configuration mismatch

2017-03-28 Thread Cas
The solution is to remove libavcodec-ffmpeg-extra56 package, which will replace it with libavcodec-ffmpeg which stops the ffmpeg warning output. sudo apt remove libavcodec-ffmpeg-extra56 AskUbuntu References: - How to fix "library configuration mismatch":

[Bug 730159] Re: ffmpeg library configuration mismatch

2017-01-15 Thread Travisgevans
I get this, too. It *seems* to work fine anyway, but it sure looks scary. And ffmpeg is already a ridiculously verbose program as it is *without* spewing a full-page of incomprehensible gobbledegook on every single invocation. ;-) -- You received this bug notification because you are a member of

[Bug 730159] Re: ffmpeg library configuration mismatch

2016-04-25 Thread Felipe Castillo
This problem is found on the new Ubuntu 16.04 right out of the box. Tons of messages and warnings. It's annoying! This should at least be changed back to confirmed ** Changed in: ffmpeg-extra (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a

[Bug 730159] Re: ffmpeg library configuration mismatch

2016-02-03 Thread dino99
outdated report ** Changed in: ffmpeg-extra (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/730159 Title: ffmpeg library configuration mismatch To

[Bug 730159] Re: ffmpeg library configuration mismatch

2012-05-01 Thread Jonathan Harker
Bump -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/730159 Title: ffmpeg library configuration mismatch To manage notifications about this bug go to:

[Bug 730159] Re: ffmpeg library configuration mismatch

2011-10-31 Thread Jonathan Harker
The problem is that ffmpeg is spewing nearly a page-full of spurious error messages to the screen every time it is run, and/or that ffmpeg is mis-configured at build-time, and the library mismatch may be causing very difficult to find glitches or artefacts, bugs, or even outright crashes and

[Bug 730159] Re: ffmpeg library configuration mismatch

2011-04-13 Thread Tom
I believe this is not just a problem with ffmpeg-extra, but also with the libraries that don't have the -extra stuff as well. I put output in bug https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/760134, this bug was marked as a duplicate (correctly), but I think the effectivity of this needs

[Bug 730159] Re: ffmpeg library configuration mismatch

2011-03-06 Thread VanillaMozilla
The error is shown a few lines from the top. ** Attachment added: ffmpeg output https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/730159/+attachment/1889770/+files/Temp.ffmpegoutput.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 730159] Re: ffmpeg library configuration mismatch

2011-03-06 Thread VanillaMozilla
Huh? I have no idea if there's any harm, but it sounds very much like a broken program. It may not seem important, but video editing software is riddled with problems, and this adds to the already considerable noise. Among other problems, ffmpeg failed to convert files from Ogg Theora, but the

[Bug 730159] Re: ffmpeg library configuration mismatch

2011-03-06 Thread Reinhard Tartler
the message does not do any harm in ubuntu ** Package changed: ffmpeg (Ubuntu) = ffmpeg-extra (Ubuntu) ** Changed in: ffmpeg-extra (Ubuntu) Importance: Undecided = Low ** Changed in: ffmpeg-extra (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are