The dpkg history log contains:
Start-Date: 2017-01-06 21:09:48
Commandline: aptdaemon role='role-upgrade-system' sender=':1.77'
Install: [...]
Error: Sub-process /usr/bin/dpkg exited unexpectedly
End-Date: 2017-01-06 21:11:03
This looks like dpkg crashed, which would explain why libavformat is
Attached is a debdiff. (git repo is at [1])
Testing performed (in a xenial chroot):
* build including test suite works
* installation works
* upgrade works
* autopkgtests pass
1: https://anonscm.debian.org/cgit/pkg-
multimedia/ffmpeg.git/log/?h=xenial
** Patch added: "debdiff for 2.8.11"
Attached is a debdiff. (git repo is at [1])
Testing performed (in a xenial chroot):
* build including test suite works
* installation works
* upgrade works
* autopkgtests pass
1: https://anonscm.debian.org/cgit/pkg-
multimedia/ffmpeg.git/log/?h=xenial
** Patch added: "debdiff for 3.0.7"
*** This bug is a security vulnerability ***
Public security bug reported:
FFmpeg 2.8.11 fixing a number of crashes and other potentially security
relevant issues was released.
This includes fixes for CVE-2016-9561, CVE-2017-5024 and CVE-2017-5025.
>From the upstream Changelog:
version 2.8.11
*** This bug is a security vulnerability ***
Public security bug reported:
FFmpeg 3.0.7 fixing a number of crashes and other potentially security
relevant issues was released.
This includes fixes for CVE-2016-9561 (3.0.6) and
CVE-2017-5024/CVE-2017-5025 (3.0.7).
>From the upstream Changelog:
This has already been reported before (https://bugs.debian.org/786670) and my
opinion hasn't changed:
I don't think these external libraries increase the attack surface much.
The bug I mentioned was closed by disabling the two external libraries that
turned out to be problematic, libopenjpeg
Your logs show that while you were trying to install chromium,
unattended-upgrades was running in the background and that failed, so the
failure is unrelated to chromium.
The unattended-upgrades update was also tried on the preceding days and also
failed, but unfortunately it is not clear from
There is no package 'ffmpeg-20090322-i486' in Ubuntu 16.10.
Hence I'm closing this bug as invalid.
Just remove that package with 'sudo apt-get purge ffmpeg-20090322-i486' and
your problem will be gone.
** Changed in: ffmpeg (Ubuntu)
Status: New => Invalid
--
You received this bug
Debdiff mentioning the CVEs in the changelog is attached.
** Patch added: "debdiff for 2.8.10"
https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1647226/+attachment/4790034/+files/ffmpeg_2.8.10.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
For 2.8.9 there are now CVEs available [1]:
CVE-2016-7502, CVE-2016-7785, CVE-2016-7905, CVE-2016-7562
1: https://ffmpeg.org/security.html
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-7502
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-7562
**
CVEs aren't available yet, but this fixes important security issues like:
https://trac.ffmpeg.org/ticket/5992
https://trac.ffmpeg.org/ticket/5994
** Bug watch added: FFmpeg Trac bug tracker #5992
https://trac.ffmpeg.org/ticket/5992
** Bug watch added: FFmpeg Trac bug tracker #5994
Attached is a debdiff. (git repo is at [1])
Testing performed (in a yakkety chroot):
* build including test suite works
* installation works
* upgrade works
* autopkgtests pass
1: https://anonscm.debian.org/cgit/pkg-
multimedia/ffmpeg.git/log/?h=yakkety
** Patch added: "debdiff for 3.0.5"
*** This bug is a security vulnerability ***
Public security bug reported:
FFmpeg 3.0.5 fixing a number of crashes and other potentially security
relevant issues was released.
This includes fixes for CVE-2016-5199 (3.0.4) and
CVE-2016-6164/CVE-2016-6881 (3.0.3).
>From the upstream Changelog:
There has been another release fixing bugs in network code:
version 2.8.10
- avformat/http: Match chunksize checks to master..3.0
- Changelog: fix typos
- ffserver: Check chunk size
- Avoid using the term "file" and prefer "url" in some docs and comments
- avformat/rtmppkt: Check for packet size
Attached is a debdiff. (git repo is at [1])
Testing performed (in a xenial chroot):
* build including test suite works
* installation works
* upgrade works
* autopkgtests pass
1: https://anonscm.debian.org/cgit/pkg-
multimedia/ffmpeg.git/log/?h=xenial
** Patch added: "debdiff for 2.8.9"
*** This bug is a security vulnerability ***
Public security bug reported:
FFmpeg 2.8.9 fixing a number of crashes and other potentially security
relevant issues was released.
>From the upstream Changelog:
version 2.8.9
- avcodec/flacdec: Fix undefined shift in decode_subframe()
-
I've just verified that ffmpeg 3.2-2 from zesty starts fine after installation
in a minimal chroot.
Your problem is caused by third-party libraries.
To identify the problematic one, try running the following command:
$ for lib in $(ldd /usr/bin/ffmpeg | sed 's/.*=> \(.*\) (.*/\1/'); do [ -e
This looks like another problem in software-center/aptdaemon, similar to
#1509169 and #1511571. Thus I'm reassinging the bug.
** Package changed: ffmpeg (Ubuntu) => aptdaemon (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1511571 ***
https://bugs.launchpad.net/bugs/1511571
** This bug has been marked a duplicate of bug 1511571
package libavcodec-ffmpeg56 (not installed) failed to install/upgrade:
conflicting packages - not installing libavcodec-ffmpeg56:amd64
--
You
ffmpeg was synced from Debian, so it uses openjpeg2 now also in Ubuntu.
** Changed in: ffmpeg (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1626220
Title:
A new ffmpeg version was synced from Debian, so this bug can be closed.
** Changed in: ffmpeg (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628595
Title:
Sorry about that. I mistakenly thought this fix was included in 3.1, but
it was only committed a few days after that was released.
I've cherry-picked it for the next Debian release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
version 7:3.0.2-1ubuntu3:
ffmpeg (7:3.1.4-1) unstable; urgency=medium
[ Ondřej Nový ]
* Disable librtmp support, because the built-in RTMP support is better.
[ Andreas Cadhalpun ]
* Import new upstream bugfix release 3.1.4.
- Fixes CVE-2016-7122, CVE-2016-7450, CVE-2016-7502, CVE-2016-7555
Attached is a debdiff. (git repo is at [1])
Testing performed (in a xenial chroot):
* build including test suite works
* installation works
* upgrade works
* autopkgtests pass
1: https://anonscm.debian.org/cgit/pkg-
multimedia/ffmpeg.git/log/?h=xenial
** Patch added: "debdiff for 2.8.8"
*** This bug is a security vulnerability ***
Public security bug reported:
FFmpeg 2.7.6 fixing a number of crashes and other potentially security
relevant issues (including CVE-2016-2213) was released.
>From the upstream Changelog:
version 2.7.6
- avcodec/jpeg2000dec: More completely check
Attached is a debdiff. (git repo is at [1])
Testing performed (in a wily chroot):
* build including test suite works
* installation works
* upgrade works
* autopkgtests pass
1: https://anonscm.debian.org/cgit/pkg-multimedia/ffmpeg.git/log/?h=wily
** Patch added: "debdiff for 2.7.6"
As I understand it vivid will be EOL'ed tomorrow, so I don't think it'll need
an update for this.
However, I could prepare a debdiff for 2.5.11 if that would be useful.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Filipp, if an issue is fixed in libavformat it doesn't affect programs
using this dynamic library (like mplayer) anymore, once they have been
restarted after libavformat has been upgraded.
To fix this issue in xenial, 2.8.5-1 needs to be merged from
Debian/unstable.
Attached is a debdiff for
CVE-2016-1897 (concat) and CVE-2016-1898 (subfile) were assigned to this
bug, which (among other potentially security relevant issues) is fixed
in FFmpeg 2.7.5 (the lines below starting with avformat/hls refer to
this bug).
Attached is a debdiff. (git repo is at [1])
Testing performed (in a wily
A few more CVEs were assigned to fixes in this update:
CVE-2015-8661, CVE-2015-8662 and CVE-2015-8663
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2015-8661
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2015-8662
** CVE added: http://www.cve.mitre.org/cgi-
Attached is a debdiff. (git repo is at [1])
Testing performed (in a wily chroot):
* build including test suite works
* installation works
* upgrade works
* autopkgtests pass
1: https://anonscm.debian.org/cgit/collab-maint/ffmpeg.git/log/?h=wily
** Patch added: "debdiff for 2.7.4"
*** This bug is a security vulnerability ***
Public security bug reported:
Fmpeg 2.7.4 fixing a number of crashes and other potentially security
relevant issues (including CVE-2015-6761) was released.
>From the upstream Changelog:
version 2.7.4
- nuv: sanitize negative fps rate
- rawdec: only
*** This bug is a security vulnerability ***
Public security bug reported:
FFmpeg 2.5.9 fixing a number of crashes and other potentially security relevant
issues (including CVE-2015-6761, CVE-2015-8216, CVE-2015-8219, CVE-2015-8363,
CVE-2015-8364 and CVE-2015-8365) was released.
>From the
Attached is a debdiff. (git repo is at [1])
Testing performed (in a vivid chroot):
* build including test suite works
* installation works
* upgrade works
* no regressions in the autopkgtests from 2.8.3-1
1: https://anonscm.debian.org/cgit/collab-maint/ffmpeg.git/log/?h=vivid
** Patch
*** This bug is a duplicate of bug 1511571 ***
https://bugs.launchpad.net/bugs/1511571
** This bug has been marked a duplicate of bug 1511571
package libavcodec-ffmpeg56 (not installed) failed to install/upgrade:
conflicting packages - not installing libavcodec-ffmpeg56:amd64
--
You
*** This bug is a security vulnerability ***
Public security bug reported:
FFmpeg 2.7.3 fixing a number of crashes and other potentially security
relevant issues (including CVE-2015-8216, CVE-2015-8217 and
CVE-2015-8219) was released.
>From the upstream Changelog:
version 2.7.3:
- rtmpcrypt:
** Description changed:
FFmpeg 2.7.3 fixing a number of crashes and other potentially security
relevant issues (including CVE-2015-8216, CVE-2015-8217 and
CVE-2015-8219) was released.
From the upstream Changelog:
version 2.7.3:
- rtmpcrypt: Do the xtea decryption in little
Attached is a debdiff. (git repo is at [1])
Testing performed (in a wily chroot):
* build including test suite works
* installation works
* upgrade works
* autopkgtests pass
1: https://anonscm.debian.org/cgit/collab-maint/ffmpeg.git/log/?h=wily
** Patch added: "debdiff for 2.7.3"
*** This bug is a duplicate of bug 1511571 ***
https://bugs.launchpad.net/bugs/1511571
If you can figure out how to reproduce this bug in a freshly installed
virtual machine, that would probably help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1511571 ***
https://bugs.launchpad.net/bugs/1511571
Thanks for trying to find a way to reproduce this.
I'm not sure what your question is about, but the important point is 'freshly
installed', so that it can be easily reproduced by everyone.
If you have a
*** This bug is a duplicate of bug 1511571 ***
https://bugs.launchpad.net/bugs/1511571
** This bug has been marked a duplicate of bug 1511571
package libavcodec-ffmpeg56 (not installed) failed to install/upgrade:
conflicting packages - not installing libavcodec-ffmpeg56:amd64
--
You
A small clarification: the SIMPLE-ARM implementation can also be
selected at runtime, e.g. with the '-idct simplearm' option. That's
mainly useful for debugging purposes, though.
Regarding the binutils bug:
Attached testcase test.S doesn't require compiling ffmpeg, but simply:
$ gcc -g -c -o
I can't imagine that Ubuntu freezing is an ffmpeg bug.
I guess you meant to file a bug against linux, so I'm reassigning this bug
there.
But for this bug report to be useful you have to provide more information,
at least excerpts of /var/log/syslog from the time, when the freezing happens.
**
Debugging the failing command 'libavcodec/dct-test -i' with gdb shows
that this is clearly a binutils bug.
* Working with binutils 2.25.1-6ubuntu1:
Breakpoint 1, __end_a_evaluation () at libavcodec/arm/simple_idct_arm.S:239
239 ldr r10, =MASK_MSHW @ R10=0x
(gdb) disas
So, apparently, the Software Center can't deal with conflicts correctly, thus
I'm reassigning this bug to it.
That libavcodec-ffmpeg56 and libavcodec-ffmpeg-extra56 conflict is intentional
and certainly not a bug.
** Package changed: ffmpeg (Ubuntu) => software-center (Ubuntu)
--
You
This is a duplicate of bug #1458359 and just as invalid.
** Changed in: ffmpeg (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509960
Title:
package ffmpeg
The transition tracker shows that all rebuilds have been done by now, so
I'm closing this bug.
** Changed in: ffmpeg (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
libavcodec-ffmpeg56 intentionally conflicts with libavcodec-ffmpeg-extra56.
I'm not sure what you did, but according to DpkgHistoryLog.txt it involves
aptdaemon, which seems to not handle conflicts correctly.
But since this is definitely not a bug in libavcodec-ffmpeg56, I'm reassigning
this
Attached is a debdiff. (git repo is at [1])
Testing performed (in a vivid chroot):
* build including test suite works
* installation works
* upgrade works
* no regressions in the autopkgtests from 2.7.2-1
1: https://anonscm.debian.org/cgit/collab-maint/ffmpeg.git/log/?h=vivid
** Patch
*** This bug is a security vulnerability ***
Public security bug reported:
FFmpeg 2.5.8 fixing a number of crashes and other potentially security relevant
issues was released.
From the upstream Changelog:
version 2.5.8
- snow: remove an obsolete av_assert2
- huffyuvdec: validate image size
-
Then please post the full command line and it's output.
The libx264 encoder works just fine, e.g.:
$ ffmpeg -f lavfi -i testsrc=d=1 -vcodec libx264 output.mp4
ffmpeg version 2.5.7-0ubuntu0.15.04.1 Copyright (c) 2000-2015 the FFmpeg
developers
built with gcc 4.9.2 (Ubuntu 4.9.2-10ubuntu13)
ffmpeg version 2.6.2 Copyright (c) 2000-2015 the FFmpeg developers
This version of ffmpeg does not come from Ubuntu, hence closing the bug as
invalid.
Please report any problems with it wherever you got it from.
The ffmpeg version in vivid is currently 2.5.7-0ubuntu0.15.04.1.
If you want to
Unknown encoder 'lib264'
Looks like you missed the 'x' between 'lib' and '264'.
Using the actual libx264 encoder works fine.
Thus closing this bug as invalid.
** Changed in: ffmpeg (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
There is no ffmpeg package in Ubuntu 14.04 LTS Trusty Tahr.
You're trying to install ffmpeg 4:0.5.9-0ubuntu0.10.04.3 from Ubuntu
10.04 LTS Lucid Lynx in trusty, so you should expect problems.
This problem does not exist in the ffmpeg package in Ubuntu 15.04 Vivid
Vervet.
Thus this bug is
*** This bug is a security vulnerability ***
Public security bug reported:
FFmpeg 2.5.7 fixing a number of crashes and other potentially security relevant
issues was released.
From the upstream Changelog:
version 2.5.7
- avformat/nutdec: Fix recovery when immedeately after seeking a failure
Attached is a debdiff. (git repo is at [1])
Testing performed (in a vivid chroot):
* build including test suite works
* installation works
* upgrade works
* results of autopkgtests from 2.6.3-1 (in Debian) are unchanged from 2.5.6
1:
As Carl Eugen explained this bug is invalid.
You can use the native AAC encoder and report specific bugs if you
encounter any issues with it.
** Changed in: ffmpeg (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Hi,
On Wed, 29 Apr 2015, maurizio de santis wrote:
Fraunhofer FDK AAC is the only decent aac encoder supported by ffmpeg, and
aac encoding is crucial for web media encodings, which are tipically
(unfortunately) mp4 with h264/aac encodings.
As Carl Eugen already explained, we can't enable the
As vivid is released now, this update needs to go through vivid-security.
Attached is an updated debdiff. (git repo is at [1])
Testing performed (in a vivid chroot):
* build including test suite works
* installation works
* upgrade works
* running the autopkgtests from 2.6.2-1 (in Debian)
In the meanwhile FFmpeg 2.5.6 with some more fixes has been released.
version 2.5.6
- avcodec/atrac3plusdsp: fix on stack alignment
- ac3: validate end in ff_ac3_bit_alloc_calc_mask
- aacpsy: avoid psy_band-threshold becoming NaN
- aasc: return correct buffer size from aasc_decode_frame
-
*** This bug is a security vulnerability ***
Public security bug reported:
FFmpeg 2.5.5 fixing a number of crashes and other potentially security relevant
issues was released.
From the upstream Changelog:
version 2.5.5:
- vp9: make above buffer pointer 32-byte aligned.
- avcodec/dnxhddec:
. (Closes: #776649)
* Fix dep5-copyright-license-name-not-unique lintian warnings.
-- Andreas Cadhalpun andreas.cadhal...@googlemail.com Sat, 14 Feb
2015 23:14:52 +0100
** Affects: ffmpeg (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because
There is now a -hide_banner option that hides the startup messages, see:
https://trac.ffmpeg.org/ticket/3246
** Bug watch added: FFmpeg Trac bug tracker #3246
https://trac.ffmpeg.org/ticket/3246
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
There is no ffmpeg package in Ubuntu 14.04 and the ffmpeg package in
Ubuntu 15.04 doesn't have this problem. Thus this bug is invalid. Please
report the problem wherever you obtained your ffmpeg package from.
** Changed in: ffmpeg (Ubuntu)
Status: Confirmed = Invalid
--
You received this
** Changed in: ffmpeg (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/930040
Title:
ffmpeg shows too much output at start up
To manage
This problem does not exist anymore in Ubuntu Gnome 13.10 with gnome-shell
3.8.4-0ubuntu5.
The bug can be closed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1173981
Title:
gnome-shell crashes
Public bug reported:
I am using Ubuntu 13.04 with Gnome 3.8 from the PPA.
How to reproduce the bug:
- Go to the gnome-control-center, accessibility, zoom, options.
- Turn the zoom on.
- Change the zoom factor to 6,00.
- Gnome-shell will crash and even a reboot does not bring it back. Only
67 matches
Mail list logo
