1624636 - WebRTC not working properly in SeaMonkey 2.53

Status: UNCONFIRMED

(SeaMonkey :: General, defect)

Description

[Isaac Schemm]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:75.0) Gecko/20100101 Firefox/75.0

Steps to reproduce:

1. Install User Agent Switcher (https://addons.thunderbird.net/en-US/seamonkey/addon/user-agent-switcher/) and WebRTC Permissions UI Toggle (https://addons.thunderbird.net/en-US/seamonkey/addon/webrtc-permissions-ui-toggle/?src=search)
2. Change the user agent string to Firefox 56 (the site used in this example does not allow a SeaMonkey user agent string)
3. Enable WebRTC from the Tools menu
4. Visit https://treffen.freifunk-bs.de/MozBugTest in SeaMonkey
5. Open another browser (e.g. Firefox, Chrome) on another computer, and visit the same site

Actual results:

When using SeaMonkey 2.53, the video and audio is not shared in either direction (just a black screen for me)

Expected results:

The two computers should make each others' webcams visible and play each others' microphone audio, as happens in SeaMonkey 2.49

Comment 1

[Isaac Schemm]

Thanks to Rainer for making me aware of this :)

https://github.com/IsaacSchemm/webrtc-permissions-ui-toggle/issues/5

Comment 2

[Firefox Bug Husbandry Bot]

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is -- (Backlog,) indicating it has has not been previously triaged, the bug's Severity is being updated to -- (default, untriaged.)

Comment 3

[Firefox Bug Husbandry Bot]

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is -- (Backlog,) indicating it has has not been previously triaged, the bug's Severity is being updated to -- (default, untriaged.)

Comment 4

[Firefox Bug Husbandry Bot]

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is -- (Backlog,) indicating it has has not been previously triaged, the bug's Severity is being updated to -- (default, untriaged.)

Comment 5

[Firefox Bug Husbandry Bot]

The severity of these bugs was changed, mistakenly, from normal to S3.

Because these bugs have a priority of --, indicating that they have not been previously triaged, these bugs should be changed to Severity of --.

Comment 6

[bernd.speiser]

Hi,
the problem is still present in Seamonkey 2.53.3 from an openSuSE Leap 15.2 installation.
I use a conference room at conf.dfn.de, where everything works with Firefox (78.1.0).
I see only a black screen (except the list of participants), while the other participants see that I am connected, but have no video or audio from me.
When I installed the WebRTC Permissions UI Toggle, I choose to get OpenH264, but I did not get any visual information that anything had indeed been downloaded or installed, and the process continued suspiciously quick. Is there a way to check if OpenH264 has indeed been installed, for example by checking for a specific file?
I'll be happy to provide additional information if needed.

Comment 7

[Isaac Schemm]

If you want to check the installed OpenH264 version, it seems like you can find it from the about:config setting "media.gmp-gmpopenh264.version". I don't think the problem is related to that, though, because I've seen the same problem in apps that use VP8 for video.

Comment 8

[bernd.speiser]

Attachment: screenshot of about:config

This is a screenshot for selected entries in about:config (filter: "H264"). I think it is showing that the installation was OK. At least there are entries related to "H264".
If so, I would conclude that missing openH264 can not be the reason for the problem.

Comment 9

[Isaac Schemm]

This bug does not seem to affect screen sharing - only webcam and microphone sharing. Screen sharing works fine in the current SeaMonkey 2.53.7.

Comment 10

[Isaac Schemm]

The bug also (maybe predictably) does not affect the user's ability to share or view a webcam that does not have a corresponding audio stream. So it seems the problem is audio-related.