Tìm kiếm hỗ trợ

Tránh các lừa đảo về hỗ trợ. Chúng tôi sẽ không bao giờ yêu cầu bạn gọi hoặc nhắn tin đến số điện thoại hoặc chia sẻ thông tin cá nhân. Vui lòng báo cáo hoạt động đáng ngờ bằng cách sử dụng tùy chọn "Báo cáo lạm dụng".

Tìm hiểu thêm

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

  • 3 trả lời
  • 2 gặp vấn đề này
  • 8 lượt xem
  • Trả lời mới nhất được viết bởi ExFido

more options

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.

Tất cả các câu trả lời (3)

more options

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.

more options

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.

Được chỉnh sửa bởi ExFido vào

more options

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