17527 - a profile created with -CreateProfile will cause a slew of assertions because <profile>/bookmarks.html does not exist.

Status: VERIFIED FIXED

(Core Graveyard :: Profile: BackEnd, defect, P3)

Description

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

linux and windows (probably mac too.)

create a profile with -CreateProfile.

on launch, you get a bunch of assertions:

Start reading in bookmarks.html
Opening file bookmarks.html failed
Error: "unable to open file" at file nsBookmarksService.cpp, line 3191
Break: at file nsBookmarksService.cpp, line 3191
Warning: "unable to load datasource 'rdf:bookmarks'" at file
nsXULContentSink.cpp, line 1725
Start reading in bookmarks.html
Opening file bookmarks.html failed
Error: "unable to open file" at file nsBookmarksService.cpp, line 3191
Break: at file nsBookmarksService.cpp, line 3191
Warning: "unable to load datasource 'rdf:bookmarks'" at file
nsXULContentSink.cpp, line 1725
Start reading in bookmarks.html
Opening file bookmarks.html failed
Error: "unable to open file" at file nsBookmarksService.cpp, line 3191
Break: at file nsBookmarksService.cpp, line 3191

Comment 1

[racham]

Accepting the bug.

Comment 2

[selmer (gone)]

Need to merge this code in with the new profile case.

Comment 3

[racham]

I have a fix coming in with the new changes.
Marking TFV to M13.

Comment 4

[racham]

-CreateProfile is fixed.

now....

case 1 : mozilla -CreateProfile foo - a profile named foo is created in the
         default profiles dir and browser is launched with that profile.

case 2 : mozilla -CreateProfile "foo c:\bar" - a profile named foo is created in
         the chosen path (c:\bar) and browser is launched with that profile.

note : quotes are mandatory to pass arguments in case 2.

true for all platforms.
Marking fixed.

Comment 5

[Grace Bush]

the last comments are true, using -CreateProfile with a profile name or with
profile name and user supplied directory (all in quotes) does as it says BUT
these profiles do not display in Profile Manager in subsequent launches.  They
do get created with the commands as verified by viewing on explorer.  They do
launch and you can set bookmarks, prefs etc but you cannot use that profile
again except with mozilla -P foo or mozilla -P "testing d:\bar".
Using the -installer, -SelectProfile, -ProfileManager arguments bring up the
Profile Manager without the newly created profiles, foo and testing
build 1999121008

Comment 6

[racham]

Grace,
I just tested this on my windows box with today's build.
Had no problems. I see the profile getting added to the list
and displayed when ran with -ProfileManager option. Will
update the report with Linux and Mac behavior soon. If there are
specific steps to reproduce this problem...please udpate the
bug.

Comment 7

[racham]

Linux is OK too....waiting for Mac to unstuff the sit file.

Comment 8

[racham]

Haven't seen this in recent builds.  If you see it again, please reopen the bug.

Comment 9

[Grace Bush]

testing with 1999121608 builds
WinNT   -CreateProfile cases 1 and 2 work
subsequent launches with -ProfileManager, -SelectProfile DO NOT DISPLAY the
profiles created above

Win95 works as noted in this bug report

Linux -CreateProfile foo brings up the CreateProfileWizard -bad
      -CreateProfile "foobar $HOME/foobar does create profile in directory and
launches, subsequent launches display the profiles

Mac - these cases not available as written, can use ProfileWizard and select
folder to accomplish the same thing however

Comment 10

[racham]

This looks like an registry update problem.
Let me look into this in detail and see what's
different on different platforms.

Comment 11

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

I just fixed #23744, which was caused because when you used -CreateProfile, we
never created prefs.js

this should help fix other CreateProfile issues.

Comment 12

[leger]

Moving all Profile Manager bugs to new Profile Manager Backend component.
Profile Manager component to be deleted.

Comment 13

[Grace Bush]

Bhuvan,
Using builds 20000120 for both Linux and Windows (95 and NT) - I am seeing the
same behavior I have reported above.  New profiles get created but are not seen
using mozilla -SelectProfile/-ProfileManager etc. They do get created and can be
viewed  BUT I used the BiggerRegToy tool and cannot see them in mozregistry.dat
which would explain why they do not show up.  They do seem to appear in registry
on Linux.

Comment 14

[racham]

Registry update request has been made after this command line option. Should 
make all problems go away. Marking fixed.

Comment 15

[Grace Bush]

build  2000-01-28-12-M14/