Closed
Bug 16119
Opened 25 years ago
Closed 25 years ago
[DOGFOOD][REGRESSION]unable to create profile in default folder
Categories
(Core Graveyard :: Profile: BackEnd, defect, P1)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
M11
People
(Reporter: agracebush, Assigned: racham)
References
Details
(Whiteboard: [PDT+])
Steps to reproduce: 1. remove mozregistry/documents folder 2. click on apprunner icon or Apprunner Installer 3. in CreateProfileWizard, enter data, press finish or select profile to migrate, press start Actual results: message displayed 'unable to create profile' Expected results: profile created mac build 1999101114-mozilla build
Updated•25 years ago
|
Target Milestone: M11
Comment 1•25 years ago
|
||
I was able to create a new profile after trashing ``Mozilla Registry'' and running apprunner. I will try to verify successful startup on another mac as well.
Reporter | ||
Comment 2•25 years ago
|
||
I did that again-still no profile. I get a nice message box telling me 'failed to create a profile'. I don't get any message when trying to migrate. I can exit gracefully though.
Comment 3•25 years ago
|
||
I've tried this on a second mac, as well as creating new profiles on a system with the ``Mozilla Installer'' icon. We're reopening the tree, and hopefully we can track down this inconsistency before tomorrow.
Updated•25 years ago
|
Assignee: selmer → racham
Assignee: racham → waterson
Summary: [PP]CreateProfileWizard will not create profile, ProfileMigrator will not migrate → [PP]unable to create browsing profile component
unable to create profile comment is coming from http://lxr.mozilla.org/seamonkey/source/rdf/brprof/server/nsBrowsingProfileReade r.cpp#174. The profile it refers there is browsing profile and the assertion is coming from the failure to create that object. Reassigning to Chris Waterson. Grace, However, I stil have to check my Mac build (going on) for profile manager stuff. Please open a new bug if you can't create a profile. Changing the summary.
Reporter | ||
Comment 5•25 years ago
|
||
Bhuvan, The message is coming from an alert window that says 'failed to create a profile' which I can see in /chrome/profile/content/default/createProfileWizard.js in the function processCreateProfileData()
Reporter | ||
Comment 6•25 years ago
|
||
Bhuvan, The message is coming from an alert window that says 'failed to create a profile' which I can see in /chrome/profile/content/default/createProfileWizard.js in the function processCreateProfileData()
Reporter | ||
Comment 7•25 years ago
|
||
Mac mozilla build 1999101208- I am unable to create a profile or migrate a profile If I choose 'new', an empty documents folder gets created, the mozregistry is created and an alert window comes up saying 'failed to create profile' If I choose a profile to migrate and press start, nothing happens If I go to an old build and create or migrate a profile, I am able to run seamonkey with that profile rename and delete buttons work with the old profiles
Reporter | ||
Updated•25 years ago
|
Priority: P3 → P1
Reporter | ||
Updated•25 years ago
|
Severity: blocker → critical
Reporter | ||
Comment 8•25 years ago
|
||
update with 1999101308 builds New icons/commands are shown Mozilla Profile Manager and Mozilla Profile Wizard Either will allow creation of profile *IF* you choose a folder other than default Rename,delete work Migrate (from Mozilla Installer) does not work, separate bug logged from this (16305) Changing from blocker to critical
Reassigning this bug back to myself. Sorry chris. I was misled by the error message.
Assignee | ||
Comment 10•25 years ago
|
||
Grace, Looks like you are not getting the alert any more. We should use thig bug to figure why default folder is not accepted.
Reporter | ||
Updated•25 years ago
|
Summary: [PP]unable to create browsing profile component → [PP]unable to create profile in default folder
Updated•25 years ago
|
Summary: [PP]unable to create profile in default folder → [PP][DOGFOOD]unable to create profile in default folder
Assignee | ||
Comment 14•25 years ago
|
||
I could not even launch apprunner with my previuos builds. A buils is in progress now in Mac. I will post the status.
Reporter | ||
Comment 15•25 years ago
|
||
This is not working for me as late as yesterday. I still see the same behavior, if I try to use the default folder, the alert tells me 'failed to create a profile'. The documents folder is created but empty.
Assignee | ||
Comment 17•25 years ago
|
||
This works on my daily mac build. So, is this happening only with commercial build ? Adding leaf to the cc list. Are we pulling the correct version of CreateProfileWizard.js for the commercial build ?
Comment 18•25 years ago
|
||
The commercial build process currently copies everything in mozilla/dist... so it's unlikely it's a js file. It's *possible* that there are conflicts between the commercail js/xul file usages and the imported mozilla js/xul files.
Reporter | ||
Updated•25 years ago
|
OS: Mac System 8.5 → other
Hardware: Macintosh → All
Reporter | ||
Comment 20•25 years ago
|
||
Changing platform to all Bug 17633 was found on Windows-1991030 build. I was able to reproduce on Win 19991101 build. Found also that migration uses the default folder but I had to use custom folder for a new profile
Assignee | ||
Comment 21•25 years ago
|
||
I haven't noticed tihs with Friday's Mac commercial build. Grace will cross check this with today's build. Now as this seems to be happening on Windows CVS build too, If I can reproduce this, we will get a clue as to what's happening..?
Reporter | ||
Comment 22•25 years ago
|
||
Using the following commercial builds, I was unable to create a profile in the default folder on any platform. Linux - ftp://sweetlou.mcom.com/products/client/seamonkey/unix/linux/2.2/x86/1999-11-01- 08-M11/netscape-i686-pc-linux-gnu.tar.gz Mac OS - ftp://sweetlou.mcom.com/products/client/seamonkey/macos/8.x/ppc/1999-11-01-08-M1 1/netscape5-mac-M11.sea.bin Win32 ftp://sweetlou.mcom.com/products/client/seamonkey/windows/32bit/x86/1999-11-01-0 9-M11/seamonkey32e.exe
Summary: [PP][DOGFOOD]unable to create profile in default folder → [DOGFOOD][REGRESSION]unable to create profile in default folder
Updated•25 years ago
|
Assignee: racham → sspitzer
Status: ASSIGNED → NEW
Updated•25 years ago
|
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Reporter | ||
Updated•25 years ago
|
Status: RESOLVED → REOPENED
OS: other → Mac System 8.5
Hardware: All → Macintosh
Reporter | ||
Comment 26•25 years ago
|
||
I am able to create a profile in default folder on windows but still get the 'failed to create a profile' error message on the Mac. Will change platform to Mac as before.
Reporter | ||
Updated•25 years ago
|
Resolution: FIXED → ---
Comment 27•25 years ago
|
||
It is misleading to open/close/reopen/close/reopen any bug, the history gets skewed. We have fixed the XP problem here, I suggest closing this and opening a new bug. For instance, you now pick up the PDT+ status, do you want that? you're dragging a lot of jumbled up bug history around by reopening.
Updated•25 years ago
|
Assignee: sspitzer → racham
Status: REOPENED → NEW
Comment 28•25 years ago
|
||
giving profile bugs back to racham. racham, if you need help, let me know.
Status: NEW → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → WORKSFORME
Assignee | ||
Comment 29•25 years ago
|
||
I created a new profile on 3 different machines (using commercial build) without any problems. Marking this worksforme. Grace, will you please check the behavior on other Mac machines (of other QA engineers you know)? If you find this behavior, please file a new bug so that the problem has a new track that is related just to Mac.
Reporter | ||
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
Reporter | ||
Comment 30•25 years ago
|
||
I tested on another machine and was able to create the profile, so I will mark verified. I will investigate my own machine further as the problem still exists with todays build.
Comment 31•25 years ago
|
||
Moving all Profile Manager bugs to new Profile Manager Backend component. Profile Manager component to be deleted.
Updated•9 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•