Pšašanja ze slědujucym wobznamjenim pokazaś: Wšykne pšašanja pokazaś

Option "Open with" is grayed out on the download dialog

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… (cytajśo wěcej)

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

Pšašany wót wužywarja mdii pśed 1 tyźenjom

Slědne wótegrono wót wužywarja jonzn4SUSE pśed 1 tyźenjom

Can no longer use Firefox since update 128 on DEBIAN 12

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 lo… (cytajśo wěcej)

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 :)

Pšašany wót wužywarja alberic0000 pśed 1 mjasecom

Slědne wótegrono wót wužywarja user129772368266352146567327946278130777141 pśed 1 mjasecom

Firefox Debian significantly slower page loads than Chromium Debian

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 … (cytajśo wěcej)

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.

Pšašany wót wužywarja Samuel (+Uni) pśed 5 mjasecami

Slědne wótegrono wót wužywarja zeroknight pśed 5 mjasecami