TOPIC: MOZILLA
Toggling the appearance or non-appearance of the Firefox session exit dialogue box
One thing that I notice with Firefox installations in both Ubuntu and Linux Mint is that a dialogue box appears when closing down the web browser asking whether to save the open session or if you want to have a fresh session the next time that you start it up. Initially, I was always in the latter camp, but there are times when I took advantage of that session saving feature for retaining any extra tabs containing websites to which I intend to return or editor sessions for any blog posts that I am still writing; sometimes, composing the latter can take a while.
To see where this setting is located, you need to open a new tab and type about:config in the browser's address bar. This leads to advanced browser settings, so you need to click OK, answering a warning message, before proceeding. Then, start looking for browser.showQuitWarning using the Search bar; it acts like a dynamic filter on screen entries until you get what you need. On Ubuntu and Linux Mint, the value is set to true but false is the default elsewhere; unlike Opera, Firefox generally does not save sessions by fault unless you tell it to that (at least, that has been my experience anyway). Setting true to false or vice versa will control the appearance or non-appearance of the dialogue box at browser session closure time.
Using a variant of Debian's Iceweasel that keeps pace with Firefox
Left to its own devices, Debian will leave you with an ever ageing re-branded version of Firefox that was installed at the same time as the rest of the operating system. From what I have found, the main cause of this was that Mozilla's wanting to retain control of its branding and trademarks in a manner not in keeping with Debian's Free Software rules. This didn't affect just Firefox but also Thunderbird, Sunbird and Seamonkey with Debian's equivalents for these being IceDove, IceOwl and IceApe, respectively.
While you can download a tarball of Firefox from the web and use that, it'd be nice to get a variant that updated through Debian's normal apt-get channels. In fact, IceWeasel does get updated whenever there is a new release of Firefox, even if these updates never find their way into the usual repositories. While I have been known to take advantage of the more frozen state of Debian compared with other Linux distributions, I don't mind getting IceWeasel updated so it isn't a security worry.
The first step in so doing is to add the following lines to /etc/apt/sources.list using root access (using one of sudo, gksu or su to assume root privileges) since the file normally cannot be edited by normal users:
deb http://backports.debian.org/debian-backports squeeze-backports main
deb http://mozilla.debian.net/ squeeze-backports iceweasel-release
With the file updated and saved, the next step is to update the repositories on your machine using the following command:
sudo apt-get update
With the above complete, it is time to overwrite the existing IceWeasel installation with the latest one using an apt-get command that specifies the squeeze-backports repository as its source using the -t switch. While IceWeasel is installed from the iceweasel-release squeeze-backports repository, there are dependencies that need to be satisfied and these come from the main squeeze-backports one. The actual command used is below:
sudo apt-get install -t squeeze-backports iceweasel
While that was all that I needed to do to get IceWeasel 18.0.1 in place, some may need the pkg-mozilla-archive-keyring package installed too. For those needing extra information beyond what's here, there's always the Debian Mozilla team.
Sometimes it's a small change that matters...
Firefox 3.6 is now available and others are going on about more striking features, but it's a small change that I have noticed, which happens to be a good one too. Middle-clicking on a link in a tab used to open a new one on the right hand of the tab bar. Now, the new tab opens next to the one where the click was clicked, which is a good thing if you are previewing blog posts. It was something that Internet Explorer already did, so it's good to see cross-fertilisation of useful features; yes, Microsoft can come up with good ones too from time to time. Though not likely to make major headlines, this is the type of thing that makes for a better user experience, and a few of them together can be more beneficial than some big shiny new feature. In life, it's often the little things that make all the difference.
Testing a Firefox performance fix
Recently, I have been having problems with Firefox being sluggish, so I resorted to a Lifehacker tip to see if that helped. It was a matter of opening up the Error Console from the Tools menu and entering the following long line into the command bar and hitting the evaluate button:
Components.classes["@mozilla.org/browser/nav-history-service;1"].getService(Components.interfaces.nsPIPlacesDatabase).DBConnection.executeSimpleSQL("VACUUM");
It did the track once or twice, but its database hoovering claims are on trial as far as I am concerned. Keeping an eye on what's eating system resources will be on the menu too, especially after seeing what my brief foray with Ubuntu One was doing. A move to Google Chrome cannot be ruled out of the question, either.
A late "advance" sighting?
Somewhat infuriatingly, Google released its own browser, Chrome, into the wild near the end of last year, though only for Windows. My experiences with it on that platform are that it works smoothly, albeit without many of the bells and whistles that can be got for Firefox. While an unofficial partial port was achieved using Crossover Chromium and there is the Chromium project with all its warnings and the possibility to add a repository for its wares to Ubuntu's software sources, we have been tantalised rather than served so far. However, that was recently bettered by the release of early access versions. In reality, these can be said to be alpha versions so not everything works, but it's still Chrome and without the need for Windows or WINE. The rendering engine, most importantly, seems to be the equal of what you get on Windows, while ancillary functions like bookmark handling seem incomplete. In summary, the currently available deb packages are a work in progress, yet that's better than not having anything at all.
An option for when BBC's iPlayer will not allow you to "Listen Again"
Following my move to Firefox 3, the BBC's iPlayer became problematical again. While I eventually sorted it after a fashion, I am noting an option for the frustrated before talking more about that. Finding the links to the ram files for the BBC's Listen Again service can be a nightmare because of the Beeb's reliance on JavaScript to cloak things up, so it's useful to find somewhere where things have been deconvoluted for us. That's The Beebotron. It's really meant for users of the mobile internet, yet it serves well for those times when a mismatch between Firefox and RealPlayer on Linux derails the more usual way to do things.
Better font display in Firefox 3 on Ubuntu
Now that all bar one of the Firefox plugins that I use have been updated to work with it, I have finally jumped ship to 3 from 2.0.x. The move wasn't without its travails, though. For one thing, Google Toolbar stopped working, and I resorted to Googlebar Lite instead for my needs. Apart from that, the only other irritation has been the appearance of fonts in the new version.
In Firefox 2, it would seem that I was getting away without tweaking my system settings to be their most optimum. With 3, I could do that no longer because of an irritating and pervasive fuzziness that particularly afflicted k's and w's. The way out of this turned out to involve changing my Appearance Preferences (Preferences > Appearance from the System menu). The required attention was focussed on the Fonts tab, whereupon the Details button was brought into use.

