[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#993222: marked as done (ffmpeg: Having libvpx 1.10.0-1 installed gives "ABI version mismatch" error)

Your message dated Wed, 1 Sep 2021 14:52:21 +0200
with message-id <YS93hfoy5Dbx+M2S@ramacher.at>
and subject line Re: Bug#993128: libvpx6: Unable to use camera or share screen on WebRTC conferences
has caused the Debian Bug report #993128,
regarding ffmpeg: Having libvpx 1.10.0-1 installed gives "ABI version mismatch" error
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
993128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993128
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: ffmpeg
Version: 7:4.4-5
Severity: normal

Dear Maintainer,

A recent apt-upgrade installed the latest version of libvpx, 1.10.0-1,
on my system. The next time I tried to encode a video with VP8, it gave
the error message "Failed to initialize encoder: ABI version mismatch".
Downgrading to the previous version, 1.9.0-1, fixed the issue.
FFmpeg should declare its incompatibility with 1.10.0-1 so the package
gets kept back.
Besides that, no issues with the package. Thank you for maintaining it!

Sincerely,
Jan

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-8-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages ffmpeg depends on:
ii  libavcodec58    7:4.4-5
ii  libavdevice58   7:4.4-5
ii  libavfilter7    7:4.4-5
ii  libavformat58   7:4.4-5
ii  libavutil56     7:4.4-5
ii  libc6           2.31-17
ii  libpostproc55   7:4.4-5
ii  libsdl2-2.0-0   2.0.14+dfsg2-3
ii  libswresample3  7:4.4-5
ii  libswscale5     7:4.4-5

ffmpeg recommends no packages.

Versions of packages ffmpeg suggests:
pn  ffmpeg-doc  <none>

-- no debconf information

--- End Message ---
--- Begin Message --- 
Version: 1.10.0-2

On 2021-09-01 09:38:24 -0300, Paulo wrote:
> On Tue, 31 Aug 2021 18:10:36 +0200 Sebastian Ramacher <sramacher@debian.org> wrote:
> > Control: tags -1 moreinfo
> > 
> > On 2021-08-27 12:10:14 -0300, Paulo Roberto Alves de Oliveira (aka kretcheu) wrote:
> > > Package: libvpx6
> > > Version: 1.10.0-1
> > > Severity: important
> > > Tags: a11y
> > > > Dear Maintainer,
> > > > When we try do use camera or share screen on WebRTC like, Jitsi,
> > GoogleMeeting, it's not working.
> > > > Running Chromium on terminal we can see many error messages:
> > > > ERROR:video_stream_encoder.cc(1729)] Failed to encode frame. Error
> > code: -7
> > > > Downgrading to version 1.9.0-1 it's working again.
> > 
> > Could you please retry with 1.10.0-2 which is now available in unstable?
> > 
> > Cheers
> > 
> > > > Thank's
> > > > > -- System Information:
> > > Debian Release: bookworm/sid
> > >   APT prefers unstable
> > >   APT policy: (500, 'unstable')
> > > Architecture: amd64 (x86_64)
> > > > Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads)
> > > Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE not set
> > > Shell: /bin/sh linked to /bin/dash
> > > Init: systemd (via /run/systemd/system)
> > > LSM: AppArmor: enabled
> > > > Versions of packages libvpx6 depends on:
> > > ii  libc6  2.31-17
> > > > libvpx6 recommends no packages.
> > > > libvpx6 suggests no packages.
> > > > -- no debconf information
> > >
> > 
> > -- 
> > Sebastian Ramacher
> 
> 
> Hi Sebastian,
> 
> It's working again, normal using Chromium and Firefox.
> 
> For me you could (Closes: #993128).

Thanks for checking.

Cheers
-- 
Sebastian Ramacher

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: