Bug 26642 - Firefox 68 causes regression in BigBlueButton (WebRTC issue ?)
Summary: Firefox 68 causes regression in BigBlueButton (WebRTC issue ?)
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: All Linux
Priority: High normal
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: MGA7-64-OK
Keywords: advisory, validated_update
Depends on:
Blocks:
 
Reported: 2020-05-19 12:54 CEST by François PELLEGRINI
Modified: 2020-08-01 01:27 CEST (History)
10 users (show)

See Also:
Source RPM: firefox-68.10.0-1.mga7.src.rpm
CVE:
Status comment:


Attachments

Description François PELLEGRINI 2020-05-19 12:54:14 CEST
After installing the Firefox v68 update two days ago, the BigBlueButton (HTML5 version) echo room did no longer work. BBB is no longer able to detect speakers.
Installing back Firefox v67 restores normal behavior.
I suspect a change in the handling of audio peripherals in the WebRTC module caused a regression.
François PELLEGRINI 2020-05-19 12:54:52 CEST

Priority: Normal => High
CC: (none) => pelegrin

Comment 1 Morgan Leijström 2020-05-20 11:38:47 CEST
Could you please search upstream and other distros for similar problem and report back?

CC: (none) => fri

Comment 2 aguador 2020-06-04 19:30:03 CEST
I can confirm that WebRTC is not working properly in firefox-68.8.0-1.mga7.x86_64. I have tried with both Talky.io and Meet.jit.si. Chat is available, but neither audio nor video.

As I could see that my camera was working, I did not realize that this was a Mageia Firefox problem until today when tested with a friend who was using the latest Firefox in another distro. We tested first with Jitsi, then with Talky. Using the same session for each tool, audio and video did not work in Mageia Firefox, while Chromium-based Vivaldi worked with no problem. The FF build on my friend's system had no problem.

A lot of WebRTC related bugs have been reported upstream, many quite old but not closed. Looked through a number, especially related to WebRTC:Audio-Video, but saw nothing that matches the problem encountered here.

CC: (none) => waterbearer54

Comment 3 François PELLEGRINI 2020-06-04 23:36:53 CEST
I did not have the occasion to search for other distros. As I said, it doesn't work for Firefox 68 while it works for Firefox 67.
What I have experienced is that FF 68 is not able to detect audio and video sources other than "dummy audio" and "dummy video".
So, maybe the problem lies in the interface between the declaration of audio and video streams in the relevant Mageia component and the way FF expects to see them?
Comment 4 François PELLEGRINI 2020-06-04 23:40:29 CEST
More specifically, even with FF 67, there is an issue.
For instance, the first stream that is detected when I run BBB is "dummy audio", and I have to plug-in some earphone plug, and then remove it, to have FF discover that the speaker channel is available and functional. In the beginning, it won't send any sound to the speakers, and the volume toggles won"t work.
So maybe the problem is older, and lies in the ALSA module?
Comment 5 r howard 2020-06-05 05:21:18 CEST
Francois Did you check the Alsa settings? Back when I used to use alsa a lot I found that at random times alsa would set its channel outputs to 0.

CC: (none) => rihoward1

