Open Bug 1841628 Opened 2 years ago Updated 1 year ago

WARNING: 7f42da7d7dc0 OpenCubeb() failed to init cubeb: file /build/firefox-RH6krf/firefox-115.0+build2/dom/media/AudioStream.cpp:281

Categories

(Core :: Audio/Video: cubeb, defect)

Firefox 115
defect

Tracking

()

UNCONFIRMED

People

(Reporter: marietto2008, Unassigned, NeedInfo)

Details

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/115.0

Steps to reproduce:

ziomario@Z390-AORUS-PRO-DEST:~$ firefox

[GFX1-]: More than 1 GPU from same vendor detected via PCI, cannot deduce device

[Parent 8662, Main Thread] WARNING: Unable to connect to ibus: Could not connect: Connection refused: 'glib warning', file /build/firefox-RH6krf/firefox-115.0+build2/toolkit/xre/nsSigHandlers.cpp:167

(firefox:8662): IBUS-WARNING **: 14:25:21.696: Unable to connect to ibus: Could not connect: Connection refused
[Child 11787, MediaDecoderStateMachine #1] WARNING: 7f42da7d7dc0 OpenCubeb() failed to init cubeb: file /build/firefox-RH6krf/firefox-115.0+build2/dom/media/AudioStream.cpp:281
[Child 11787, MediaDecoderStateMachine #1] WARNING: Decoder=7f42e8205800 [OnMediaSinkAudioError]: file /build/firefox-RH6krf/firefox-115.0+build2/dom/media/MediaDecoderStateMachine.cpp:4604
[Child 11787, MediaDecoderStateMachine #1] WARNING: 7f42f902d4c0 OpenCubeb() failed to init cubeb: file /build/firefox-RH6krf/firefox-115.0+build2/dom/media/AudioStream.cpp:281
[Child 11787, MediaDecoderStateMachine #1] WARNING: Decoder=7f42f50efd00 [OnMediaSinkAudioError]: file /build/firefox-RH6krf/firefox-115.0+build2/dom/media/MediaDecoderStateMachine.cpp:4604
[Child 11787, MediaDecoderStateMachine #1] WARNING: 7f42e076b820 OpenCubeb() failed to init cubeb: file /build/firefox-RH6krf/firefox-115.0+build2/dom/media/AudioStream.cpp:281
[Child 11787, MediaDecoderStateMachine #1] WARNING: Decoder=7f42f50efd00 [OnMediaSinkAudioError]: file /build/firefox-RH6krf/firefox-115.0+build2/dom/media/MediaDecoderStateMachine.cpp:4604
[Child 11787, MediaDecoderStateMachine #1] WARNING: 7f42d8cab280 OpenCubeb() failed to init cubeb: file /build/firefox-RH6krf/firefox-115.0+build2/dom/media/AudioStream.cpp:281
[Child 11787, MediaDecoderStateMachine #1] WARNING: Decoder=7f42f50efd00 [OnMediaSinkAudioError]: file /build/firefox-RH6krf/firefox-115.0+build2/dom/media/MediaDecoderStateMachine.cpp:4604

Actual results:

I don't hear any audio.

Expected results:

I should hear audio from videos on line and offline.

(I'm running ubuntu 23.04 - lunar).

The Bugbug bot thinks this bug should belong to the 'Core::Audio/Video: Playback' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Audio/Video: Playback
Product: Firefox → Core

https://searchfox.org/mozilla-central/rev/f03ce34731ff8d1f6c77d8241c41d10df13e9aca/dom/media/AudioStream.cpp#281

Maybe a media format issue, or some sort of device specific problem in cubeb. Mathew what are the potential causes of a failed call to CubebUtils::CubebStreamInit?

Flags: needinfo?(kinetik)
Severity: -- → S3
Component: Audio/Video: Playback → Audio/Video: cubeb

I can also confirm this bug in 115.4.0esr (64-bit), as shipped in Debian 12. This did not occur with 102.15.1esr, to the best of my knowledge.
I had seemingly identical symptoms, no sound and

[MediaDecoderStateMachine #1] WARNING:  OpenCubeb() failed to init cubeb: file ./dom/media/AudioStream.cpp:281

would appear each time a page tried to play audio. about:support correctly listed my audio device along with the expected backend.
Quick disclaimer, which may not be true for the reporter: My system is an ALSA-only system, no Pipewire or PulseAudio.

In my case, about:support was full of "Rejected System Calls" for syscall 220, which was a hint.
Running with MOZ_LOG=cubeb:5, I also saw seccomp warnings repeated quite frequently.

Sandbox: seccomp sandbox violation: pid 89629, tid 89805, syscall 220, args 65543 139974933195068 2 0 8 0.

I was able to workaround this by adding 220 to about:config's security.sandbox.content.syscall_whitelist. Sound immediately worked after doing so. Removing it from a running session did not seem to have an impact, so it's possible that syscall is only needed on sound initialization.

You need to log in before you can comment on or make changes to this bug.