Solution: Try finding and closing running Firefox process(es) on other nodes and clusters.With many clusters sharing common home directory, a running Firefox instance on one can affect another. Reason: You may indeed have another Firefox process (in another Thinlinc or Gateway session on this or other cluster, another front-end or compute node).Solution: If you are certain you do not have any other Firefox processes running elsewhere, please use the following command in a terminal window to detect and remove the lock files:.the job got terminated, session ended, node crashed or rebooted, etc). Reason: You had a single Firefox process running, but it terminated abruptly without a chance to clean its lock files (e.g.This error can happen due to multiple reasons: If a newly-started Firefox instance detects the presence of these lock files, it complains. When Firefox runs, it creates several lock files in the Firefox profile directory (inside ~/.mozilla/firefox/ folder in your home directory).
Link to section 'Solution' of 'Close Firefox / Firefox is already running but not responding' Solution You must first close the existing Firefox process, or restart your system.
You receive the following message after trying to launch Firefox browser inside your graphics desktop: Close Firefoxįirefox is already running, but not responding. Close Firefox / Firefox is already running but not responding Link to section 'Problem' of 'Close Firefox / Firefox is already running but not responding' Problem
0 kommentar(er)
