為了改善您的使用體驗,本網站正在進行維護,部分功能暫時無法使用。若本站的文件無法解決您的問題,想要向社群發問的話,請到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 發問,我們的社群成員將很快會回覆您的疑問。

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

Firefox 30.0 will not open profiles on my server, only local ones. (Ubuntu 14.04 LTS)

  • 3 回覆
  • 2 有這個問題
  • 8 次檢視
  • 最近回覆由 ExFido

I get the dreaded "Profile in use" error any time I try to open a profile that's stored on my network attached file server (it works fine for locally stored profiles).

I get this only under Ubuntu 14.04. I'm also running FF 30.0 under Windows (including in a VMWare virtual Windows machine under Ubuntu) and it works fine.

It's creating a .parentlock file each time, then claiming the profile is in use, then leaving the .parentlock file upon closing the message box. Deleting the .parentlock file by hand doesn't fix it: it creates it again the next time I try to run and again claims the profile is open. This happens for every user and every NAS profile on my system. But again, only under Ubuntu 14.04, not under Windows, and only for profiles on my server, not locally.

I get the dreaded "Profile in use" error any time I try to open a profile that's stored on my network attached file server (it works fine for locally stored profiles). I get this only under Ubuntu 14.04. I'm also running FF 30.0 under Windows (including in a VMWare virtual Windows machine under Ubuntu) and it works fine. It's creating a .parentlock file each time, then claiming the profile is in use, then leaving the .parentlock file upon closing the message box. Deleting the .parentlock file by hand doesn't fix it: it creates it again the next time I try to run and again claims the profile is open. This happens for every user and every NAS profile on my system. But again, only under Ubuntu 14.04, not under Windows, and only for profiles on my server, not locally.

所有回覆 (3)

This is mote likely a problem with (write) permissions of files in the Firefox profile folder.

In Firefox 13+ the parent.lock (Windows) or .parentlock (Linux, Mac) file is no longer removed in order to detect startup failures (crashes) and offer to start in Safe mode.

I didn't realize they weren't removed any longer. Thank God! That issue drove me nuts. Any thoughts on what the permissions issue might be and how I could fix it? The .parentlock is created with me as owner and -rw-rw-r-- permissions.

由 ExFido 於 修改

Oh well, I'll just keep using Chrome. I don't support Mozilla's war on free speech, anyway.