Avatar for Username

Iskanje po podpori

Izogibajte se prevarantski tehnični podpori. Nikoli vam ne bomo naročili, da pokličete telefonsko številko ali nam pošljete osebne podatke. Sumljivo dejavnost prijavite z gumbom »Prijavi zlorabo«.

Več o tem

Ta tema je arhivirana. Postavite prosim novo vprašanje, če potrebujete pomoč.

Webm doesn't play, breaks entire computer's sound output

  • 1 odgovor
  • 6 ima to težavo
  • 1 ogled
  • Zadnji odgovor od Moses

Turbosepp
Turbosepp
more options

I have a rather strange problem: I play a few .webm files, and everything works perfectly - until something happens (mostly after opening a new .webm video, doesn't have to do with the content itself, it just randomly happens whenever I open a new .webm) and the sound output on my entire system doesn't work anymore.

I then have to go to Control Panel -> Sound and have to manually de- and reactivate the sound output (speakers) to get it working again. I have no idea in what way Firefox, or .webm in particular, messes directly with the sound output.

System: Windows 7 64-bit FF version: 29.0

I have a rather strange problem: I play a few .webm files, and everything works perfectly - until something happens (mostly after opening a new .webm video, doesn't have to do with the content itself, it just randomly happens whenever I open a new .webm) and the sound output on my entire system doesn't work anymore. I then have to go to Control Panel -> Sound and have to manually de- and reactivate the sound output (speakers) to get it working again. I have no idea in what way Firefox, or .webm in particular, messes directly with the sound output. System: Windows 7 64-bit FF version: 29.0

Vsi odgovori (1)

Moses
Moses
  • Moderator
more options

Can you try to start Firefox in Safe Mode to see if Firefox works properly with no error? You can start Firefox in Safe Mode below:

  • Windows/Mac: Go to Help > Restart with add-ons disabled
  • Linux: Run firefox -safe-mode in the Terminal/Konsole

If Firefox opens up fine with no problems, it's probably one of your extensions that's causing the issue. You can re-enable your add-ons one by one until you find the one that causes the issue upon being re-enabled.