This is an error that I have started to see a lot in the last few weeks. First, it was with Piwik and latterly with WordPress.com Stats. For the record, I have never seen it on up to date systems but always with IE6 and at page unloading time. The CPU usage hits 100% before the error is produced and that has had me blaming JavaScript in error; it isn’t the cause of all ills. In fact, the cause seems to be a bug in a certain release of Adobe Flash 9 but I am of the opinion that the inclusion of certain features in a Flash movie are needed to trigger it too. I don’t have the exact details of this but WordPress.com Stats worked without fault until a recent update and that is what is making me reach the conclusion that I have. That observation is making me wonder whether we are coming to a point where Flash compatibility is something that needs to factored into the use of the said technology in a website or web application. Updating Flash will solve the problem on the client but it might be better if it wasn’t triggered on the server side either.
Archive for May, 2009
64-bit Firefox plugins?
My laptop has both Windows Vista and Ubuntu on there with WUBI being the facilitator of the peaceful coexistence. However, what I either forgot or never realised was that it was the 64-bit variant of Ubuntu 9.04 that has found its way onto the thing. For the most part, it works well but there is one catch that I recently encountered: not every Firefox plugin or add-on is 64-bit compatible. Google Gears is one such example but other very useful and pervasive helpers have the same affliction. RealPlayer is one and Adobe’s Flash is another. Apparently, you can still download the 32-bit release versions and use nspluginwrapper to get them going. That worked for RealPlayer but seemingly not for Flash; more investigation may be needed on that one. Other remedies like using 32-bit Firefox (if it runs, of course) or alpha versions of what Adobe offers can be tried too. For more details on the conundrum, feel free to take a look at the Mozilla Project’s offering on the subject. It almost goes without saying that I’d wish that there was more awareness of the 64-bit Linux world but I remain glad to have met this rough edge before taking the plunge with my main system.
About Perl’s Binding Operator
This piece is as much an aide de memoire for myself as anything else but putting it here seems worthwhile if it answers questions for others. The binding operators, =~ or !~, come in handy when you are framing conditional statements in Perl using Regular Expressions, for example, testing whether x =~ /\d+/ or not. The =~ variant is also used for changing strings using the s/[pattern1]/[pattern2]/ regexp construct (the “s” stands for “substitute”). What has brought this to mind is that I wanted to ensure that something was done for strings that did not contain a certain pattern and that’s where the !~ binding operator came in useful; ^~ might have come to mind for some reason but it wasn’t what I needed.
A case of the reverse Midas touch?
Last week, a power cut put my main home PC of of action. It may have been recoverable if that silly accident of a few weeks back hadn’t happened but a rebuild is progress. That hasn’t been going so well but I somehow am managing to remain hopeful that an avenue of exploration will yield some fruit. Thoughts of throwing in the towel and call in the professionals rather than throwing good money after bad are gathering. The saga is causing me to question the sense of self building in place of buying something ready built. Saying that, they can have their off days too.
In the meantime, I have been displaced onto the spare desktop PC and the laptop. In other words, my home computing needs are being fulfilled to a point though the feeling of frustrated displacement and partial disconnection from my data remains; I have been able to extricate most of my digital photos and my web building so things are far from being hopeless. With every disappointment, there remains an opportunity or two. The spare desktop runs Debian so I have been spending some time seeing if I can bend that to my will and it can be done, sometimes after a fashion.
A few posts should result from this period, not least regarding working with Debian. On the subject of hardware, I’ll not elaborate until the matter comes to a more permanent resolution. From past attempts (all were successful in the end), I know that the business of PC building can feel like a dark art: you are left there wondering why none of your efforts summon a working system to life and then it all comes together in the blink of an eye and you wonder why all the effort was expended. The best analogy that I can offer is awaiting a bus or train; it often seems that the waiting takes longer than the journey. Restoring my home computing to what it was before is a mere triviality compared to what some people have to suffer but resolution of a problem always puts a spring in my step.
Old tricks can still save money
Recently, there was no sound coming out from my main PC and I began to suspect the sound card, an aging Guillemot Maxi Sound Muse. Naturally, my thoughts turned to acquiring and those in stock at PC World seemed to have unknown or dubious Linux compatibility. However, I powered the machine down for the night and re-seated the card in its slot the following morning. That was enough to solve the problem and I held onto my cash, never a bad thing and especially so in these times. It’s always nice to know that and old trick still has its place.
Getting Fedora working in VirtualBox
After a hiatus induced by disk errors seen on start up, I have gone having a go with Fedora again. In the world of real PC’s, its place has been taken by Debian so virtualisation was brought into play for my most recent explorations. I could have gone with 10, the current stable version, but curiosity got the better of me and I downloaded a pre-release version of 11 instead.
On my way to getting that instated, I encountered two issues. The first of these was boot failure with the message like this:
FATAL: INT18: BOOT FAILURE
As it turned out, that was easily sorted. I was performing the installation from a DVD image mounted as if it were a real DVD and laziness or some other similar reason had me rebooting with still mounted. There is an option to load the hard disk variant but it wasn’t happening, resulting in the message that’s above. A complete shut down and replacement of the virtual DVD with a real one set matters to rights.
The next trick was to get Guest Additions added but Fedora’s 2.6.29 was not what VirtualBox was expecting and it demanded the same ransom as Debian: gcc, make and kernel header files. Unfamiliarity had me firing up Fedora’s software installation software only to find that Synaptic seems to beat it hands down in the search department. Turning to Google dredged up the following command to be executed and that got me further:
yum install binutils gcc make patch libgomp glibc-headers glibc-devel kernel-headers kernel-devel
However, the installed kernel headers didn’t match the kernel but a reboot fixed that once the kernel was updated. Then, the Guest Additions installed themselves as intended with necessary compilations to match the installed kernel.
The procedures that I have described here would, it seems, work for Fedora 10 and they certainly have bequeathed me a working system. I have had a little poke and a beta of Firefox 3.5 is included and I saw sign of OpenOffice 3.1 too. So, it looks very cutting edge, easily so in comparison with Ubuntu and Debian. Apart from one or niggles, it seems to run smoothly too. Firstly, don’t use the command shutdown -h now to close the thing down or you’ll cause VirtualBox to choke. Using the usual means ensures that all goes well, though. The other irritation is that it doesn’t connect to the network without a poke from me. Whether SELinux is to blame for this or not, I cannot tell but it might be something for consideration by the powers than be. That these are the sorts of things that I have noticed should itself be telling you that I have no major cause for complaint. I have mulled over a move to Fedora in the past and that option remains as strong as ever but Ubuntu is not forcing me to look at an alternative and the fact that I know how to achieve what I need is resulting in inertia anyway.