yes it was, but now i've since given up and reinstalled jaunty in a VM under virtualbox where i run firefox 3.5 as shiretoko and have removed my native jaunty install where this problem existed, and here this problem has gone away.
yes it was, but now i've since given up and reinstalled jaunty in a VM under virtualbox where i run firefox 3.5 as shiretoko and have removed my native jaunty install where this problem existed, and here this problem has gone away.