Quite some issues here with www-client/mozilla-firefox-2.0.0.1 and www-client/mozilla-firefox-2.0.0.1-r2 after upgrading from the 1.* version. I think they are somewhat related so I'll deal with all of them in one bug report. I've been running the source-compiled firefox versions successfully for some years now, until now. * If I download files (for instance archives) then firefox sometimes doubles the extension. Some other times it postfixes the .bin extension. Some files still download correctly, for instance when doing a "save page". Example: At http://www.getjar.com/products/3334/OperaMini click on the first download link titled "opera-mini-3.0.6655-advanced-int.jad" (points to http://download2.getjar.com/downloads/web/pub/9531/opera-mini-3.0.6655-advanced-int.jad) quite a bit down the page, to download a file that gives me troubles. It ends up on my hard drive as opera-mini-3.0.6655-advanced-int.jad.jad (notice the double extension). In the error console the only error is: Error: [Exception... "Component returned failure code: 0xc1f30001 (NS_ERROR_NOT_INITIALIZED) [nsIMIMEInfo.primaryExtension]" nsresult: "0xc1f30001 (NS_ERROR_NOT_INITIALIZED)" location: "JS frame :: file:///usr/lib/mozilla-firefox/components/nsHelperAppDlg.js :: anonymous :: line 238" data: no] Source File: file:///usr/lib/mozilla-firefox/components/nsHelperAppDlg.js Line: 238 There are no errors in the terminal from which I started firefox. * Downloading generally is more problematic. Files that don't exist remotely (dead-links) or are hard to reach tend to end up as 0-sized files on my hard disk without any further warning. I believe in the older versions at least the Download window would stay open with the file listed with an empty progress bar. Now the file is never listed in the download window. * Firefox seems to be slower on some web pages that used to be only a little slow. It also stalls while loading the page (and not yet showing it) and while scrolling. An example is www.gentoo-portage.com. This is hard to measure but at least the stalls are really there I think. * I'm experiencing random non-reproducible (at the moment) crashes. Both of the type where everything freezes and of the type where everything just disappears. Thx Reproducible: Always [ebuild R ] www-client/mozilla-firefox-2.0.0.1-r2 USE="gnome ipv6 java mozbranding xinerama -debug -filepicker -mozdevelop -moznopango -restrict-javascript -xforms -xprint" LINGUAS="nl -ar -bg -ca -cs -da -de -el -en_GB -es -es_AR -es_ES -eu -fi -fr -fy -fy_NL -ga -ga_IE -gu -gu_IN -he -hu -it -ja -ka -ko -ku -lt -mk -mn -nb -nb_NO -nn -nn_NO -pa -pa_IN -pl -pt -pt_BR -pt_PT -ru -sk -sl -sv -sv_SE -tr -zh -zh_CN -zh_TW" 36,396 kB
Created attachment 109814 [details] emerge --info I forgot to mention that: * I tried safe-mode, no luck. * It also neglects to visit my custom homepage after startup and instead goes to my homedirectory (viewed like ftp). * I haven't prelinked yet so maybe I should do that first before really comparing performance...
1/ Try with a fresh profile. 2/ If you still have problems, try w/ mozilla-firefox-bin and report back please.
I've done the tests: * After deleting .mozilla and restarting the differences are: - Homepage problem seems gone. (But when I restored my old .mozilla I didn't have the homepage problem either when I restarted firefox). - Still download extension problems but at least each time an entry appears in the download window. So, does not solve most of the problems. However I noticed that when downloading to the desktop (I always used to download to a specific download folder, letting firefox ask me every time, but the default settings just downloaded to the desktop) a file which used to end up 0-sized now downloaded to full length. When I changed the settings to ask me where to download to I had the old behaviour again as described in the differences above. Maybe I should note that I download to a FAT32 partition (like I've done for years) and that my homepage also is a html-file on that partition. File access should be ok because I can write the files manually. * mozilla-firefox-bin with a fresh profile: On top of the solved things from the source-compiled firefox with fresh profile it now downloads the old 0-sized file properly to full length in my specific download folder. It changes the extension to .tar.gz.tar however (the mime type recognition seems to be different: with the bin it is TAR, with the source version it is Tarball or something if I remember correctly). The example .jad file extension problem is not yet solved. I noticed that in stead of replacing an old file that was present from previous tries it made a new file called opera-mini-3.0.6655-advanced-int.jad(2).jad (notice the (2) is behind the first extension!). * I can't say anything more about the other problems because I need to run firefox longer. I'll just reopen the bug so you see it is active. Hope this information helps. Thanks in advance.
It seems there are at least two of us with the same problem now: http://forums.gentoo.org/viewtopic-p-3907702.html#3907702 .
Same with 2.0.0.2?
I checked my main issue and it's still around with 2.0.0.2 (giving me opera-mini-3.1.7203-advanced-int.jad.jad).
I couldn't reproduce the main bug. What you do, left click -> save link as, or directly clicking in the link and choose save to?
I just click the link. It pop-ups a dialog with "Save to disk" preselected (I have it set to ask where to put it). It recognizes the file (or rather does not) as a JAD file (for opening it suggests "less"). I click OK and then click again to save it in my regular download-directory, which I've been using since a lot of versions back.
I just tried creating a fresh user and tested everything again. It now appears that the (main) problem does not happen when saving files to linux partitions (desktop, home, tmp, ...), but only to FAT32 partitions. I must have tested this before as I made notes about FAT32 quite early in my previous comments, but I don't know why now I'm seeing something different. Here's my hunch at the moment: A known issue there has always been with FAT32 partitions is that filenames with only upper case chars (I suppose this goes for extensions by itself too) are being renamed to lower case. I suppose this is what happening: .JAD becomes .jad and firefox can't find the file anymore, leading to 0 size. Or, firefox finds .jad different from the original extension and decides to add it (again) (as common in save dialogs I suppose). Maybe in firefox 2.0 some extensions are converted to upper case for some reason, or not converted to lower case any more, as with firefox 1.5?. Since in a long time I've never seen this with the old firefox. Another possibility is that my FAT32 partition settings have become faulty and I've wasted your time :-(.
Unfortunately I might equally be wrong since I added "shortname=winnt" to my fstab to use another rule for FAT32 short filenames and the extensions still double. In fact the leftmost extension is the one you enter in the dialog, while the rightmost one is appended automatically for FAT32, but not for linux partitions (reiserfs in my case). For instance entering only "blabla" as filename in the dialog would give blabla.jad on FAT32 and blabla on reiserfs.
Well, I've come across quite a lot of identical bug reports: - https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/65164 - https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/105474 and also forum users mentioning exactly the same problems as I have: - http://forum.ntfs-3g.org/viewtopic.php?t=486 - http://forum.ntfs-3g.org/viewtopic.php?t=474&highlight=firefox I will try out some things and let you know.
Adding ",dmask=000,fmask=111" quick-fixed it for me too as described in the above links. However I'm concerned about possible side-effects. This should need a proper fix (which shouldn't be too hard as previous versions did work correctly) and firefox 2.0.0.3 doesn't yet have it. This is my original fstab entry btw: /dev/hda5 /Data vfat noatime,user,owner,defaults,gid=users,uid=pjv,umask=002,exec,managed,shortname=winnt,utf8 0 0 I quickly looked up related bugs at mozilla and found these: - https://bugzilla.mozilla.org/show_bug.cgi?id=270159 - https://bugzilla.mozilla.org/show_bug.cgi?id=336113 - https://bugzilla.mozilla.org/show_bug.cgi?id=356431 I suggest you go on and settle this upstream... You can consider all of symptoms fixed. Cheers,
Is this still an issue with latest 2.* and 3.*?
I no longer have the same setup and FAT32 partition, but I am still using the quick-fix described above with an NTFS partition. Not sure it is still necessary. Since this bug has been quiet for two years and therefore has become difficult to test, I agree to closing the bug for now. If I ever find time I might test if I can remove that quick-fix. Quite demotivating to see that even the upstream bug (https://bugzilla.mozilla.org/show_bug.cgi?id=356431) never caught on, and yet a lot of effort was put into it by reporters.
