This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

ఇంకా తెలుసుకోండి

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