More information
Greetings to you all. This problem has also been occurring for me, on a brand new MacBook Pro with SnowLeopard and a freshly installed, bookmarks excepted, Firefox 3.6. But it does not occur never has on my old G4 machines with Tiger and the same v. 3.6 of Firefox. All three machines are using the same "places.sqlite" (which now includes the bookmarks) file in the Firefox Profiles directory, the same preference settings for Firefox, and the same fonts (several 100's). I've done quite a bit of searching about, and I'd be inclined to think that it's an unhappy combination between the last Mac OS's and the last Firefoxes. I'm not offering a solution, but maybe some indications that might help others find one.
I get the same message as Glitch44, but the external volume, used for backups, which it is calling for is a straightforward Mac-formatted one (no Windows or Boot Camp there) that was purchased and put in use at the same time as the MacBook.
The fonts Firefox is calling for are rather unusual ones (some of them are for specialized linguistics, see list below) that are most unlikely to be used, even less so together, by anyone designing a website and its related css scripts. As far as mine are concerned, they date back to the days with Mac OS 9. They probably have never been used since, and certainly not on this new MacBook. But, again, they have been installed on it. Thanks to EasyFind, I also found out that they were registered in a number of files, such as:
Office Font Cache (10), in User/Library/Preferences/Microsoft/
At least 4 different files, in Library/Caches/com.apple.ATS/501/
AdobeFnt.lst and UserCache.bin, in Library/Application Support/Adobe/Acrobat
Their names also appear in three data files created by Word. Two of these are Word documents saved as Web html, and I'm gratified to find that Word has chosen to clutter them with the whole content of my font libraries! Yet, these html files are not even bookmarked in Firefox, so that's probably not where we have to look for an explanation.
As to why choosing "Allow" is seemingly not remembered, I discovered by fuddling about that the setting gets temporarily stored in a file called "sessionstore.js" (I had replaced it between program launches, and the messages asking for all those fonts came back right away). Why the setting doesn't get remembered permanently between bootups might be understandable to someone more knowledgeable than myself, from the following (found in a file called "kernel.log"):
Feb 25 15:30:42 [my user name] kernel[0]: firefox-bin[3783] Unable to clear quarantine `Avant Garde Mono ITCTT': 93
Feb 25 15:30:46 [my user name] kernel[0]: firefox-bin[3783] Unable to clear quarantine `ProFont': 93
Feb 25 15:30:49 [my user name] kernel[0]: firefox-bin[3783] Unable to clear quarantine `Classicalgreek-Translit.suit': 93
Feb 25 15:30:51 [my user name] kernel[0]: firefox-bin[3783] Unable to clear quarantine `BancoITC TT-Heavy': 93
Feb 25 15:30:54 [my user name] kernel[0]: firefox-bin[3783] Unable to clear quarantine `IranWeb2': 93
Feb 25 15:30:57 [my user name] kernel[0]: firefox-bin[3783] Unable to clear quarantine `ProFontISOLatin1': 93
Feb 25 15:31:00 [my user name] kernel[0]: firefox-bin[3783] Unable to clear quarantine `VNI-Times.fnt': 93
The digits between [] after "firefox-bin" vary from launch to launch.
Finally, choosing "Don't allow" seems to be a workaround, but that doesn't tell us what might come next. And the most nagging question still remains: why just those particular fonts, and not other fonts among those I've inherited from OS9, that are just as old, unused or peculiar?
Next day, one slight correction: those peculiar fonts hadn't been installed yet the first time Firefox started requesting them from the external drive. But it kept on requesting them even after allowing and after they had been installed on the local drive.