| PLEX86 | ||
|
Problem with Mozilla Firefox in Linux. 1089I see you have since received good advice for finding the lock files under your $HOME-.mozilla tree. Their recommendations looked reasonable. I would have tried find $HOME-.mozilla -name '*lock*' and maybe find $HOME-.mozilla -name '.*lock*' The other recommendations may be more precise. One thing that might help is for you to understand the difference between a profile directory and an installation. The profile directory (well, directory tree, actually) is rooted at $HOME-.mozilla and contains your preferences, cache, history, lock file(s), etc. This area is unique to you and is both read and written by a browser instance you run. Problem with Mozilla Firefox in Linux. 1090 Hi Robert, I shall now post the outputs of the commands that you have suggested. Here is the first one's: 127.0.0.1:26881 Next: rm: remove... The installation area is most likely somewhere else, like maybeusr-lib orusr-local. Most likely, the installation area is shared by all users on the machine in a read-only manner. Trauma Survivors You don't have to go it alone any more Almost to a person, those who have suffered serious physical trauma, whether by car accident, work related trauma injury, shooting... Another thing to be careful of is whether the browser is running on the local diskless node or on the main server. For clarity, I would recommend stating specifically in any future postings where the broswer is running. Also, if there is any chance of confusion on your part about where you have been running the browser, I would suggest checking both machines to see whether there might be a stale browser process sitting around. If you have deleted all the lock files and a browser still refuses to run, there's a chance you might have run into a bug. -- Robert Riches (Yes, that is one of my email addresses.)
|
||||
Problem with Mozilla Firefox in Linux. 1090 Linux groups from Newsgroups The #1 Usenet Provider on the Internet
|
||||