Bug#882598: libavutil55: segfault after upgrade
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: ffmpeg7:3.2.8-1~deb9u1 libavcodec57:amd647:3.3.4-2+b1 libavdevice57:amd64 7:3.3.4-2+b3 libavfilter6:amd647:3.3.4-2+b3 libavformat57:amd64 7:3.3.4-2+b3 libavresample3:amd64 7:3.4-3 libavutil55:amd64 7:3.4-3 libpostproc54:amd64 7:3.4-3 libswresample2:amd64 7:3.4-3 libswscale4:amd64 7:3.4-3 After upgrading all packages to 7:3.4-4 it works fine. Thanks for your time! -- Antoni Villalonga http://friki.cat/
Bug#882598: libavutil55: segfault after upgrade
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 Eugen Hoyos wrote: >> Hi! >> >> I created FFmpeg ticket #6861, thank you for the report! >> https://trac.ffmpeg.org/ticket/6861 > > That is not a nice bug. > > I'll have to think about the best way to handle this. I guess we will > have to revert the ABI breaking commit, identify the packages which are > broken (including ffmpeg itself like in this bug), add some Breaks for > them, and finally binNMU them. Alternatively we could force an ABI > transition and rebuild everything, but I'm not sure if I want to do > that (especially since we'll have to do another in a few months anyway). On closer inspection (and reading the upstream bug), the ABI break occurs in the private float_dsp.h header and the only consumers are libavcodec and libavfilter. This makes things much easier than I originally thought since the breakage is internal to ffmpeg. I think this can be fixed by keeping the new ABI and use package dependencies to enforce that it's used only with 3.4. We need to ensure 3.4 libavcodec/libavfilter uses 3.4 libavutil, but this is already guaranteed through the existing symbols system. We then need to prevent 3.4 libavutil from being used with pre-3.4 libavcodec/libavfilter by adding this to libavutil55: Breaks: libavcodec57 (<< 7:3.4), libavcodec-extra57 (<< 7:3.4), libavfilter6 (<< 7:3.4), libavfilter-extra6 (<< 7:3.4) I think that will fix the bug. Can anyone see anything I've missed? Thanks, James signature.asc Description: OpenPGP digital signature
Bug#882598: libavutil55: segfault after upgrade
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, thank you for the report! > https://trac.ffmpeg.org/ticket/6861 That is not a nice bug. I'll have to think about the best way to handle this. I guess we will have to revert the ABI breaking commit, identify the packages which are broken (including ffmpeg itself like in this bug), add some Breaks for them, and finally binNMU them. Alternatively we could force an ABI transition and rebuild everything, but I'm not sure if I want to do that (especially since we'll have to do another in a few months anyway). Antoni, you should be able to fix your specific problem by upgrading all the ffmpeg related packages (libav* etc) to 3.4. Thanks, James signature.asc Description: OpenPGP digital signature
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#882598: libavutil55: segfault after upgrade
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 > 7fef350b7943 sp 7fef07386ea8 error 4 in > libavutil.so.55.78.100[7fef35069000+67000] > > After downgrading libavutil55 to 7:3.3.4-2+b3 ffmpeg tools starts working > again. Please can you provide the full ffmpeg command and any input files you are using. What is "read_thread"? Thanks, James signature.asc Description: OpenPGP digital signature
Bug#882598: libavutil55: segfault after upgrade
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 downgrading libavutil55 to 7:3.3.4-2+b3 ffmpeg tools starts working again. Regards, -- System Information: Debian Release: 9.1 APT prefers stable APT policy: (900, 'stable'), (500, 'unstable'), (500, 'testing'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages libavutil55 depends on: ii libc62.24-11+deb9u1 ii libdrm2 2.4.74-1 ii libva-drm2 2.0.0-2 ii libva-x11-2 2.0.0-2 ii libva2 2.0.0-2 ii libvdpau11.1.1-6 ii libx11-6 2:1.6.4-3 libavutil55 recommends no packages. libavutil55 suggests no packages. -- no debconf information
