Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Αυτός ο ιστότοπος θα έχει περιορισμένη λειτουργικότητα, όσο εκτελούμε εργασίες συντήρησης για να βελτιώσουμε την εμπειρία σας. Αν ένα άρθρο δεν επιλύει το ζήτημά σας και θέλετε να κάνετε μια ερώτηση, η κοινότητα υποστήριξής μας είναι έτοιμη να σας βοηθήσει στο Twitter (@FirefoxSupport) και στο Reddit (/r/firefox).

Αναζήτηση στην υποστήριξη

Προσοχή στις απάτες! Δεν θα σας ζητήσουμε ποτέ να καλέσετε ή να στείλετε μήνυμα σε κάποιον αριθμό τηλεφώνου ή να μοιραστείτε προσωπικά δεδομένα. Αναφέρετε τυχόν ύποπτη δραστηριότητα μέσω της επιλογής «Αναφορά κατάχρησης».

Μάθετε περισσότερα

Firefox cannot access its profile directory on Retina iMac OS 10.11.1

  • 5 απαντήσεις
  • 2 έχουν αυτό το πρόβλημα
  • 6 προβολές
  • Τελευταία απάντηση από jddjdd

more options

Clean install of Firefox 42.0 gives "Your Firefox profile cannot be loaded. It may be missing or inaccessible" error. This is on a new Retina iMac running OS 10.11.1 (15B42). I cannot run the Profile Manager except as root (using sudo). If I run as root everything is fine, I can make a new profile and store it somewhere else, give it any permissions I like. But I cannot then run Firefox as my normal administrative user, I get the same error. It cannot get access to the profile.

Clean install of Firefox 42.0 gives "Your Firefox profile cannot be loaded. It may be missing or inaccessible" error. This is on a new Retina iMac running OS 10.11.1 (15B42). I cannot run the Profile Manager except as root (using sudo). If I run as root everything is fine, I can make a new profile and store it somewhere else, give it any permissions I like. But I cannot then run Firefox as my normal administrative user, I get the same error. It cannot get access to the profile.

Όλες οι απαντήσεις (5)

more options
more options

Locate the profiles.ini file and delete this file or use the Profile Manager to create a new profile.

See:


This issue can be caused by a problem with the profiles.ini file or with the permissions (owner) of involved folders with the main profile location or the location used for the cache.

You can use one of these to make Firefox create a new default profile or recover an existing profile:

  • Delete the profiles.ini file to make Firefox create a new (default) profile
  • Use the Profile Manager to create a new profile
    If you still have an existing profile then click "Choose Folder" in the Profile Manager and browse to the location of a lost profile to recover this profile
    https://support.mozilla.org/kb/Managing+profiles

You should find the profiles.ini file in this hidden location:

  • Windows: %AppData%\Mozilla\Firefox\
    *C:\Users\<user>\AppData\Roaming\Mozilla\Firefox\
  • Mac: ~/Library/Application Support/Firefox/
  • Linux: ~/.mozilla/firefox/

If clearing the profiles.ini file isn't working then also check the location of the cache files.

  • Windows: *C:\Users\<user>\AppData\Local\Mozilla\Firefox\Profiles\<profile>\
  • Mac: ~/Library/Caches/Firefox/Profiles/
  • Linux:~/.cache/mozilla/firefox/

You can also try to rename/delete the MozillaFirefox folder in both above mentioned locations (main, cache).


more options

Thanks very much, but from my initial post you can see that I have in fact created new profiles with the profile manager. The problem is, that (for me) the profile manager will run only with root privileges, and any profile it creates then seems to be completely inaccessible to Firefox run as a normal user.

This may be a bigger problem I'm having with permissions in El Capitan, a few other applications that should run fine are also unable to access the filesystem normally. If nobody else has seen this behavior it may be time to re-install OS X.

more options

Try to repair the disk permissions:

more options

Thanks Cor-El. As of OS X El Capitan, Apple no longer permits/requires repairing permissions. Disk Utility now has no such option. Apparently they think that the critical permissions are now invulnerable. (cf., SS Titanic).