You are not logged in.
I have recently unpacked firefox to ~/bin, and used debian alternatives to point to the executable file.
Dead easy, and one doesn't need to be root to update.
I guess I am saying this to give those who know better the chance to inform me of potential problems, if any.
Offline
^Do I understand correctly: Using firefox from ~/bin/firefox makes it update automatically? Does it also work with firejail that way?
I'm not a friend of the usually recommended /opt/firefox either, because of being root for an update (although firejail works fine that way).
Offline
I just tried it myself:
- Downloaded FF57.0.3, extracted to ~/bin, started it
- Opening the "Info" window it instantly downloaded FF57.0.4 and offered the installation.
- After restarting it the installation finished.
Offline
^Do I understand correctly: Using firefox from ~/bin/firefox makes it update automatically? Does it also work with firejail that way?
...
Yes, the update is automatic. The download of the update occurs in the background and the next time you start Firefox, the update is incorporated.
Re. firejail, I'm guessing it would depend on how you configure things. I found firejail too difficult and don't use it any more
Using the Openbox (3.5.2) session of Lubuntu 14.04 LTS but very interested in BL :)
Offline
Thank you @vinzv and @vasa1 for the clarification.
Firejail basic usage does not really look to be complicated, simply firejail firefox -p --no-remote works (or using the full path for firefox is required sometimes). As there is a sandbox, from within Firefox folders are not available, only Downloads on default (other ones can be set too). Other browsers like Ungoogled Chromium or Vivaldi also work with firejail.
Offline
I just tried it myself:
- Downloaded FF57.0.3, extracted to ~/bin, started it
- Opening the "Info" window it instantly downloaded FF57.0.4 and offered the installation.
- After restarting it the installation finished.
Yes, this is why I do it this way. And using galternatives to set it as x-www-browser makes life very easy.
Offline
Yes, this is why I do it this way. And using galternatives to set it as x-www-browser makes life very easy.
I start liking the idea. But what about dependencies? Is the FF version from repositories needed in parallel?
Offline
I start liking the idea. But what about dependencies? Is the FF version from repositories needed in parallel?
No, not at all. Firefox-esr simply remains as an option if you leave it there, but in my experience you can remove it without any problems.
Offline
@dhalgren Thanks! Will try that and check if there occur any problems.
Offline
@vinzv Enjoy!
Offline
I just tried it myself:
- Downloaded FF57.0.3, extracted to ~/bin, started it
- Opening the "Info" window it instantly downloaded FF57.0.4 and offered the installation.
- After restarting it the installation finished.
Where is bin exactly in home directory ?
Started it ? How ? Using firefox command in terminal ?
Offline
Where is bin exactly in home directory ?
Started it ? How ? Using firefox command in terminal ?
I placed it in /home/<username>/bin/firefox/... and started it from terminal.
But I guess using update-alternatives or manually symlinking is more convenient. See the great howto by BLizgreat! here.
Offline
vinzv wrote:I just tried it myself:
- Downloaded FF57.0.3, extracted to ~/bin, started it
- Opening the "Info" window it instantly downloaded FF57.0.4 and offered the installation.
- After restarting it the installation finished.Yes, this is why I do it this way. And using galternatives to set it as x-www-browser makes life very easy.
Debian alternatives are system-wide. Do you really want other users to access the firefox in your personal ~/bin?
For just one user (ie you) you can make a personal symlink instead, something like:
ln -s path/to/your/firefox ~/bin/x-www-browser
so (as long as ~/bin is in $PATH) your local x-www-browser will override /usr/bin/x-www-browser.
normal service will be resumed as soon as possible
Offline
For just one user (ie you) you can make a personal symlink instead, something like:
ln -s path/to/your/firefox ~/bin/x-www-browser
so (as long as ~/bin is in $PATH) your local x-www-browser will override /usr/bin/x-www-browser.
On a shared or locally networked computer I would absolutely agree, but with just me?
I see no real reason because I am working to remove my paranoia. (joke)
But the method of linking that you have provided is good to know, because I'm not very good with that stuff.
Last edited by dhalgren (2018-01-10 02:57:27)
Offline
Hi Busenlabs team.
I did read all messages above and I realized that BusenLabs still doesn't support newer Firefox releases (quantum based). There's no prevision to add it to distro's repositories ?
Thanks in advance.
Leidson
Offline
BusenLabs still doesn't support newer Firefox releases (quantum based). There's no prevision to add it to distro's repositories ?
No and there never will be
BunsenLabs follows Debian (old)stable and so uses the ESR version of Firefox because we prefer not to test all the nasty new bugs such as the recent vulnerability that let FF Quantum act as an attack vector for Meltdown — the ESR version didn't do that 8)
If you want to test the latest FF bugs then run it from $HOME, see the _many_ posts above for details, it is _very_ easy to do
Offline
Now it's Firefox Quantum v58. Here is a good description for Stretch based Debian with apt pinning bad description with horrible apt pinning for installing Firefox, so don't follow this guide.
Last edited by martix (2018-01-24 20:18:10)
Offline
Here is a good description for Stretch based Debian with apt pinning for installing Firefox.
No, it's awful, please don't follow that.
Pinning is not something that should be copy&pasted, don't use it unless you understand it
Just run FF from $HOME, I thought we had already established that was the best option?
Offline
^Indeed, forgot about that, $HOME is clearly a better place.
But why is it a bad thing to give priority for those four packages from sid to install firefox? Basically it could be available in stable right now (as it is on other distros), but because of Debian policy obviously it isn't in stable, only in sid.
Actually thinking about it, Firefox-ESR should be removed too via apt, and if $HOME is preferable, simply downloaded from Mozilla and installed in ~.
Offline
But why is it a bad thing to give priority for those four packages from sid to install firefox?
I don't want to have to help fix FrankenDebians here on these boards so I am trying to discourage that sort of nonsense.
If Debian stable is too crusty for you, run one of those trendy rolling-release distributions instead.
Offline