Comment #2 indicates that a non-Ubuntu, 3rd party package is most likely responsible for this bug.
Dear medibuntu guys, this issue looks pretty serious to me. Please have a look and feel free to contact me if you believe that this issue is also present in the ubuntu libavcodec53 package.
Thanks.
Comment #2 indicates that a non-Ubuntu, 3rd party package is most likely responsible for this bug.
Dear medibuntu guys, this issue looks pretty serious to me. Please have a look and feel free to contact me if you believe that this issue is also present in the ubuntu libavcodec53 package.