Closed Bug 84178 Opened 23 years ago Closed 23 years ago

Browser won't start after installing Java from XPI package.

Categories

(SeaMonkey :: Installer, defect)

x86
Linux
defect
Not set
major

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 84896

People

(Reporter: darrell, Assigned: ssu0262)

References

Details

After I install Java using the XPI package (get prompted to install java from a
java enabled web site and then follow the prompts to install) I restart Mozilla
so that it can utilize the Java package.  However, at this point I get the
following pop-up notice:

"The program must close to allow a previous installation attemp to complete. 
Please restart."

With an 'OK' button.  At which point Mozilla refuses to start up no matter what
I do.  I've checked for any other mozilla processes that might be running and
none are.  My only choice is to re-install Mozilla.

I'm using Mozilla Build ID: 3001060508 on Debian "Potato" with kernel 2.4.4 and
KDE 2.1.1.
I can also replicate this on 0.9.1 (Build ID: 2001060713).  Same OS et al.
I tried this and was successful in installing plug-in ---but I had to wait a bit
before I was able to relaunch.
I was warned about previous installation attempt needed to complete and saw the
process running.
when it finished mozilla launched and java was installed
branch build 2001060713

reporter try again - watch for process xpicleanup
After trying again and this time waiting awhile (don't know exactly how long is
long enough) I did find that mozilla would start again.

However I didn't see any processes containing 'xpi' immediately after the Java
install.
*** Bug 84916 has been marked as a duplicate of this bug. ***
*** Bug 84936 has been marked as a duplicate of this bug. ***

*** This bug has been marked as a duplicate of 84896 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
vfy
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
Component: Installer: XPI Packages → Installer
QA Contact: agracebush → general
You need to log in before you can comment on or make changes to this bug.