Closed Bug 88893 Opened 23 years ago Closed 23 years ago

unable to launch profile from profile manager

Categories

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

Product:
Core Graveyard
Component:
Profile: BackEnd
Platform:
x86
Linux
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED
Milestone:
mozilla0.9.3

People

(Reporter: bugzilla, Assigned: ccarlen)

References

Details

(Keywords: platform-parity, regression, smoketest, Whiteboard: [PDT+]) 

found using 2001.07.02.04-branch comm bits on linux. not a problem on winnt or
mac branch comm bits.

don't know if this is an issue [yet] on mozilla or trunk builds.

1. launch netscape, ie, ./netscape
2. when profile manager comes up, select a profile then click the "start
netscape 6" button.

result: profile mgr dialog goes away, but the app doesn't startup. just get the
following in the console:

ProfileManager : StartApprunner
profileName passed in: <profile-name>

workaround: using ./netscape -P <profile-name>
Keywords: nsdogfood, regression
this occurs using a new and existing profile [both were non-migrated].
Keywords: pp
workforme on Linux; redhat 6.2 using a new or existing profile (branch build:
2001-07-02-04-0.9.2)
Just want to add more info about this bug:
Linux; redhat 6.2 (branch build: 2001-07-02-04-0.9.2)

First time launching, there's no problem if I followed the same procedure
that Sarah mentioned in this bug report.

Part #1
1. launch netscape, ie, ./netscape
2. when profile manager comes up, select a profile either the existing
profile OR creating a new profile then click the "start
netscape 6" button.
3. profile mgr dialog goes away, the the app startup (work fine)

Part #2:
1. launch from profile manager, ie, ./netscape -profilemanager
2. when profile manager comes up, select a profile either the existing
profile OR creating a new profile then click the "start
netscape 6" button.

result: profile mgr dialog goes away, but the app doesn't startup. just get the
following in the console:

ProfileManager : StartApprunner
profileName passed in: <profile-name>

result: profile mgr dialog goes away, but the app doesn't startup. just get the
following in the console:

ProfileManager : StartApprunner
profileName passed in: <profile-name>

------------------------
Part #3:

I tried to follow step part #1 again, it does not launch anymore no matter
using existing or new profiles.
nav triage team:

Marking nsbeta1+, nsBranch, p1, and mozilla0.9.3. Multiple profiles should work
Keywords: nsbeta1+, nsBranch
Priority: -- → P1
Target Milestone: --- → mozilla0.9.3
more strangeness:
I tried ./netscape -profilemanager with my earlier installation after seeing
K'Trina's hang  and could reproduce this problem.
the farthest I get in app is
ProfileManager : StartApprunner
profileName passed in: gbush
 and hang

I installed again (after removing .mozilla) and cannot reproduce.
I have been successful in migrating, creating 3 new    profiles and getting
through activation. now the console says

ProfileManager : StartApprunner
profileName passed in: gbush
 I am inside the initialize
 Hey : You are in QFA Startup 
(QFA)Talkback loaded Ok.

this is also occurring with my mozilla debug build [21:22 pull tonight].
forgot to mention in my last comment: the mozilla debug build i have is a trunk
build.
moving over here from bug 89060

seeing on respin for linux 2001-07-03-11-trunk
Severity: major → blocker
Keywords: smoketest
I don't know if this should be a seperate bug, but in win98, on an unmigrated 
profile. If I double click on a profile it starts the migration then returns me 
to the profile wizard, showing that said profile has not been migrated. And will 
retry migration if I double click again. I have to click on the start mozilla 
button. I would think that double clicking the name and the start mozilla button 
should do the same thing, it used to.
Doing a Linux build now to look at this.

> I don't know if this should be a seperate bug

Yes, it's bug 87150 - fixed on trunk, needs to go on branch.
 
I can't reproduce this using 2001-07-03-04-0.9.2 commercial linux build on
Redhat 7.0.

Also, 2001-07-03-11-trunk commercial linux build seg faults very quickly after
launch (before profile manager dialog comes up) on the same system.

Sairuh and Tracy, what version of linux are you running?
pchen

...the bug is on trunk builds only.  The branch is fine.
Umm, ok, I was testing branch bits because Patty Mac mentioned:
> Just want to add more info about this bug:
> Linux; redhat 6.2 (branch build: 2001-07-02-04-0.9.2)
and I just happened to download the 2001-07-03-04-0.9.2 branch build today.

Well, unfortunately, like I mentioned before, 2001-07-03-11-trunk build seg
faults on my linux machine.
The text is displayed after the profile manager front end is dismissed. This is
not a FE bug. 

