539 bytes, application/octet-stream
Mozilla 0.9.1+ 2001060721 After I've successfully installed Java2 plugin, I quit the browser to take changes into account. Unfortunately a process hangs up and I have to kill it manually, else Mozilla tells me that the installation did not finish when next started.
i have seen this...confirming. correcting component:OJI
Installation. Over to Xiaobin.
I'm having this same problem. When I go to a page that requires Java, it will kick open the "You need a Plugin!" page. So I download the Java plugin, and it installs very happily. I close Mozilla, restart it, and I get a dialog: "The program must close to allow a previous installation attempt to complete. Please restart." If I do a ps aux, I can see /usr/local/mozilla/xpicleanup is running, and won't die. Once this happens, I can't restart Mozilla unless it is reinstalled.
sorry...took a while to 'confirm' this bug..this does really happen ..even on windows for me too.
corrected typo in summary
I am really think it is a XPInstaller issue. Over to XpInstaller comp.
Really annoying bug... I've also heard people talking about deleting one "xpicleanup.dat" file for mozilla to work again... except that java doesn't work after that.
What's happening here is that once you install Java, the installer spins off xpicleanup at shutdown of the browser if there are files that were in use and therefore could not be replaced right away. Xpicleanup is responsible for finishing the replacing process once the browser has quit. If there are still files in use by other apps (or if some were marked readonly), then xpicleanup will stick around until it's finished. Yes, there are some problems with xpicleanup that we're going to address. In the meantime, can you attach the xpicleanup.dat file to this bug? it should be in the same dir as xpicleanup and mozilla. This .dat file contains information on what files still need to be resolved (replaced/deleted/moved/etc...). It will tell us which file(s) it's having problems with.
There's my xpiclenup.dat file which I copied to my home dir right after the java plugin installed successfully and then the browser failed to restart because it was "still running" I may be able to get a couple other people's files and will attach them in due course.
from looking at the .dat file, it looks like can't delete: /home/vanbalen/tmp/xpinstall.sh do you know if that file is readonly? In any case you should be able to simple delete xpicleanup.dat and you should be good to go. As to the problem that it still tells you that you need the java plugin after you've installed, what's the url to the java plugin that you have been trying to install?
I don't have problems getting the plugin to work, I simply install it off http://home.netscape.com/plugins/jvm.html and them kill -HUP the xpicleanup process before restarting the browser and then the plugin works. I find this annoying because I shouldn't have to kill a process in order for my browser to work... if the xpicleanup process is going to take so long, there should be some kind of progress bar telling me that it's still working so I know not to try to restart the browser yet. Of course, I can kill the process without any apparent adverse consequences so maybe it shouldn't be running anyway? The problem I mentioned with the plugin not working was reported by a couple people on the debian-user mailing list who had installed 0.9.1 from debian-unstable. I think they're installing the plugin off java.sun.com though.
I think this is a dupe of another bug already dealilng with xpicleanup. I can't find the bug right now. Dave, you are correct, you shouldn't need to do anything for the browser to work. We're rethinking the way xpicleanup is implemented.
Oh, sorry about the spam but /home/vanbalen/tmp/xpinstall.sh is gone now so I guess it got deleted between the time I copied the file and when I killed the process.
It actually goes away if you wait long enough (when I tried, seemed like a minute or less).
Yes, I tried waiting also. I kept running the browser until it finally worked... still didn't get the java plugin recognized (stopped working a few days ago), but that's a different issue. See my comments from 2001-06-27 13:06 for my opinion, which applies even if the process does go away by substituting "kill a process" with "wait for a process."
*** Bug 90107 has been marked as a duplicate of this bug. ***
This appears to have been handled elsewhere... *** This bug has been marked as a duplicate of 84896 ***
SPAM: reassigning OJI bugs to new QA, pmac. (227 bugs)