This is a strange one-related to what one command will be used to see all 4.x profiles, allow to create new etc. Steps to reproduce: 1. Remove all previous registry data (mv .mozilla .oldmozilla) 2. Run apprunner -installer (testing migration of 4.x profile) Actual result: Profile Manager window with no profiles listed Expected result: Profile Manager window with 4.x profile noting it can be migrated Note also: If I run apprunner first, create profile, launch, test and then run apprunner -installer to check migration, the first profile created does not show in Profile Manager window. This may be a separate bug Build ftp://sweetlou/products/client/seamonkey/unix/linux_glibc/2.2/x86/1999-10-08-08- M11/
this occurs on second set of tests ie I run a set of tests to migrate a imap profile, clean the system, change 4.x to a pop profile and rerun. No profile shown for migration (could be pop first and then imap-tested both) not seeing this on windows
I sent mail to the hook about this late last night. I think its a tree problem. I'll go find out more.
Status: NEW → ASSIGNED
someone backed out troy's changed that caused this regresssion. I'm rebuilding now to make sure its fixed. I'll report back when I'm done building.
the bug that caused this bug was #15790
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED
yes, this is fixed now. troy (or someone else) broke it late last night. I imagine the later respins have the fixed.
Target Milestone: M11
verified on build 1999101108-both mozilla and commercial
Moving all Profile Manager bugs to new Profile Manager Backend component. Profile Manager component to be deleted.
You need to log in before you can comment on or make changes to this bug.