Comment 6 François PELLEGRINI 2020-06-05 08:15:47 CEST
(In reply to r howard from comment #5)
> Francois Did you check the Alsa settings? Back when I used to use alsa a lot
> I found that at random times alsa would set its channel outputs to 0.

I don't know if I got your message right, so please correct me, but it is not an issue about output levels. It is the fact that streams are not detected/offered to applications.
Comment 7 Lewis Smith 2020-06-05 20:58:23 CEST
Sorry to have left this. Thanks to aguador for comment 2.
Firefox has no specific maintainer, so assigning it globally.

Assignee: bugsquad => pkg-bugs
Source RPM: (none) => firefox-68.8.0-1.mga7.src.rpm

Comment 8 aguador 2020-06-06 17:01:13 CEST
FF 68.9 is already in Cauldron. I don't have access to my Cauldron machine at the moment, but if it is working there, that would be encouraging.

Cauldron FF has been build with some later versions of dependencies, which, if it is working, might provide some hints. On the other hand that also makes it impossible to grab the Cauldron FF for a fair test in Mga7.
Comment 9 Morgan Leijström 2020-06-06 17:35:51 CEST
BTW, also FF 78.0 beta is in cauldron today.
Comment 10 Tristan Balan 2020-07-07 21:38:32 CEST
Depuis la mise a jour vers firefox 68.8 framatalk et les appels hangout ne fonctionne plus. A cause des similarités entre framatalk, les appels hangout et big blue button je n’est pas ouvert un nouveau bug.

Dans les deux cas, l'entrer webcam fonctionne (je peux me voir) et l'indication du niveau de mon micro indique que le son est détecté par firefox. Mais il n'y pas de communication avec les autres personnes présentent, ni dans un sens ni dans l'autre. Le micro et la webcam fonctionnent dans d'autre logiciels comme skype.

Ce problème n'affecte pas:
- chromium
- firefox 68.7
- firefox 68.8 téléchargé depuis le site de mozilla

Suite a la mise à jour pour firefox 68.10, un test avec un appel hangout a eu le même problème, revenir a firefox 68.7 corrige toujours le problème.

Dans le forum une autre personne a noté un problème pour ce connecter a une livebox 2 depuis la même mise a jour.

https://www.mageialinux-online.org/forum/topic-27679+probleme-firefox-framatalkgoogle-hangout.php

CC: (none) => stinkys206

Comment 11 Nicolas Salguero 2020-07-10 10:37:57 CEST
Hi,

After many searches, I found this link: https://github.com/openbsd/ports/commit/349520532ca0a827b77d076fddc128083d547f40.

I added the upstream patch (https://hg.mozilla.org/mozilla-central/rev/463069687b3d) and I hope firefox-68.10.0-1.1.mga7 will fix the issue.

Best regards,

Nico.

CC: (none) => nicolas.salguero

Comment 12 Nicolas Salguero 2020-07-10 13:28:52 CEST
Suggested advisory:
========================

The firefox package has been updated to fix a regression with BigBlueButton, for instance.

References:
https://github.com/openbsd/ports/commit/349520532ca0a827b77d076fddc128083d547f40
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246363
https://bugzilla.mozilla.org/show_bug.cgi?id=1624128
========================

Updated packages in core/updates_testing:
========================
firefox-68.10.0-1.1.mga7
firefox-devel-68.10.0-1.1.mga7

from firefox-68.10.0-1.1.mga7.src.rpm

Status: NEW => ASSIGNED
Source RPM: firefox-68.8.0-1.mga7.src.rpm => firefox-68.10.0-1.mga7.src.rpm
Assignee: pkg-bugs => qa-bugs

Comment 13 Morgan Leijström 2020-07-11 14:06:49 CEST
64 bit test OK on i7, Plasma, Nvidia proprietary: three banking sites, flash, three video sites, webshops...
Comment 14 Morgan Leijström 2020-07-11 14:10:28 CEST
( That said, i noted a possible problem with previous version .10 (maybe one of the times was with .9 ), probably upstream: is have twice for me and once for my wife stopped responding.  Not consuming CPU, just sitting there. Force shut down and it restarts and we can continue OK. )
Comment 15 Thomas Andrews 2020-07-12 03:01:49 CEST
64-bit Plasma system, i5-2500, Intel graphics. 

No installation issues. While I don't do anything with video/audio web chatting (no camera or microphone), I was able to see that everything else I use still works.

Withholding an OK, hoping that someone will come along who can test the problem that was the reason for the update.

CC: (none) => andrewsfarm

Comment 16 aguador 2020-07-12 09:11:30 CEST
64-bit, Enlightenment, N4200, Intel graphics.

Tested with meet.jit.si and talky.io and audio and video both working, but with one caveat concerning permissions.

With Jitsi microphone and camera permissions are requested properly in the drop down from the address bar.

With Talky, the drop down does not appear on entering the site. Giving permission with the buttons on Talky's entrance screen works. However, if one enters the session first, permission can be granted to the microphone (from Talky), but not the camera. There is no such problem with Chromium-based Vivaldi.

Testing with Firefox 78.0.2esr in Cauldron and, on a friend's machine, Firefox 78.0.1, the same issue appears with Talky.
Comment 17 James Kerr 2020-07-13 06:45:03 CEST
on mga7-64  kernel-desktop  plasma

packages installed cleanly:
firefox-68.10.0-1.1.mga7.x86_64  

no regressions observed

looks OK for mga7-64

I don't have a webcam or microphone and so cannot
confirm that regression is fixed.

CC: (none) => jim

Comment 18 Nicolas Salguero 2020-07-13 09:05:29 CEST
Hi,

In my test with BigBlueButton, the issue with the microphone was solved.

Best regards,

Nico.
Comment 19 Morgan Leijström 2020-07-13 10:14:42 CEST
Thanks Nico
Marking as fixed then
(by  firefox-68.10.0-1.1.mga7 currently in testing repo )

Resolution: (none) => FIXED
Status: ASSIGNED => RESOLVED

Comment 20 Thomas Andrews 2020-07-13 12:38:16 CEST
Not yet. It has to have OKs and validation by QA, and the advisory must be added before that happens. 

Taking care of part of that: Giving this a 64-bit OK and validating. Advisory in Comment 12.

Whiteboard: (none) => MGA7-64-OK
CC: (none) => sysadmin-bugs
Resolution: FIXED => (none)
Keywords: (none) => validated_update
Status: RESOLVED => REOPENED

Comment 21 Morgan Leijström 2020-07-13 15:07:09 CEST
OOPS sorry, thanks!  I mixed the versions thinking this Firefox was the same one as in Bug 26890
Comment 22 François PELLEGRINI 2020-07-15 19:26:37 CEST
(In reply to Nicolas Salguero from comment #11)
> After many searches, I found this link:
> https://github.com/openbsd/ports/commit/
> 349520532ca0a827b77d076fddc128083d547f40.
> 
> I added the upstream patch
> (https://hg.mozilla.org/mozilla-central/rev/463069687b3d) and I hope
> firefox-68.10.0-1.1.mga7 will fix the issue.

I do confirm that the new version solves the issue that I reported.

Thanks !

                    f.p.
Dave Hodgins 2020-07-31 08:48:23 CEST

Keywords: (none) => advisory
CC: (none) => davidwhodgins

Comment 23 Mageia Robot 2020-08-01 01:27:19 CEST
An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2020-0158.html

Resolution: (none) => FIXED
Status: REOPENED => RESOLVED


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