搜尋 Mozilla 技術支援網站

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

了解更多

Thunderbird already running on UNIX system

  • 1 回覆
  • 1 有這個問題
  • 1 次檢視
  • 最近回覆由 fuffberry

more options

Attempts to start Thunderbird on a UNIX system result in a 'Thunderbird already running' message. This is even though Thunderbird is not already running and, there is no .parentlock present

Attempts to start Thunderbird on a UNIX system result in a 'Thunderbird already running' message. This is even though Thunderbird is not already running and, there is no .parentlock present

被選擇的解決方法

Thunderbird responds with the already running message if someone is holding the .parentlock or, you are unable to create that .parentlock at startup.

My Thunderbird has several email profiles on an Ubuntu system with multiple user accounts. These multiple user accounts (IDs) have access to the various Thunderbird profiles.

Somehow the permission bits on several of the email profiles got flipped (from 777 to 775) resulting in loss of permission to create new files in the profile directory. The .parentlock is created when Thunderbird starts but, if permission is denied to create a file - Thunderbird thinks it's because the profile is in use.

Setting permissions of 777 solved this problem. Permissions of 770 would have also worked if every ID who should be able to open a specific profile were in the group association with the profile directory

從原來的回覆中察看解決方案 👍 0

所有回覆 (1)

more options

選擇的解決方法

Thunderbird responds with the already running message if someone is holding the .parentlock or, you are unable to create that .parentlock at startup.

My Thunderbird has several email profiles on an Ubuntu system with multiple user accounts. These multiple user accounts (IDs) have access to the various Thunderbird profiles.

Somehow the permission bits on several of the email profiles got flipped (from 777 to 775) resulting in loss of permission to create new files in the profile directory. The .parentlock is created when Thunderbird starts but, if permission is denied to create a file - Thunderbird thinks it's because the profile is in use.

Setting permissions of 777 solved this problem. Permissions of 770 would have also worked if every ID who should be able to open a specific profile were in the group association with the profile directory