Komunitné fórum Firefox

I use eBird extensively. When I try to play the audio (with sonograms), I get a message that says "We are still processing this file. Try again later". These files perform well on my Android phone, so I know it it is not eBird's glitch. I am confused about the setting options on Firefox that I need to set. These files are usually .wav format. I have tried to open a ticket with eBird, but have not had a response. Can you guide me? Thanks.

Hello there.

Since last update i'm unable to browse websites like youtube, social media and all other websites with video content. Video often fails to load,the wholewebsite is not loading, freezes while played or while exiting full screen mode. All of these freezes the browser - the site cannot be refreshed, links does not work. The only way is to close the tab with the freezed page or kill the Firefox process in windows Task Manager. Refreshing, re-installing, deleting or using different profile don't work. Same with add-ons. Seems like the issue lies within the browser and it started to appear since last update.

I've tried messing with hardware acceleration, resetting the zoom to 100, it seems when i get the zoom as low as possible it tries to fall back into place, i can't find any fix on this, i like this browser but i cant watch anything like this

Unable to play a video on Hulu with my own Hulu account, which I have had no issues in the past doing, even with all my ad blockers and trackers enabled (Privacy Badger, uBlock Origin, AdBlocker Ultimate, Ghostery, and Malwarebytes). I have tried disabling all of the above extensions, refreshing the website and still no luck. I have also followed the instructions Hulu guides me to via a link on the screen (see attached screenshot) to their help page https://help.hulu.com/article/hulu-power-cycle?utm_source=hulu&utm_medium=error-message&utm_campaign=video-02 None of these have helped either. My internet speed is fine, I checked it through 3 different internet speed testers to verify Also checked my Wifi signal through our Google Home portal. I've searched online for solutions and haven't found anything new to help or in the Mozilla Support forum. My computer/laptop is up to date on all updates and software. Appreciate any support, thank you!

Hello Firefox Support Team/Forum

