I'm using wayland, with i915 early loading. Right now, with firejail set up, Firefox starts instantly. But running $ /usr/bin/firefox to bypass firejail takes 20s to load, with no apparent error message...
If you want a new tab to open without a URL known yet, then firefox --new-tab (i.e. omitting a URL) will open a new window, which is probably not the desired behavior. Instead, use the following to open a new tab in the existing window (with the cursor set to the URL bar, so that you can enter your prompt right away):
I have a few questions for you guys and please be patient with this dumb newbie Linux user. How do I switch the Firefox on to the ESR channel on the firefox? Or am I to install it seperately from the regular firefox? Or do I just download the installer from the Mozilla and it will take care of itself?
Once this is done, you should have firefox ESR 68.9 installed (correct at time of publishing). The repo has now been added which also updates Firefox ESR, when updates are available. Open and check Firefox ESR all works as you will need to add your favorite extensions (then re-apply earlier saved settings) /configure ESR settings, and import bookmarks (that you saved earlier)
In firefox I cant move the map with left-click and moving the mouse. But I can zoome in and out with scroll wheel. And the issue only exists on (On it works). The mouse pointer over the map changes to a hand-icon, but left-click and moving the mouse around doesnt do anything.
The only marginal difference is, that when moving with rightclick on linux the context-menu opens at the start (rightbutton down event) and on windows the context menu opens at stop moving (rightbutton up event). What is no problem at all.
If it is running, quit it. If it doesn't appear to be running but appears in the list from ps ax, kill it by running killall firefox, waiting a few seconds, then running killall -KILL firefox. If you don't see firefox: no process found after the second killall command, run that second command again. If you still don't see it, reboot (or you may want to try running it with sudo too, thought that won't usually help).
Strange as it seems, I can't find information how I can set a default nice value for a program (not for a user or a group!). I would like to start all chrome and firefox instances with a nice value of 10. What would be the most appropriate solution?
Open URL in a new private browsing window. If a private browsing window is already open, a new tab is opened in the existing window. Firefox 29 and later only. Does not work in Firefox 31 on linux mint 17 nor on Firefox 48 on Windows 7. URL opens in a non-private window.
First, you need to enable rpm fusion Installing Free and Nonfree Repositories and reboot. Next, rpm-ostree install ffmpeg should provide firefox the codec, and then reboot the system again to apply the change.
P.S.: I noticed that on my Windows 8.1 machine the plugin still works. At my laptop with arch linux however I don't even find the right plugin with the addon search. Does this have something to do with the architecture or is the addon just not available anymore and I should copy it somehow from one machine to the other?
The Mozilla Foundation is a valuable contributor to the free softwarecommunity; it has, among other things, provided us with a free browserwhich has restored the notion of standards to the World Wide Web. Therelationship between the Foundation and Linux distributors has occasionallybeen a little bumpy, however. Mozilla's trademark policies have createdstress for distributors, a few of whom have decided to leave thetrademarked names behind altogether. The Foundation's security update andmaintenance policies have also made life harder, sometimes having theeffect of force-upgrading users to newer versions in otherwise stabledistributions. To some, it seems that Mozilla's main interest is now itsWindows users, with Linux support relegated to second-tier status.At the recent Firefox summit, the Foundation got together withrepresentatives from Red Hat and Novell and faced the problem directly:Historically, there has been a great deal of tension betweenmozilla.org and the Linux distros, notably over maintenance ofbranches, divergence between distros, and lack of sustainedcommunication between the groups. All seemed in agreement thatcloser cooperation and dividing responsibilities appropriatelywould benefit everyone involved. A number of changes were proposedthat have general consensus among the stakeholders.What came out of this meeting was an agreement on a number of changeswhich, going forward, should improve the relationship between Mozilla andthe distributors; it should also make life better for Linux-based Mozillausers. A new group of maintainers - representing Linux distributors - will bepulled together "in the Firefox 3 timeline." These maintainers willhave a much bigger say on what goes into the Linux builds of Firefox andwill be able to help ensure that the browser integrates better with Linux.They will also have the explicit goal of moving many of the patchescurrently carried by distributors into the Firefox mainline, decreasingtheir divergence from the mainline (and from each other).Another advantage of pushing the patches up, evidently, is that it willmake compliance with the Firefox trademark rules easier, since there willbe fewer patches to get rubber-stamped.These maintainers will also have a bigger role in the long-term upkeep ofFirefox releases. Red Hat's Christopher Aillon notesthat this group will be maintaining Firefox 1.5 past the date when theMozilla Foundation plans to let it go. This work should help thedistributors keep that version secure into the future, with the result thatthey need not push their users to the 2.0 release before they want to gothere.The Mozilla Foundation has also recognized that most Linux users runversions of Firefox built by their distributors rather than the officialMozilla builds. In the future, distributor packages will be availabledirectly from the Mozilla web pages. That, too, should make life easierfor the user community. Overall, this new cooperation seems like a stepin the right direction; having Mozilla more tightly tied to the freesoftware community can only be a good thing.These changes are unlikely to bring Debian back into the Firefox camp,however, since they will still see the trademark policy as not beingDFSG-free. Debian's policy of shipping "iceweasel" will almost certainlycontinue. But there is an interestingconversation going on about how iceweasel is shipped as well.The issue is this: on a Debian system, it is still possible to type: apt-get install firefoxWhat the packaging system will do, however, is install iceweasel. Giventhat the driving force behind the switch in the first place was trademarkusage, it seems unlikely that the Mozilla people will be amused by thisbehavior - though they have made no public statements on it as of thiswriting. Moving away from Firefox as a result of disagreement with therules attached to that name is arguably a reasonable thing to do. But,once that decision is made, the right thing is almost certainly to moveaway from the "firefox" name altogether - before the next round of "ceaseand desist" letters shows up. (Log in to post comments) Firefox and Linux distributors Posted Dec 7, 2006 2:01 UTC (Thu) by Frej (subscriber, #4165) [Link]
They are moving away from it, as per normal Debian process.
The replacement package is part of the series of steps needed to transition users with "firefox" installed to iceweasel, as they have been instructed. They need to ensure these users are transitioned in oder to be in compliance.
Additionally, they were given legal permission to use the mark in this context in the past. I'm sure some legal principle allows them to _refer_ to the name in a historical basis.
Lastly, extending trademarks to _exclusive_ ownership of _package names_ is quite a reach. A package claiming to provide the same functionality as another package will be installed for that other package name in certain circumstances. This is what iceweasel does. A trademark may be used by others, but not to mislead. However, apt will tell you quite explicitly that it is installing iceweasel.
Debian's behaviour and Mozilla's funny bone Posted Dec 7, 2006 15:24 UTC (Thu) by coriordan (guest, #7544) [Link]
It was alleged during the firefox discussions that the developers, while obviously providing their patches in the published firefox .debs, were not making access to their patch development very transparent. Supposedly the patches were developed and tracked in a version control system which was not public-accessible, and the mozilla folks wanted to be able to have access to this. In many cases I bet such tracking systems exist without needing to be accessible, but the debian patches to firefox were larger than some (firefox is larger than many programs), and the mozilla folks seem more concerned about the third-party patch quality than most. Also alleged was that the purpose of some of the patches was not always clear.
So I think it can be honestly asked whether the debian packagers and the mozilla developers will find ways to work together more closely on changes to the codebase. My impression is that the obstructions to cooperation have been a mix of cultural, ideological, structural, and technical, and so I don't expect perfect cooperation, but if the various assertions I read in the mailing lists and BTS had merit, then it seems Debian (and Mozilla) could find ways to cooperate more closely.
My personal expectation is that Mozilla will adopt Debian patches more readily as they have (partially) learned the cost of the rift, and that Debian will more readily push them for the same reasons. There continues to be minor bad blood though.
Firefox and Linux distributors Posted Dec 8, 2006 8:36 UTC (Fri) by erwaelde (subscriber, #34976) [Link]