154486 - (branch) Can't download anything, no D/L manager

Status: VERIFIED WORKSFORME

(SeaMonkey :: Download & File Handling, defect)

Description

[Mike Pinkerton (not reading bugmail)]

branch 1.0 bits from 6/26/02, OSX

try to d/l anything, like off the mozilla homepage. nothing happens. try to open
the D/l manager from the Tools menu. nothing happens.

critical regression

Comment 1

[rxsherm]

Added me to CC and added blockage link to bug# 149510

Comment 2

[Blake Ross]

Um, not being able to download things and not being able to open download
manager are two different things.  Since the progress dialog comes up by default
on mac.  Is there a js error trying to open download manager?

Comment 3

[sairuh (rarely reading bugmail)]

pink, what happens if you try this with a new profile?

fwiw, using today's branch build (wasn't a problem w/y'day's branch) i
encountered a problem accessing the dl mgr window from the Tools menu --it just
wouldn't appear. for kicks i quit the app...then the crash reporter appeared (in
nsDownloadManager::_dt(void)).

however, i had seen this using an existing profile (1-2 wk's old), but was
unable to repro with a new profile.

Comment 4

[sairuh (rarely reading bugmail)]

i tried saving with that older, existing profile, and i'm also unable to save
--i get as far as the file picker, click Save, but no progress dialog, nothing
saved to my machine.

i'll attach the crash report in a bit (though not sure how relevant it'd be to
this bug).

Comment 5

[sairuh (rarely reading bugmail)]

Attachment: crash report

after attempting to save a file, then accessing the download manager from the
tools menu (both which failed), i quit the application. this resulted in a
crash. pink, do you see this as well?

Comment 6

[sairuh (rarely reading bugmail)]

console output when attempting to open dl mgr window from tools menu:

Error: uncaught exception: [Exception... "Component returned failure code:
0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE) [nsIJSCID.getService]"  nsresult:
"0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE)"  location: "JS frame ::
chrome://communicator/content/tasksOverlay.js :: toDownloadManager :: line 47" 
data: no]

Comment 7

[sairuh (rarely reading bugmail)]

hrm, the crash might be unrelated (or just erratic), coz the last time i tried
to quit (after failing to open the dl mgr window), it didn't crash.

Comment 8

[Blake Ross]

Okay, so for some reason, for existing profiles only, suddenly the download
manager service can no longer be obtained?!

If it's related, the problem about the progress dlg not showing up would also
mean that an nsIDownload instance can't be created.  nsIDownload is totally
different from nsIDownloadManager and I'm not sure if these bugs are related.
But we'll see.

Comment 9

[Blake Ross]

I looked at this on Asa's machine. Deleting the component registry made this
work fine.  Nothing was checked into the branch yesterday that would suddenly
cause the download manager service to not get registered for existing profiles.
 pink said jj/the build team were doing something with component registry, so
passing off to them...

Comment 10

[Blake Ross]

Also, this is technically not a smoketest blocker since it doesn't occur with
new profiles.

Comment 11

[J.J. Enser]

sounds like a dup of bug 154463 and bugscape 17121. Different consequence, but
same cause: an 'invalid' Component Registry included with yesterday's OSX branch
build.

Release packaging automation has been fixed yesterday to stop packaging that
file with Branch builds. If this works with today's OSX branch build, then we
know it's the comp reg for sure. Please verify and update accordingly.

Comment 12

[sairuh (rarely reading bugmail)]

with the [formerly] new profile i had created y'day, i'm now encountering this
bug... will dbl-check this using today's bits...

Comment 13

[sairuh (rarely reading bugmail)]

yep, this wfm using 2002.06.27.05 branch comm bits on 10.1.5 and my older profile.

Comment 14

[Simon Fraser [no longer active]]

I wonder if we have 2 libs that have the same fragment name?

Comment 15

[J.J. Enser]

There was a problem with the 6/26 bits.
Can someone verify that this bug is gone with 6/28 bits?

Comment 16

[sairuh (rarely reading bugmail)]

mass-verifying WorksForMe bugs.

reopen only if this bug is still a problem with a *recent trunk build*.

mail search string for bugspam: AchilleaMillefolium