54615 - when we fail to migrate, we do it silently

Status: RESOLVED FIXED

(SeaMonkey :: Startup & Profiles, defect, P3)

Description

[(not reading, please use [e-mail] instead)]

right now, esther has a 4.x profile that is failing to migrate.  we are still
working on why it is failing.

but one thing to note is that when we fail, we just silently fail.

we should at least pop up an alert dialog telling the user they failed.

from her console:

stdout directed to dynamic console
stderr directed to dynamic console
has multiple monitor apis is 1
Move window by 520,404.5
New location for profile registry and user profile directories is -> C:\WINDOWS\
APPLICATION DATA\Mozilla
Inside Migrate Profile routine.
start of pref migration
JavaScript error:
 line 0: uncaught exception: [Exception... "Component returned failure code: 0x8
0520008 [nsIProfile.migrateProfile]"  nsresult: "0x80520008 (<unknown>)"  locati
on: "JS frame :: chrome://communicator/content/profile/profileSelection.js :: on
Start :: line 178"  data: no]

we should wrap the call to profile.migrateProfile() in profileSelection.js with
a try and catch, and on catch pop up an alert with the exception.

at least we'd get some bug reports.

tomorrow I'll work with esther to reproduce and debug this failure.

Comment 1

[racham]

-> Conrad.

Comment 2

[Conrad Carlen (not reading bugmail)]

Agreed that we need this. It's pretty easy to do.

Comment 3

[Conrad Carlen (not reading bugmail)]

-> 0.9.1

Comment 4

[Conrad Carlen (not reading bugmail)]

-> front end

Comment 5

[Blake Ross]

Profile Manager FE bugs --> me

Comment 6

[Blake Ross]

reassigning to default owner.

Comment 7

[tom wible]

after installing mac os9.2.2 (up from 9.04) mozilla stopped working: old profile
not recognized, new profile ignored: manage profiles shows nothing after
creating a new one:-(

clue: set profile folder window, while allowing browsing, & creating a new
profile in the selected dir, doesn't show the dir.name in the wizard window...

Comment 8

[Serge Gautherie (:sgautherie)]

(In reply to comment #7)
> after installing mac os9.2.2 (up from 9.04) mozilla stopped working: old profile

This is probably not this bug...

***** *****

[Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8b4) Gecko/20050806 SeaMonkey/1.0a]
(nightly) (W98SE)

Today, I deleted a NSv4 (un-migrated) profile,
then started SM with my usual profile,
then went to 'Tools > Switch Profile...':
that profile is still listed [that would be another bug...]
and when I tried to migrate it, it silently failed, with
{{
Error: [Exception... "Component returned failure code: 0x80520012
(NS_ERROR_FILE_NOT_FOUND) [nsIProfileInternal.getProfileDir]"  nsresult:
"0x80520012 (NS_ERROR_FILE_NOT_FOUND)"  location: "JS frame ::
chrome://communicator/content/profile/profileSelection.js :: onStart :: line
208"  data: no]
Source File: chrome://communicator/content/profile/profileSelection.js
Line: 208
}}

The error seems correct, but we still lack to let user know.

Comment 9

[Serge Gautherie (:sgautherie)]

(In reply to comment #8)
> [Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8b4) Gecko/20050806 SeaMonkey/1.0a]
> (nightly) (W98SE)
> 
> Today, I deleted a NSv4 (un-migrated) profile,
> then started SM with my usual profile,
> then went to 'Tools > Switch Profile...':
> that profile is still listed [that would be another bug...]

I filed bug 303789.


Trying to rename: (silly, but the UI makes it possible)
{{
Error: uncaught exception: [Exception... "Component returned failure code:
0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIProfileInternal.getProfileDir]" 
nsresult: "0x80520012 (NS_ERROR_FILE_NOT_FOUND)"  location: "JS frame ::
chrome://communicator/content/profile/profileManager.js :: RenameProfile :: line
83"  data: no]
}}

Comment 10

[Philip Chee]

Bug 379068 removed support for migrating NS4 profiles and Bug 384083 prevents the existence of NS4 profiles from interfering with profile migration and SuiteRunner isn't supported on Win98 anyway so marking this FIXED.