Closed Bug 211860 Opened 22 years ago Closed 22 years ago

Profile Manager does not see/use/remember existing profiles that are not the default / only uses default or default user profile

Categories

(Firefox :: General, defect)

x86
All
defect
Not set
blocker

Tracking

()

VERIFIED FIXED

People

(Reporter: noririty, Assigned: ccarlen)

References

Details

You cannot select existing profile even use with -p switch. Because 'Profile Manager' doesn't come up.
*** Bug 211911 has been marked as a duplicate of this bug. ***
Slightly incorrect. Here at my box, the profile manager comes up but it seems to be in profile-creation-only mode, since the first dialog that pops up is the 'Create Profile'-dialog.
Same problem here. When using Mozilla Firebird (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5a) Gecko/20030706 Mozilla Firebird/0.6 StumbleUpon/1.73) night build for the first time I found my old profile no longer loaded so I used -p to make a new profile and point it to my Profile dir D:\Documents and Settings\Paul\Application Data\Mozilla\Profiles\Paul\ which loaded my setting (bookmarks, teams etc). Next time I ran Mozilla Firebird it did not load up my profile again (only loaded default) I also noticed it uses the directory D:\Documents and Settings\Paul\Application Data\Phoenix\Profiles. Next I made a new Profile but it still did not save the new settings. In the end I copied all the files from my backed up profile into D:\Documents and Settings\Paul\Application Data\Phoenix\Profiles\default\0l4668st.slt which worked around this bug. (p.s. this I my first time using Bugzilla so sorry if I posted in the wrong place) Paul
This sounds like the flip side of bug #205820, and I suggest that the 2 should be considered together.
> so I used -p to make a new profile -p is not meant to create a profile or bring up any dialog. It just selects an existing profile. See: http://lxr.mozilla.org/seamonkey/source/profile/src/nsProfile.cpp#730
Assignee: bryner → ccarlen
Component: build-config → General
*** Bug 211983 has been marked as a duplicate of this bug. ***
Just starting MozillaFirebird without the -p switch just starts it with the default profile, regardless if that profile exist or not. It doesn't seem to care at all about the actual profiles listed in registry.dat.
Hardware: PC → All
a major issue here is that firebird is not "remembering" created profiles. I've been able to use my existing, "old", profile by launching with the profile manager and creating a "new" one with the same name. each time the profile manager comes up with NO profiles listed, not even "default user". I suppose a work-arround would be to copy my bookmarks, cookies, password file tec. into the default user directory & update prefs with the new xx.s & xx.w file names. I haven't tried that yet as I'm hoping this will be resolved soon.
I have found this problem with the nightly builds from 7/8 to date. My profiles are not recognized even after I create them. The -p XXX switch loads the create profile window not the designated profile. I have this set up for several users to start FB with their own preferences on one PC. If I download the Firebird 0.6 with installer, the problem does not occur. http://downloads.mozdev.org/seb/MozillaFirebird-0.6-setup.exe What is the difference in the nightly builds and the full product in this intall file? Thank you JOe
Does this have anythign to do with bug 212132, Allow disabling of profile locking. http://bugzilla.mozilla.org/show_bug.cgi?id=212132 The checkin's for that bug seem to have happened the day this broke, and the description is pretty close. Perhaps the default got set to Disable profiles, and simply needs to be turned back on.
I have noticed that after the 0702 windows build, the profile manger will not read or create profiles. The 0702 windows build was the last build where you can created new and even see the profiles. Seems like it does not look or read the registry.dat file. The last build I tried was windows 0711 and it did not work. I have used -p and -profilemanger...
I hit this bug even though I only have one profile. It's called Jesse2 rather than Default or Default User.
Carlen: -> Firebird 0.7?
I think I've got past this! Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5a) Gecko/20030712 Mozilla Firebird/0.6 Erased _completely_ <AppData>\Phoenix directory tree; Run MozillaFirebird -profilemanager The select profile dialog comes up with no profiles shown (no default either). Select CreateProfile. ChooseFolder: select the parent of the original profile, type the name of the desired profile directory. (Select DontAsk) Select StartMozillaFirebird. And I'm up with my prefs, etc from before.
Y'OTTA - Change the Summary. Profile Manager does 'come up'. It's just blind to existing profiles. And my previous comment was premature. Only works the first time! Next launch I'm back with dumb default settings for everything. I'd need to wipe out the Phoenix AppData every time. When I wrote a clone of this, I had it set as "blocker" - and was promptly slapped on the wrist. But *&()(&(* ! It blocks me out of Firebird until it's fixed! I'm back to MozillaTrunk for now.
-> Blocker since we can't complete SmokeTests (2. Profile Manager). http://www.mozilla.org/quality/smoketests/
Severity: major → blocker
apeiron in #firebird and I can't reproduce this on Unix flavoured boxes and 20030708 (or later) builds. Throwing back to PC/some variety of Windows
OS: All → Windows 2000
Hardware: All → PC
Updated summary to, I think, more accurately state the issue and make it a little easier to find this bug.
Summary: Cannot select profile because Profile Manager doesn't come up → Profile Manager does not see/use/remember existing profiles that are not the default / only uses default or default user profile
Is Firebird a static build on Windows?
Depends on: 211645
OS: Windows 2000 → All
Hardware: PC → All
OS: All → Windows 2000
Hardware: All → PC
windows 98SE as well
Same problem on Win XP
bryner says we do build a static build. I just checked in a fix to my makefile changes. It may have been the cause of this bustage. Checking in Makefile.in; /cvsroot/mozilla/xpcom/obsolete/component/Makefile.in,v <-- Makefile.in new revision: 1.7; previous revision: 1.6 done Could someone verify that this indeed fixes the problem?
Doug, I can't verify it with the current win32 build from 20030714. The zip-file date is 20:12 of that day, but I don't know, when the code got checked out of cvs.
the build with the 20:12 timestamp is in the folder 2003-07-14-15-trunk, so the code came from CVS 15:00 PST (could be up to 15:59) - a couple of hours before the checkin. (ftp.m.o's timezone is 3 hours later than the Mozilla tools, so that 20:12 would be 17:12 PST, the time the build finished...)
second hand information, but according to http://forums.mozillazine.org/viewtopic.php?p=116514#116514 , this is fixed. thanks Doug.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Yes, it works for me! Using Aebrahim's build. Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5a) Gecko/20030715 Mozilla Firebird/0.6
This bug does not seem to be fixed on the 0714 win32 build. I deleted firebird and the phoenix profiles directory completely, and then created two new profiles. Then I shutdown. When starting with -ProfileManager, it's blank. No profiles are listed. So, same as always. I'm on WinXP
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Jason, as comment 25 noted, the checkin happened after the 0714 win32 build was created. Try Aebrahim's 0715 build.
Jason - that's to be expected. The win32 build from the 14th is before the fix was checked in. If you get Aebrahim's 07/15 build, or wait for the Mozilla 0715 build to appear, you should find it works. marking fixed again.
Status: REOPENED → RESOLVED
Closed: 22 years ago22 years ago
Resolution: --- → FIXED
Can't find the 7/15 win32 build anywhere. Can someone supply a URL?
The mozilla firebird win32 builds seem to have got stuck - the 20030715 build never appeared. Other people have made builds from the source code though - for example - http://forums.mozillazine.org/viewtopic.php?t=15862
*** Bug 213184 has been marked as a duplicate of this bug. ***
V. 20030720 PC/WinXP, showed up on mozilla.org this morning (yay).
Status: RESOLVED → VERIFIED
On what grounds was this marked FIXED? And why Windows-only? This problem has been around (and still is around) on Linux for eons. I just moved my .phoenix dir and ran FB to create a new one, then ran another instance of FB to create a second profile. Shut both instances down, and started FB again. It goes to the default without running up the profile manager. I started a second instance and the profile manager pops up with only the default profile showing despite the fact I had just created a second. Sorry guys - this bug still exists on my 20030722 build. -->Reopening OS --> All
Status: VERIFIED → REOPENED
OS: Windows 2000 → All
Resolution: FIXED → ---
Bug still exists without fix in 7/23 build on XP, definatly not fixed.
David, this bug is a specific breakage against Win32 which appears to have been a regression. If this has been around "for eons" on Linux, that is a separate issue that needs a separate bug. Stephen, make sure you do a clean install (delete contents of the directory before unzipping) and try again (run MozillaFirebird -profilemanager). The build structure changed slightly, when this came out I needed to do that to get this working. Also, there are two 07-23 builds, if you are using the 0.6.1 candidate build this won't be fixed in that build because of where its built from. Restoring previous status pending real confirmation with real build ID information. This is still WFM on current nightly and for anyone I asked.
Status: REOPENED → RESOLVED
Closed: 22 years ago22 years ago
OS: All → Windows 2000
QA Contact: asa → mconnor
Resolution: --- → FIXED
Fine. If you ask me they're exactly the same bug which has only recently appeared in Win32 builds but which has been around in Linux builds for a while longer ("eons" being months :) ). At any rate, bug 213704 has been filed for this issue in Linux.
OS: Windows 2000 → All
*** Bug 213704 has been marked as a duplicate of this bug. ***
Verified
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.