Closed
Bug 1410076
Opened 7 years ago
Closed 7 years ago
No Sound in Firefox since Firefox version 56.0 and 56.01 is installed on Server 2012
Categories
(Core :: Security: Process Sandboxing, defect, P2)
Tracking
()
RESOLVED
DUPLICATE
of bug 1385207
Tracking | Status | |
---|---|---|
firefox56 | + | wontfix |
firefox57 | --- | fix-optional |
firefox58 | --- | fix-optional |
People
(Reporter: it, Unassigned)
References
Details
(Keywords: regression, regressionwindow-wanted)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:56.0) Gecko/20100101 Firefox/56.0
Build ID: 20171002220106
Steps to reproduce:
i have several Microsoft Server 2012 latest ServicePack Levels, Firefox is installed on these Servers.
We use these Server as RDP Server and some als Hostserver.
There was never a problem with Video-Files oder Sound-Files since Version Firefox 56.0. Since the update to Firefox version 56.0 there is no sound provided anymore. All the settings are still the same. The videos are running normally, only there is no sound.
If we go back to Firefox Version 55.0 sound is back normally, without any further settings.
Actual results:
We testet this issue on 10 server 2012 latest Patchlevels, on all Server has been the same issue... RDP Server and Host Server as well.
It doesn´t matter if the 2012 Server is a hyper-V VM or a plain Hostserver. There is no sound in Firefox if the version 56.0 and higher is running!
Expected results:
Video and Sound should be there
[Tracking Requested - why for this release]: tracking requested as this appears to be a regression in Firefox 56.
@VGWORT, would you be able to debug this further for us locally? It will require running some of our Nightly builds to track down the issue which I'd be happy to walk you through. Otherwise we'll need to try to replicate your environment in house.
status-firefox56:
--- → affected
status-firefox57:
--- → ?
status-firefox58:
--- → ?
tracking-firefox56:
--- → ?
Component: General → Audio/Video
Keywords: regressionwindow-wanted
OS: Unspecified → Windows
Hardware: Unspecified → All
Status-firefox57: affected
Status-firefox57.0b9: affected
OS: Windows Server 2012 Std. Version 6.2 (Build 9200)and Server R2 Std. 6.3 (Build 9600)
Hardware: Hyper-V VM and IBM System X3550 M4 Server
Status-firefox56.0.1: affected
OS: Windows Server 2012 Std. Version 6.2 (Build 9200)and Server R2 Std. 6.3 (Build 9600)
Hardware: Hyper-V VM and IBM System X3550 M4 Server
Sorry, i can´t find any folder that contains any version higher than 57.0b9
I´m using the URL https://ftp.mozilla.org/pub/firefox/releases/
have you got any further versions?
Have a nice weekend, Ralf
Comment 5•7 years ago
|
||
You can also find downloads at: https://archive.mozilla.org/pub/firefox/nightly/2017/10/
It would be helpful to get a regression range with http://mozilla.github.io/mozregression/
Updated•7 years ago
|
Component: Audio/Video → Audio/Video: cubeb
Priority: -- → P2
Status-Firefox Nightly 58.0a1 (2017-10-23) (32bit): affected
Thank you @Michael Froman for the URL
Comment 8•7 years ago
|
||
Too late to fix in 56, I'll mark this fix-optional for 57 since we are nearing the release date for 57, but we could still take a patch in 58.
Keywords: regression
this Problem seems to have it´s source in the sandbox-level.
This is a known issue.
https://support.mozilla.org/de/kb/i-cant-play-audio-remote-desktop-connection
If you are on a Remote Desktop Connection (RDP) on Windows, audio playback will be disabled due to increased security restrictions. This is a known issue in Firefox version 56 that we are working hard to fix.
In the meantime, you can reduce the sandbox security level by following these steps:
In the address bar, type about:config and press Enter.
The about:config "This might void your warranty!" warning page may appear. Click I accept the risk! to continue to the about:config page.
Search for security.sandbox.content.level and set it to 2.
Restart Firefox on the remote device.
Reporter | ||
Comment 10•7 years ago
|
||
so my next question is, what´s the risk, if i may change the security.sandbox.content.level from level 3 until 2 on my RDP servers?
Reporter | ||
Comment 11•7 years ago
|
||
status-firefox58.0a1 date 2017-10-26:affected
if i lower the security.sandbox.content.level down to 2 > sound is okay
Comment 12•7 years ago
|
||
At most that lowers the sandboxing security to the level it was in the previous release. And overall it's higher than it was a few releases previous, before multi-process.
Reporter | ||
Comment 13•7 years ago
|
||
status-firefox57.0.1: ---- > affected
since version 57.0 there is another issue, whitch is happening sporadically, if users are using several tabs in firefox, sometimes there is no posibillity to write something in forms oder databases or the whole firefox is crashing down.
Workaround momentanly: close all Tabs, clearing Firefox cache, close last Firefox window and start a new session.
Next working day, some users has got the same issue.... it affects approxymately 2% of all Users a day
Updated•7 years ago
|
Component: Audio/Video: cubeb → Security: Process Sandboxing
See Also: → 1432577
![]() |
||
Updated•7 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
Comment 15•7 years ago
|
||
(In reply to VGWORT from comment #13)
> status-firefox57.0.1: ---- > affected
>
> since version 57.0 there is another issue, whitch is happening sporadically,
> if users are using several tabs in firefox, sometimes there is no
> posibillity to write something in forms oder databases or the whole firefox
> is crashing down.
> Workaround momentanly: close all Tabs, clearing Firefox cache, close last
> Firefox window and start a new session.
> Next working day, some users has got the same issue.... it affects
> approxymately 2% of all Users a day
As this is a different issue it has probably got lost in a comment on this bug.
Would you file a new bug please.
If you have related crash reports (about:crashes) then include some of the IDs.
If you can find reliable steps to reproduce that would be great, thanks.
Flags: needinfo?(it)
Updated•7 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•