On 26/01/12 19:25, Felix Miata wrote:
On 2012/01/26 19:07 (GMT+1100) Basil Chupin composed:
Thomas Taylor wrote:
Tonight Firefox (9.0.1) under OS 12.1 won't open. A message is displayed that states "Your Firefox profile cannot be loaded. It may be missing or inaccessible:. Sure enough, .mozilla is missing in /home/tom. Don't remember doing anything with it but may be due to two windstorms within the last few days. This happens from panel icon, favorites icon, or cli.
It's my understanding that if the profile is deleted a new one is created when firefox is run again. That doesn't happen here. It just keeps showing the error message and when OK is clicked the message box disappears but the program doesn't appear.
The thing to do in such cases is to start FF from a terminal to see what error messages appear when you try to start it.
Thought of restoring from the backup drive but that got fried during the storms when there was a large power surge. The computer was on a good surge protector (APC) but not the backup drive SIGH!)
I also tried completely removing Firefox through Yast2 and then re-installing but the problem is still the same.
Obviously I could use another web browser but I prefer to stay with FF for now.
Any suggestions or thoughts on where to look?
The power failure most probably corrupted the file system. The first thing to do is the make sure that the file system is OK: run e2fsck (assuming that you are using either ext2 or ext3 or ext 4) on the /dev/sdaX which has your system installed. Don't know how to run 'e2fsck'? Ask or look in the manual (/usr/share/doc /manual).
You create a new profile from a command line in terminal/console with 'firefox -P'.
Normally yes, but if ~/.mozilla is missing and ~ is not writable for some reason (including lack of freespace), it won't work. Normal behavior is if no profile can be found, and ~/.mozilla is writable, starting FF without any switches will automatically create a profile named "default" in ~/.mozilla/.
If your file system is corrupted naturally it is plausible that it will not find the mozilla sub-directory in /home. Ergo, do the e2fsck check first.
Another thing to try if trouble continues is creating another user, logging in using it, and seeing if FF will run there.
BC -- But when you take arms from people, then you start to upset them, you show you do not trust them because you are frightened or cagey. Niccolo Machiavelli -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org