Hi,
On Fri, Nov 24, 2017 at 03:40:15PM +, James Cowgill wrote:
> Antoni, you should be able to fix your specific problem by upgrading all
> the ffmpeg related packages (libav* etc) to 3.4.
If I'm not wrong, at the moment of reporting I had installed this
versions:
ffmpeg
Hi,
On 24/11/17 15:40, James Cowgill wrote:
> Control: severity -1 grave
> Control: retitle -1 libavutil55: ABI broken by "add vector_dmac_scalar()"
> Control: forwarded -1 https://trac.ffmpeg.org/ticket/6861
> Control: tag -1 - moreinfo
> Control: found -1 7:3.4-1
>
> On 24/11/17 14:46, Carl
Control: severity -1 grave
Control: retitle -1 libavutil55: ABI broken by "add vector_dmac_scalar()"
Control: forwarded -1 https://trac.ffmpeg.org/ticket/6861
Control: tag -1 - moreinfo
Control: found -1 7:3.4-1
On 24/11/17 14:46, Carl Eugen Hoyos wrote:
> Hi!
>
> I created FFmpeg ticket #6861,
Hi!
I created FFmpeg ticket #6861, thank you for the report!
https://trac.ffmpeg.org/ticket/6861
Carl Eugen
Control: tags -1 moreinfo
Hi,
On 24/11/17 13:38, Antoni Villalonga wrote:
> Package: libavutil55
> Version: 7:3.4-3
> Severity: normal
>
> Dear Maintainer,
>
> After upgrade to sid ffmpeg tools start to segfault like this:
> [370710.121304] read_thread[9924]: segfault at 7feff8051ce0 ip
>
Package: libavutil55
Version: 7:3.4-3
Severity: normal
Dear Maintainer,
After upgrade to sid ffmpeg tools start to segfault like this:
[370710.121304] read_thread[9924]: segfault at 7feff8051ce0 ip 7fef350b7943
sp 7fef07386ea8 error 4 in libavutil.so.55.78.100[7fef35069000+67000]
After
6 matches
Mail list logo