In the resulting dialogue box, smoothing was set to "Subpixel (LCDs)" and hinting to "Slight". Closing down everything after making the required selections and a restart of Firefox was all that was needed to improve matters and more completely make myself at home with Firefox 3.

Opera and table display

I have encountered something very strange with my hillwalking blog, and I have to admit that am at something of a loss as to how to resolve it. Opera (version 9.x), it seems, is not displaying the date corresponding to the first post of a particular month. You can see the effect on the right for the current month and, yes, the tenth of the month has a post associated with it. What compounds the mystery is that the same issue doesn't affect this blog, so some further investigation is very much in order. However, the cascading element of CSS doesn't help much when trying to track down the cause of this sort of thing. While, it's irritating, I don't have any definite answers yet and so would appreciate some suggestions. Meanwhile, I'll be staying on the lookout for a fix. Curiously, all's fine on Firefox and IE.
Trying out Firefox 3 Beta 3 on Ubuntu
Keeping an eye on future browser releases helps to avoid any shocks when maintaining publicly available websites. Therefore, it should come as no surprise that I have been giving Firefox 3 a whirl. As it happens, I have had it going on both Windows and Ubuntu. With the former, I have not encountered any obvious problems, but I am wondering if the new bookmarking system will mean anything to me. For installation on Ubuntu, I used the following command (I think that I culled it from Tombuntu but can't remember offhand...):
wget -P ~ ftp://ftp.mozilla.org/pub/firefox/releases/3.0b3/linux-i686/en-US/firefox-3.0b3.tar.bz2 && tar xjf ~/firefox-3.0b3.tar.bz2 -C ~
The nice thing about the above is that it places the test installation in your home directory and away from Firefox 2. It also works regardless of what Linux distribution you have. The profiles get shared between versions, so a backup would be a good idea before you start to tinker. As with the Windows version, page loading and rendering is faster in the new version, but I found a problem with printing that, I hope, will get sorted before the final release. Another area for attention is font rendering: it could be sharper for sans serif fonts on Ubuntu and serif fonts on Windows. Otherwise, it works well on both platforms and I like the way that open windows are saved on exit, an excellent idea carried over from Opera.
Getting BBC iPlayer going on Ubuntu
Following on from my earlier musings on the subject, I finally have got the BBC's iPlayer going on my Ubuntu set up. To accomplish this, I needed to get my hands on the plug-in files nphelix.so and nphelix.xpt. Once that was done (more on how I did that later), I popped the former into /usr/lib/firefox/plugins, the latter into /usr/lib/firefox/components and restarted Firefox. I think that a system restart might have helped me too, even if it was done for another reason. The files themselves were culled from the RealPlayer folder populated by the installer (realplay-10.0.9.809-linux-2.2-libc6-gcc32-i586.bin was what I used) that I had downloaded from the Helix Community website; the plugin files were found in the mozilla subfolder under RealPlayer.

Another thing that I did was to fire Alacarte, Gnome's menu editor, and add Configuration Editor (also known as GConf, I believe) to the System tools submenu on the Applications menu. Once added to the menu, I fired up the said application. Navigating to desktop > gnome > url-handlers > rtsp, I changed the command to realplay "%s". While I don't know if this helps, it certainly was no hindrance and I got the result that I wanted and in high quality audio too.
