Can't execute converted Slackware FF 37.0.1

[jimwg]

Greetings:

Need to update current Firefox from current 24.2 in my 32bit 3.0.1 XFCE sysytem.

I downloaded http://ftp.mozilla.org/pub/mozilla.org/ ... 686/en-US/ Firefox 37.0.1 and converted it into a module but when I attempt to run it I get "failed to execute command "firefox %u", no child process. Some Mint mavens suggested adding "ln -s /opt/firefox/firefox /usr/local/bin" But no dice.

Any hints greatly appreciated.

Jim in NYC

[tome]

Do not convert because you do not understand it.
1. Extract somewhere downloaded package.
2. Go to /usr/share/applications/ and copy mozilla-firefox.desktop to your desktop.
3. Open copied file in text editor and replace

Code: Select all

Exec=firefox %u

with

Code: Select all

Exec=/path/to/your/extracted/firefox-directory/firefox %u

4. use desktop modified "icon" (launcher) to start firefox

or see http://forum.porteus.org/viewtopic.php? ... 73&p=32534

[jimwg]

Thanks for the input, Tome, though you might still be able to help me since some kindly Mint Mavens showed that I can simply go ahead and use the converted module I made as I do others and keep my desktop clean of app icons without any extracting or editing stuff by creating a Firefox launcher in the panel with /firefox-bin in the command box. I'm now running a FF version even newer than what's in the Slackware library but there's a relatively minor hitch; It wants to update on start-up and says click to restart to do it. Should I pass up updating it or is there a way to do and make it stick?

Thanks for any hints!

Jim in NYC

[Bogomips]

diable... zap...

disable?

[brokenman]

Boot into fresh mode.
Open your browser and as suggested above disable the updating.
Close browser.
Now unpack the firefox module you created into a folder somewhere (say /tmp/unpacked)

Now you need to copy the config folder for firefox into the same folder and preserve the path.

Code: Select all

cp -a --parents /home/guest/.mozilla/firefox /root/.mozilla/firefox /tmp/unpacked

Now repack your module and your update conundrum is old news until the next time you create a firefox module.