Bug#829434: mpg123 segfaults once after dist-upgrades

On Jul 03, Thomas Orgis wrote: > You still see the jack errors and get a segfault? Are you able to > create a backtrace? (`ulimit -c unlimited` before running mpg123 and > then analysing the core file with gdb)? No, I cannot reproduce this at will: I have only noticed

Bug#829434: mpg123 segfaults once after dist-upgrades

On Jul 03, Thomas Orgis wrote: > This looks like the jack output module crashing, a bug in itself, that > might be fixed in the current upstream mpg123. Your main issue is that > the proper output module, alsa in this case, fails to work. What is the > output of > >

Bug#829434: mpg123 segfaults once after dist-upgrades

Package: mpg123 Version: 1.22.4-1 Severity: normal This has happened multiple times to me after a dist-upgrade, but I do not know exactly how to reproduce it: mpg123 --random --quiet --control --title ... [jack.c:252] error: Failed to open jack client: 0x1 [jack.c:58] warning: FIXME: One needs

Re: [FFmpeg-devel] Reintroducing FFmpeg to Debian

On Aug 08, Matthias Urlichs matth...@urlichs.de wrote: IMHO the best idea at this point would be to toss out libav, and rebuild the rdeps with ffmpeg. Now, before it's too late for jessie. Agreed. The interested parties should really raise this with the CTTE ASAP. -- ciao, Marco

Re: Bug#729203: [FFmpeg-devel] Reintroducing FFmpeg to Debian

On Jul 28, Alessio Treglia ales...@debian.org wrote: Personally I don't feel like dropping libav in favor of ffmpeg now at this stage. It's too late for Jessie. Except that, for a lot of the depending packages, there would be an immediate benefit in the number of bugs fixed. Personally I feel

Re: [FFmpeg-devel] Reintroducing FFmpeg to Debian

On Jul 28, Reinhard Tartler siret...@gmail.com wrote: Moreover, I am curious why I haven't seen you working on libavcodec bugs in Debian before, and why do you believe you can do a better job with the ffmpeg package currently on NEW? Why should he work on libavcodec when he (along with many