117066 - Downloads fails completely

Status: VERIFIED WORKSFORME

(Core Graveyard :: File Handling, defect)

Description

[Jarmo]

Probably a dupe of:
"69938"
"115442"
"116132"
maybe also:
"106284"

_No_ downloads seems to work. In some cases a file is created int /tmp/.
I detected this with mp3.com (mozilla did not launch xxms).

Comment 1

[Asa Dotzler [:asa]]

->file handling or necko.

Comment 2

[Boris Zbarsky [:bzbarsky]]

Can you download new mozilla build binaries?  What sites have you tested that 
fail other than mp3.com? Does going to:

Edit > Preferences > Navigator > Helper Applications 

and clicking the "Reset" button at the bottom of the panel help?  (please back 
up your prefs.js before doing this so it can be attached to this bug if needed).

Comment 3

[Jarmo]

Did a clean rebuild last night. Seems to work now (clean build takes 4 hours on
a 450MHz computer wth 256MByte memory and fast SCSI/IDE disks, this is
ridiculous, and something I try to avoid).

> ...download new mozilla build binaries?

CVS build from 29/12

> ...What sites have you tested that

Did not really matter. All links that should produce a download (local file)
_were_ broken (.tar,.zip -> "save as" .m3u, .xml -> "open with" and so on).

> Edit > Preferences > Navigator > Helper Applications 
> and clicking the "Reset" button at the bottom of the panel help?

I got the dialog window asking what to do with the file (as expected). But
nothing more (0 byte download occurs to /tmp/). Tried with Opera5 worked like a
charm.

> up your prefs.js before doing this

Too late, did it allready (but it did not help), sorry.

Seems to be one more build clobber, sorry. Too much of these (build clobbers),
maybe time to nuke the dependency support from make, as it frankly does not work!

Sorry about this "false" bug rapport, this will be my last one.

// Jarmo

Comment 4

[Boris Zbarsky [:bzbarsky]]

Jarmo, you build yourself and you build optimized?  In that case you need to 
manually delete the component registry (dist/bin/component.reg) every so often. 
 The opt build process does not touch this file and opt builds will only 
generate it once (unlike debug ones that will check its correctness every 
startup).  As a result, your component registry can get out of sync with the 
actual components installed (eg when someone adds a new interface).  Deleting 
the component.reg file is a good first step whenever functionality appears to be 
completely broken....

Comment 5

[sairuh (rarely reading bugmail)]

mass verification of WorksForMe bugs: to find all bugspam pertaining to this,
set your search string to "IfItWorksForSlappyTheSquirrelThenItWFM".

if you think this particular bug is *still* an open issue, please make sure of
the following before reopening:

a. that it's still a problem with ***recent trunk builds*** on the all
appropriate platform[s]

b. provide clear steps to reproduce (unless a good test case is already in the
bug report), making sure it pertains to the original problem (avoid morphing as
much as possible :)