303789 - Un-migrated & deleted NSv4 profiles should be removed from the list; and JS exception on deleting them

Status: RESOLVED INCOMPLETE

(Core Graveyard :: Profile: Migration, defect)

Description

[Serge Gautherie (:sgautherie)]

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

From my bug 54615 comment 8
{{
Today, I deleted a NSv4 (un-migrated) profile,
then started SM profile manager:
that profile is still listed
}}

There should be a check to remove this now-deleted profile.

Comment 1

[Serge Gautherie (:sgautherie)]

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

Workaround:
Use the UI to delete the profile from the list.

Note:
This succeeds, but we get a JS exception in the process
{{
Error: uncaught exception: [Exception... "Node was not found"  code: "8"
nsresult: "0x80530008 (NS_ERROR_DOM_NOT_FOUND_ERR)"  location:
"chrome://communicator/content/profile/profileManager.js Line: 164"]
}}

Comment 2

[Serge Gautherie (:sgautherie)]

(In reply to comment #1)
> This succeeds, but we get a JS exception in the process

This is from the 'Switch Profile...' dialog.
Actually, the profile stays in the list at first;
need to close and reopen the dialog to check that it was removed.

Comment 3

[Matthias Versen [:Matti]]

Serge: NS4.x profile migration is gone as far as I know. Can we close this report ?

Comment 4

[Benjamin Smedberg]

This bug is filed in a bugzilla component related to pre-Firefox code which no longer exists. I believe it is no longer relevant and I am therefore closing it INCOMPLETE.

If you believe that this bug is still valid and needs to be fixed, please reopen it and move it to the Toolkit:Startup and Profile System product/component.