-> profile manager back end.
Assignee: ben → ccarlen
Component: Profile Manager FrontEnd → Profile Manager BackEnd
pchen, i'm running RH 6.2.
I'm looking at it.
Status: NEW → ASSIGNED
My build is still going (slowly). If somebody has a fresh trunk build, can you
stick a breakpoint here:
http://lxr.mozilla.org/mozilla/source/xpfe/bootstrap/nsAppRunner.cpp#1139
and see if we make it past that point. Sounds like in Paul's case it's not even
getting *to* that point.
sairuh, this was originally filed for the branch build. Is this still happening 
for the latest branch build? For trunk, was it okay on 7/2 build and started 
from today's build?

This is still happening to me using today's branch build 2001070306
I'm going to mark this PDT+ as this bug sounds really bad and is happening to
some folks on the branch builds (as well as trunk).  pchen - ktrina has this
problem; do you want to take a look on her system?
Whiteboard: [PDT+]
Is what was seen in today's trunk respin bug 89099?
The reports vary greatly.
Based on Tracy's comment,
> ...the bug is on trunk builds only.  The branch is fine.
I just pulled an built mozilla linux trunk and was able to migrate a profile,
create them, and use existing ones.

Can we get some consensus on what's going on with builds done *after* 11:00 today?


The consensus is to wait for some kind of signal from engineers or the sheriff to 
kick off another build once we think we have a fix.
This just happened about 15mn ago when Leaf came to see me.
I therefore kicked off another Linux build attenpting to force some dependencies 
to be picked.

Mozilla is already done and available here:
ftp://ftp.mozilla.org/pub/mozilla/nightly/2001-07-03-16-trunk/

Commercial should follow soon.
If someone can verify that the fix is in, I think I can then open the tree

I'm still seeing bug 89099 (dependency problem, AFAICT) in the mozilla respin.
ok, I suggest to kick off a clean build on Linux (no pull ; clobber) and reopen 
the tree for general checkin.
Conrad, I rely on your level of confidence that the problem is already gone.

In any case, this bug should be marked fixed or the severity lowered before I 
proceed.

Lowering severity to critical. WFM on mozilla trunk. Not marking fixed because
the reports vary so greatly and, until we know the deal on each of the 4 builds,
this might not be over.
Severity: blocker → critical
fwiw:

the cmd-line workaround i had orginally reported here [using ./netscape -P
<profile-name>] doesn't work using the 2001.07.03.16 *trunk* bits. however, the
cmd-line workaround does work using the 2001.07.03.04 *branch* bits. interesting...
Severity: critical → blocker
eek, collision clobbered ccarlen's change...
Severity: blocker → critical
tested using 2001.07.03.18-trunk bits, both mozilla and commercial builds:

* was able to launch profile from the profile manager
* was able to launch profile via the -P cmd-line option
I also was able to launch 2001.07.03.18-trunk commercial build on Redhat 7.1 Ja.
 I created a new profile and was able to launch the new profile.


Based on latest reports on 2001.07.03.18-trunk bits, marking fixed.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Has anybody tried this bug out without having any profiles in there directory? 
Try deleting your .mozilla directory for each case and then start up netscape with 

./netscape -ProfileManager (fill out profile info and finish)
or 
./netscape -ProfileWizard (fill out profile info and finish)
or 
./netscape 

I get a hang for all cases using todays linux branch builds (2001070510).  July
02 branch bits are the only set of bits that seem to work with multiple profiles
and no profiles. 
For all cases I Installed with the Full Install option (to get the Java Plugin
installed).  The cases I described will work if you choose to install the builds
with the recommended option, or choose not to install the Java plugin when doing
a custom install.  The hanging might be related to bug 89488.
I am able to launch using profile manager.
did usual testing - with RECOMMENDED build 
remove .mozilla
migrate 4.x profile from installer
run ./netscape -profilemanager
create many profiles (rename/delete etc)
run ./netscape  -profilemanager or ./netscape to launch and test activation

all done without failures.

installed FULL setup type and after removing.mozilla etc, on first launch from
installer I hang.  2nd launch is successful with migrated  profile. Not able to
run using ./netscape -profilemanager (this bug) but obviously dependent on Java
install 

using recommended build, I downloaded and installed jre.xpi, restarted N6  and
am unable to proceed through profile manager

Agree with rvelasco that  this might be related to bug 89488
addng dependency
Depends on: 89488
hrm...i'm seeing this bug again --as i had originally reported-- using today's
2001.07.09.04-branch commercial bits. :(

* i cannot launch from the Profile Manager [used ./netscape, and got the prof
mgr since i've got multiple profiles]
* but i can launch from the cmd-line [using -P option]

is anyone else seeing this using today's bits? fwiw, i used the stubs installer,
with a custom installation [i installed everything *except* Java].
I'm seeing this using today's 2001.07.09.04-branch commercial bits as well. 
Can't launch via Profile Manager (used ./netscape -profilemanager with one 
profile) on RH Linux 7.

This bug is getting too many comments :-)
gbush or ktrina or sairuh - let's open a new bug as it applies to the branch and
leave this one closed for trunk builds.
okay, filed bug 90058.
verify for  trunk
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.