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

How to update Firefox ESR 115.14.0 to 128.1.0?

I'm a newbie using Debian and Deb 12 ships with Firefox ESR and I've decided to stick with it instead of the regular release, 'cause it breaks some extensions I have. How… (cytajśo wěcej)

I'm a newbie using Debian and Deb 12 ships with Firefox ESR and I've decided to stick with it instead of the regular release, 'cause it breaks some extensions I have. However, I want to upgrade to the latest ESR version, how do I do it? I tried going to (https://www.mozilla.org/en-US/firefox/all/#product-desktop-esr), but the file for linux 64 bit is a .tar.bz2 file, which I have no idea how to compile.

Pšašany wót wužywarja spandanjit.05 pśed 2 dnjoma

Slědne wótegrono wót wužywarja cor-el pśed 13 góźinami

Firefox 128 ESR-next Releases not reading firefox.cfg

My company has been using the same customized autoconfig.js without issue since last year's FF 115 esr release on our Ubuntu servers. cat /opt/firefox-115.13.0esr/defau… (cytajśo wěcej)

My company has been using the same customized autoconfig.js without issue since last year's FF 115 esr release on our Ubuntu servers.

cat /opt/firefox-115.13.0esr/defaults/pref/autoconfig.js pref("browser.tabs.inTitlebar", 0); pref("general.config.filename", "firefox.cfg"); pref("general.config.obscure_value", 0); pref("general.config.sandbox_enabled", false); pref("pdfjs.annotationEditorMode", 1);

Now we are testing the 128 esr next releases with the same config and getting the failed to read the configuration file. please contact your system administrator error

cat /opt/firefox-128.1.0esr/defaults/pref/autoconfig.js pref("browser.tabs.inTitlebar", 0); pref("general.config.filename", "firefox.cfg"); pref("general.config.obscure_value", 0); pref("general.config.sandbox_enabled", false); pref("pdfjs.annotationEditorMode", 1);

If remove pref("general.config.obscure_value", 0); or set it to 1, the error goes away, but our actual firefox.cfg does not get read and are configs are not present at all.

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

Slědne wótegrono wót wužywarja cor-el pśed 4 dnjami

Deploying Firefox Developer Edition with Intune

I'm having trouble find clear directions online on how to import Firefox Developer Edition into my Intune App Catalog to deploy it to users. I was able to convert the .ex… (cytajśo wěcej)

I'm having trouble find clear directions online on how to import Firefox Developer Edition into my Intune App Catalog to deploy it to users. I was able to convert the .exe installer into a .intunewin file but Intune won't import it for some reason. All the other directions i keep finding just direct me to creating a custom configuration policy around FireFox but it looks like it is just the basic Firefox for Enterprise.

I'm hoping to either get directed to actual directions for this or even a .msi installer for the developer edition. Does that exist?

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

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

Issue getting Firefox to launch for the first time, directly to a clicked link, without start page/default browser prompt

We are deploying Firefox installed via the v122 binary on Ubuntu 22.04.4 Server w/ubuntu-desktop-minimal --no-install-recommends (we need to have no-user-interaction inst… (cytajśo wěcej)

We are deploying Firefox installed via the v122 binary on Ubuntu 22.04.4 Server w/ubuntu-desktop-minimal --no-install-recommends (we need to have no-user-interaction install). We are using an Ansible playbook to copy over and unarchive the tarball, then create a firefox/distribution folder in the install directory and copying a profiles.json file to said folder, links the install directory to the /usr/bin/local directory, and setting firefox.desktop as the system default browser.

Using the instructions from: https://mozilla.github.io/policy-templates/

What we are hoping to accomplish is the user who has never launched Firefox will click on a link in an application, which will launch Firefox and go directly to the requested page. As it stands right now, the first time a user clicks the link, it launches firefox and shows a start page. The user must then close this window, and click the link again. This brings up a "Use Firefox as the default browser" prompt, which the user must accept, but then does not display the link. The third time the user clicks the link, the requested page pops up, and works from this time out.

We would like to have this be a one-click experience for the user. Looking at the options in about:config after getting firefox to launch, it appears firefox is not getting the options from the profiles.json file. Are we missing something about placement of this file? Missing some lines? Should we be using AutoConfig instead? Thank you for any assistance!

{

   "policies": {
       "Homepage": {
           "StartPage": "none"
       },
       "Preferences": {
           "browser.shell.checkDefaultBrowser": {
               "Value": false,
               "Status": "default",
               "Type": "boolean"
           },
           "browser.shell.skipDefaultBrowserCheckOnFirstRun": {
               "Value": true,
               "Status": "default",
               "Type": "boolean"
           },
           "browser.startup.homepage_override.mstone": {
               "Value": "ignore",
               "Status": "default",
               "Type": "string"
           }
       },
       "PopupBlocking": {
           "Default": false
       },
       "DontCheckDefaultBrowser": true,
       "OverrideFirstRunPage": "",
       "OverridePostUpdatePage": ""
   }

}

Pšašany wót wužywarja JuniorDevOps pśed 4 mjasecami

Slědne wótegrono wót wužywarja Mike Kaply pśed 4 mjasecami