Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

Firefox loses audio after disconnect from RDP session.

  • 2 답장
  • 1 이 문제를 만남
  • 13 보기
  • 최종 답변자: Joey Sun

more options

If Remote Desktop is set to play audio on the local device, all audio devices on the remote machine are changed to Remoteaudio, which will handle signals to and from the machine.

If Firefox is started after connection, it will use the device and send audio to the local machine, however, if the session is disconnected, the physical devices return and Remoteaudio disappears.

When the session is reconnected, FF refuses to play any sound, until it is restarted, despite showing up as a source on the windows mixer.

Is it possible to reattach the audio stream to a device by having FF follow the Windows device selection?

If Remote Desktop is set to play audio on the local device, all audio devices on the remote machine are changed to Remoteaudio, which will handle signals to and from the machine. If Firefox is started after connection, it will use the device and send audio to the local machine, however, if the session is disconnected, the physical devices return and Remoteaudio disappears. When the session is reconnected, FF refuses to play any sound, until it is restarted, despite showing up as a source on the windows mixer. Is it possible to reattach the audio stream to a device by having FF follow the Windows device selection?

모든 댓글 (2)

more options

Hi, Type about:config in the address bar and press Enter. A warning page may appear. Click Accept the Risk and Continue to continue to the about:config page. Search for the security.sandbox.content.level preference. Click the Edit button next to the preference and set its value to 2. Click on the checkmark to save the change. start Firefox on the remote device.

Thank you.

more options

Hello, I've seen the ticket, where this was mentioned, however, I am not sure if decreasing the security level is the right solution. Or is it meant as a temporary fix? Don't want to sound snarky, but shouldn't changing audio devices be a thing the browser could handle? Kind regards.