Thu, 7 Mar 2013, 21:44 +01:00 from Paul Gevers <elb...@debian.org>: > What I meant to say is that on 22 Dec, I made a mistake in testing if > the bug was still there. I had a mixed system, and I thought the bug was > fixed, while with ONLY libav related packages from experimetal the bug > was still there.
By the way, do you experience this bug in "pure wheezy libav"?