I am writing to request guidance on a hardware video acceleration issue that I have been unable to resolve despite extensive troubleshooting. Firefox appears to be blocking VA-API hardware decoding on my system even though the VA-API stack is confirmed working at the system level. — SYSTEM SPECIFICATIONS — OS: Arch Linux (rolling), kernel 7.0.13-arch1-1 Desktop: Hyprland 0.55.4 (Wayland, DRM backend) CPU: AMD A9-9425 (2 cores, 3.1GHz, Excavator architecture) RAM: 8GB Firefox: installed via pacman (native, not Flatpak) Mesa: 26.1.3-arch1.2 GPU setup (dual): • card0 / renderD128: AMD Stoney R5 Graphics (iGPU) — VA-API confirmed working here • card1 / renderD129: AMD Hainan R5 M435 (dGPU) — used by Hyprland for display output — CONFIRMED WORKING AT SYSTEM LEVEL — Running ‘vainfo’ on the integrated GPU (renderD128) confirms the following profiles are available: VAProfileH264ConstrainedBaseline, VAProfileH264Main, VAProfileH264High (VLD + EncSlice) VAProfileHEVCMain, VAProfileHEVCMain10 (VLD) VAProfileMPEG2Simple, VAProfileMPEG2Main, VAProfileVC1 (VLD) VAProfileJPEGBaseline (VLD) MPV with ‘–hwdec=vaapi-copy’ successfully hardware-decodes H264 locally, confirmed by ‘nv12’ pixel format output and reduced CPU usage. radeontop monitoring card0 (stoney, bus 00) during Firefox video playback shows: • Graphics pipe: ~53% (compositing activity) • UVD row: absent / 0% (no hardware video decode activity) • Memory clock: near 0.00G This confirms Firefox is NOT using the hardware decoder despite VA-API being functional. — FIREFOX DECISION LOG (from about:support) — HARDWARE_VIDEO_DECODING: default available / user force_enabled H264_HW_DECODE: default available (no blocklist) HEVC_HW_DECODE: default available VP8_HW_DECODE: env blocklisted — FEATURE_FAILURE_VIDEO_DECODING_MISSING VP9_HW_DECODE: env blocklisted — FEATURE_FAILURE_VIDEO_DECODING_MISSING AV1_HW_DECODE: env blocklisted — FEATURE_FAILURE_VIDEO_DECODING_MISSING DMABUF_SURFACE_EXPORT: env blocked — FEATURE_FAILURE_BROKEN_DRIVER WEBRENDER_COMPOSITOR: env blocklisted — FEATURE_FAILURE_WEBRENDER_COMPOSITOR_DISABLED Note: VP8/VP9/AV1 being missing is expected and correct for this GPU generation. The concern is that H264, which IS in the vainfo profile list and shows as ‘available’ in the decision log, is still not being routed to the hardware decoder in practice. — ENVIRONMENT VARIABLES IN USE — MOZ_ENABLE_WAYLAND=1 LIBVA_DRIVER_NAME=radeonsi LIBVA_DRM_DEVICE=/dev/dri/renderD128 MOZ_DISABLE_RDD_SANDBOX=1 — about:config SETTINGS CURRENTLY SET — media.ffmpeg.vaapi.enabled = true media.hardware-video-decoding.force-enabled = true media.hardware-video-decoding-vulkan.enabled = false media.rdd-process.enabled = true — WHAT WAS TRIED — 1. Installed full Mesa stack: mesa, libva-mesa-driver, libva-utils, ffmpeg, vulkan-radeon (64-bit and 32-bit variants via multilib). 2. Set LIBVA_DRM_DEVICE=/dev/dri/renderD128 to hardcode VA-API to the stoney iGPU and prevent it from accidentally targeting the hainan dGPU (which fails Firefox’s internal VA-API test with FEATURE_FAILURE_VIDEO_DECODING_TEST_FAILED). 3. Enabled media.ffmpeg.vaapi.enabled and media.hardware-video-decoding.force-enabled in about:config. 4. Disabled MOZ_DISABLE_RDD_SANDBOX via both ~/.bash_profile and hl.env() in the Hyprland Lua config to allow Firefox’s RDD process to access /dev/dri/renderD128. 5. Installed enhancedH264ify extension with VP9 and AV1 blocking enabled. YouTube confirms H264 (avc1.64002a) is being served. Despite this, over 1100 frames out of ~4200 are dropped during 1080p60 playback. 6. Verified with radeontop -b 0 (stoney, bus 00) during active 1080p H264 playback: the UVD block shows no activity whatsoever, confirming the CPU is doing all decoding. 7. Tested with and without gfx.webrender.all = true. Enabling it caused severe visual corruption (texture artifacts, split UI elements), so it was reset to default. 8. Did NOT disable media.rdd-process.enabled (correctly kept at true, as RDD is the process Firefox uses for VA-API decoding). 9. Confirmed Firefox is installed via pacman (not Flatpak), so there is no Flatpak sandbox layer involved. — THE CORE QUESTION — Given that: • vainfo confirms H264 hardware decode is available on renderD128 • H264_HW_DECODE shows as ‘default available’ in Firefox’s own decision log with no blocklist entry • media.hardware-video-decoding.force-enabled is set to true • MOZ_DISABLE_RDD_SANDBOX=1 is set • LIBVA_DRM_DEVICE explicitly points to the correct render node • MPV successfully uses vaapi on the same system …why is Firefox’s RDD process still not routing H264 decoding through VA-API, and what additional steps or logs would help identify the specific internal failure point?

Any guidance on enabling verbose VA-API logging within Firefox’s RDD process, or any known issues with AMD Stoney + Hainan dual-GPU setups on Wayland that might explain the DMABUF_SURFACE_EXPORT FEATURE_FAILURE_BROKEN_DRIVER blocklist, would be greatly appreciated.

Thank you.

Greetings! I've been a Firefox evangelist for a long time! I'm having issue with my Dell Precision 5530 pushing Firefox audio to a Bluetooth speaker connected to PC. Others browsers work fine, however FF wants to use the speakers on my monitor, connected via HDMI. I've tried to change several times, however FF does not want to use the BT.

Can you please help?

Thank you kindly!

Will Smith

I was receiving Directv content on Mozilla Firefox for months without issue. Suddenly it stopped completely and left a message "We couldn't play this content at this time". I don't understand why this happened or how to fix it. I want to do all my browsing with Mozilla Firefox so I need help. It would be truly excellent if I could speak to a human about this issue. Please.

this is still really annoying: https://support.mozilla.org/en-US/questions/1500761

why is the icon even there or why does it have to disappear and then also change the tab size ?

1) if its there to enable you to play a tab in the background, then i want the option to switch the feature on or off (because i do not want to play anything in the background, atleast not via a 24/7 target practice with a mouse)

2) if its there to give you notice that there is a 'multimedia' tab open in your browser, then i want the icon to stay there and not dissapear plus change tab size...

like what is this even ? are we back in the 50s ?

Many users ask for solution to disable your great invention : annoying mute buttons (speaker). And creators of FF strongly make it imposible to turn it off? Why? Is ther a "must" to suffer this? There will be some of reward for pain you give with this "feature"?