a bug was closed "because the developer couldn't be bothered to work with people". as the bug cannot be reopened i am forced into the position of creating an entirely new one, referencing the old one (see ID in subject summary), thus inconveniencing everyone who is trying to help improve opal.
a simple search shows that other people have encountered this, and even, apparently, fixed the problem, for example here:
that's a rather messy way to do it, but it works. the issue is that the opal developers cannot be bothered to ask users the question "which versions of ffmpeg libraries are you using", to which the answer would be (in this case):
lkcl@teenymac:~/src/opal$ dpkg -l | grep ffmpeg|libav
ii ffmpeg 5:0.10-0.1 audio/video encoder, streaming server & audio/video file converter.
ii libavcodec-dev 7:0.11.1-dmo4 Library to encode decode multimedia streams - devel files.
ii libavcodec52 5:0.6.1+svn20101128-0.2 library to encode decode multimedia streams - runtime files
ii libavcodec53 7:0.10.3-dmo1 Library to encode decode multimedia streams - runtime files.
ii libavcodec54 7:0.11.1-dmo4 Library to encode decode multimedia streams - runtime files.
ii libavcore-dev 5:0.6.1+svn20101128-0.2 multimedia core utilities library - devel files
ii libavcore0 5:0.6.1+svn20101128-0.2 multimedia core utilities library - runtime files
ii libavdevice52 5:0.6.1+svn20101128-0.2 ffmpeg device handling library
ii libavdevice53 5:0.10-0.1 FFmpeg device handling library.
ii libavfilter2 5:0.10-0.1 FFmpeg filter library.
ii libavformat-dev 7:0.11.1-dmo4 Development files for libavformat.
ii libavformat52 5:0.6.1+svn20101128-0.2 ffmpeg file format library
ii libavformat53 5:0.10-0.1 FFmpeg file format library.
ii libavformat54 7:0.11.1-dmo4 FFmpeg file format library.
ii libavutil-dev 7:0.11.1-dmo4 FFmpeg avutil devel files - devel files.
ii libavutil49 4:0.5.2-6 ffmpeg utility library
ii libavutil50 5:0.6.1+svn20101128-0.2 avutil shared libraries - runtime files
ii libavutil51 7:0.11.1-dmo4 FFmpeg avutil library - runtime files
these versions are, as can be deduced from the package names, obtained from debian-multimedia.
that should be sufficient information to reproduce the issue, would you agree, yes?