Firefox Community Forum

I am using Firefox on gnome desktop on the PureOS variant of Debian. About three days ago, I went to listen to my Spotify playlist on Firefox, not through the Spotify app. I had no sound, checked my system settings and turned the volume for Firefox from zero back up to normal. The rest of the song played, but when the next song came on, again no sound. I watched the sound settings and when the song finishes, Firefox disappears from the sound settings list. When the next song starts, Firefox is back in the list but volume is set back to zero. I suspect this may be something in gnome, but I thought I would check here in case anyone else is seeing this issue. Thanks so much for any help or at least a shoulder to cry on :D

Firefox screws up showing .pdfs. The first view is fine but scrolling seems to overprint the first view without erasing it, if that makes sense, sorta like a double exposure. I can't get a screen cap either, which might just mean it's not a firefox issue at all, but I can view and screen cap .pdfs from any other application. I'm running Debian 12 up to date. When I need to view a .pdf I use Chromium, but I do prefer Firefox.

If I display (e.g.) Nepal in Google maps, initially the Nepali names appear beneath the Latin alphabet names, but only for a split second. They are then overwritten with unicode block icons. Some scripts work (e.g. Cyrillic, Chinese, Japanese, Armenian), but most south Asian scripts do this weird "works for a split second" rendering.

I'm running 128.8.0esr (64-bit) on Debian 12.

This problem does NOT occur in Safe Mode!

In Normal mode, I disabled all plugins and extensions, but the rendering still breaks.

Any ideas?

The same page renders properly in Chrome 134.0.6998.88

A problem with an x.0 version? I've been using FF from "source code" for years on Debian Linux, but this is the first time such an update is failing after the most recent update to v133.0, as illustrated in attached image. How can I now update to the fix for this problem, please?

Hello,

After a few days I noticed that the option "open with" on the downloads dialog is always grayed out (see the attached picture).

If I go on the settings and tell the browser to not ask and open directly the file, it opens without any problem... (actually it shows an advertisement saying it is an executable file, but when I dismiss it, it opens)

Here are my system setup: Nom: Firefox Version: 130.0.1 Identifiant de compilation: 20240913135723 ID de distribution: mozilla-deb Canal de mise à jour: release Agent utilisateur: Mozilla/5.0 (X11; Linux x86_64; rv:130.0) Gecko/20100101 Firefox/130.0 Système d’exploitation: Linux 6.1.0-25-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.106-3 (2024-08-26) Thème du système d’exploitation: Breeze / Adwaita Binaire de l’application: /usr/lib/firefox/firefox-bin

Does anybody else is having this issue? Any ideas on how can I fix it?

Thanks in advance for all your help,

Best regards, Marc

EDIT: I just tested the behavior on the "base" Firefox-ESR, and it works as expected, as you can see on the 2nd attached file, esr.png... Version: 28.2.0esr Identifiant de compilation: 20240826114743 ID de distribution: mozilla-deb Canal de mise à jour: esr

The browser just shuts down when one tries to create a new flow ... obviously there is not a way to screenshot this ... one suspects this is a javascript issue.

Details:

• OS - Debian 12 (Wayland | Gnome 43.9)
• Nightly Version - Debian Repo (mozilla-deb - 1.0) | 132.0a1 (2024-09-23) (64-bit)
• URL / Actions - make.powerautomate.com > New Instant Cloud Flow > Name it & Select Manually trigger a flow

What Else Have I Tried?

• Ungoogle Chromium - Absolutely fine, no add-ons
• Firefox mozilla-deb - 1.0 130.0.1 (64-bit) - Absolutely fine, no add-ons

Hello guys,

The trouble I ll present you might come a bit late, I've just never thought about asking on this forum (didn't even know that it exists lol) and I spent a lot time on tutorials trying to find the solution... lol 😩

My situation : I have a laptop with debian 12 stable. Early July, I updated my apps, Firefox 128 has just been released. Since the Firefox 128 update, I can no longer execute Firefox, I always get the pop up message :

Failed to execute child process (no such file or directory)

I've tried many times to uninstall & reinstall, purge & reinstall. Still the same "failed to execute... " message. all the subsequent updates (128.X and 129.X) haven't solved this problem...

On the other hand, Firefox ESR 128 works like a charm.

Is anyone in the same situation as me ? 😕

Wishing you a nice day :)

I woke up this morning to my home directory having been remounted as read-only (it has its own dedicated hard drive at /dev/sdd1). I ran e2fsck and things looked good, so I restarted and things were fine again.

However, whenever I open Firefox, it hangs for about 1 full minute before it goes haywire and renders the entire system essentially unusable since being able to access my home directory is vital. The following is visible in dmesg:

