Firefox, what's not to love about this open-source web browser? Well, a number of users following the development work on Ubuntu 8.10 (the Intrepid Ibex) are feeling rather outraged over Mozilla Firefox 3.0.2 and later. In the latest Ubuntu packages, Firefox requires an EULA (End-User License Agreement) be accepted the first time you launch the browser.

After taking criticism from Linux vendors, Mozilla is now going to redo its end user license agreement and make it more friendly for open source.

Mitchell Baker has posted on her blog a notice that Mozilla will let us know today what solution they've come up with for the Firefox EULA dispute:Firefox without EULAs.

Mozilla received a lot of criticism from OS community for bundling EULA with Firefox builds. Even though they decided to remove EULA, earlier Ubuntu Ibex alpha builds still had the old EULA on.

As I reported yesterday, Mozilla has admitted that the Firefox EULA was flawed.

"Our good friends over at Mozilla are hosting the Mozilla 24 conference on Sept. 14th - 16th, spanning many continents and time zones. This event will feature presentations by industry leaders on the trends and technologies that will help shape the future of the Web..."

Most of us might be finding it difficult to run Mozilla Firefox 3 on Debian Etch, because of the old gtk libraries. And many might have problems installing the libraries themselves. Mozilla Firefox requires at least gtk 2.10. Here is a small howto I found to solve the problem. Basically it is to install the required libraries in a different location and make Firefox3 use them.

When trying to add the iceowl-extension package — Debian's renamed version of Mozilla's Lightning/Sunbird calendar app — to an existing Icedove installation in Lenny, I quickly learned from Mozilla's Calendar Weblog that a certain library package must be installed before you install Lightning/Iceowl.

You may have seen that the Debian project (my particular GNU/Linux distribution of choice) has decided to schedule fixed time-based releases in future. This has come as a surprise to many - including possibly some Debian developers - largely because of Debian's long-standing "we ship when it's ready" policy. So what caused this change of heart and is it a good idea.