[ 2710.362946] Aborting journal on device sdd1-8. [ 2710.363000] EXT4-fs warning (device sdd1): ext4_end_bio:343: I/O error 5 writing to inode 10520593 starting block 44134769) [ 2710.363008] Buffer I/O error on device sdd1, logical block 44134513 [ 2710.363041] EXT4-fs error (device sdd1): ext4_journal_check_start:84: comm glean.dispatche: Detected aborted journal [ 2710.363048] EXT4-fs warning (device sdd1): ext4_dx_find_entry:1795: inode #9718667: lblock 2: comm Renderer: error -5 reading directory block [ 2710.363076] EXT4-fs warning (device sdd1): htree_dirblock_to_tree:1082: inode #9701223: lblock 1: comm Cache2 I/O: error -5 reading directory block [ 2710.800016] EXT4-fs warning (device sdd1): ext4_dirblock_csum_verify:405: inode #9976467: comm BgIOThr~ool #12: No space for directory leaf checksum. Please run e2fsck -D. [ 2710.812447] EXT4-fs warning (device sdd1): ext4_dirblock_csum_verify:405: inode #9976467: comm Backgro~Pool #1: No space for directory leaf checksum. Please run e2fsck -D. [ 2710.884557] EXT4-fs warning (device sdd1): ext4_dirblock_csum_verify:405: inode #9976467: comm Backgro~Pool #1: No space for directory leaf checksum. Please run e2fsck -D. [ 2710.980923] EXT4-fs (sdd1): Remounting filesystem read-only [ 2711.049635] EXT4-fs warning (device sdd1): ext4_dirblock_csum_verify:405: inode #9701223: comm Cache2 I/O: No space for directory leaf checksum. Please run e2fsck -D. [ 2711.152739] EXT4-fs warning (device sdd1): ext4_dirblock_csum_verify:405: inode #9701223: comm Cache2 I/O: No space for directory leaf checksum. Please run e2fsck -D. [ 2711.152757] EXT4-fs warning (device sdd1): ext4_dirblock_csum_verify:405: inode #9701223: comm Cache2 I/O: No space for directory leaf checksum. Please run e2fsck -D.

All other programs that I use daily do not cause this issue. No clue what to do here. LibreWolf works fine - that's what I'm using now that Firefox breaks everything and basically forces me to restart if I want to use my computer normally.

Hello, have been scratching my head for a while on this one. Have a freshly setup install of Debian 12, using Sway (wayland) as my Window Manager. I am really struggling with slowness in Firefox, page loads take easily 15 seconds whereas loading the exact same page in another window at the same time with Chromium Debian build has near instantaneous load times. I've tried the following troubleshooting steps: - Created a new firefox profile - Tried "Troubleshooting Mode" in Firefox - Disabled ipv6 in firefox about:config and in Debian - Tried different DNS servers - Tried different non-debian specific builds of Firefox - Tried Firefox Beta and Firefox Nightly for Debian

None of these steps made any difference, and Chromium has continued to be significantly faster. Am really stuck here and would love to get to the bottom of this as Firefox is the only browser that works with a HiDPI display in Sway without blurryness. Happy to provide any and all diagnostics and reports that are needed. Thanks in advance!

EDIT: It seems to be some kind of networking issue, using a VPN solves it. But still doesn't explain why Chromium would behave differently.

After some time of idle, i.e. leave the computer for some time, say over night. No suspend or hibernate. Back to the computer next morning, unlock. Then Firefox appears frozen/hang, can't switch tab (clicking tab has no response, but not really frozen, sometimes responses after dozens of seconds of lag), page also has no response. Then after around half to 2 minutes, everything back to normal.

During the "hang", CPU load is load, no memory stress (swapping/paging).

Environment:

Firefox 123.0 (64-bit), (actually it bothered me for years)

Linux 6.6.15-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.6.15-2 (2024-02-04) x86_64 GNU/Linux

``` lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux trixie/sid Release: n/a Codename: trixie ``` Not related to particular Linux and/or kernel version.

CPU: Intel or AMD, not related. RAM: 64GB/96GB, free memory more than enough.

I will gather more detailed info later.

On bootup firefox opens a single window which says the following:

Sorry. We’re having trouble getting your pages back." We are having trouble restoring your last browsing session. Select Restore Session to try again.

The restore function succeeds in restoring 6 windows from the prior session, but this notice keeps appearing on every bootup.

Here are a few relevant details from about: config

• browser.sessionstore.max_resumed_crashes (is set to 1)
• browser.sessionstore.resume_from_crash (is set to true)
• No 3rd party third party cleaning software
• Two extensions, tab stash and tree tabs
• There are no entries in about:crash for this event

Have been using Firefox from 2004 with 5-10 open windows which appear on bootup as they existed from the prior session. This is the first occurance of this error. Appreciate your support. Here are a few system details:

1.) 28gb ram 2.) Linux ~ LMDE 5 (Elsie) 3.) Firefox ESR 115.8 (oesr) 64 bit.

I have constantly crashing tabs with FF 121.0.1 32-bit on Debian (happening since at least 120, and probably 114 or perhaps 115 ESR), and about:crashes has no listing of any tab crash reports; this hasn't been an issue until the most recent version. I'd like to report them so that they could hopefully be fixed, but reporting doesn't seem to be happening? Thanks.