[26875] in Athena Bugs

home help back first fref pref prev next nref lref last post

Re: [help.mit.edu #246059] closing Firefox

daemon@ATHENA.MIT.EDU (Robert Basch)
Tue Jul 4 00:39:10 2006

In-Reply-To: <rt-3.4.2-246059-2625148-145.11.3223271694527@help.mit.edu>
Mime-Version: 1.0 (Apple Message framework v750)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <F23C0BDD-90EB-4594-B756-C2E652BFCC0F@mit.edu>
Content-Transfer-Encoding: 7bit
From: Robert Basch <rbasch@mit.edu>
Date: Tue, 4 Jul 2006 00:39:04 -0400
To: mjwu@mit.edu
X-Spam-Score: 5.261
X-Spam-Level: ***** (5.261)
X-Spam-Flag: NO
Cc: bugs@mit.edu, acis-help@mit.edu
Errors-To: bugs-bounces@mit.edu

>> When trying to launch Firefox on athena , I get the following  
>> error message:
>>
>> Firefox is already running, but is not responding. To open a new  
>> window,
>> you must first close the existing Firefox process, or restart your  
>> system
>>
>> What should I do?

The error message indicates that another firefox process has locked
your profile.  Our firefox wrapper script tries to ensure that you will
only see this error when another running process actually holds
the lock; the "not responding" error suggests that such a process
might be hung, or is running on a different X display.

The process ID of the lock-holder can be determined by running the
following command:

testlock $HOME/.mozilla/firefox/*.*/.parentlock

If the profile is actually locked, this will output the ID of the  
locking
process (0 if the lock is held by a process on another machine).
You should terminate any such process, if possible.

If you are certain that you are not running firefox on any machine,
you can remove the .parentlock file; this should allow firefox to
start.  (Doing this when another firefox process is already running
risks corrupting the profile, though).

Bob



Robert Basch
Infrastructure Software Development and Architecture
Information Services & Technology




home help back first fref pref prev next nref lref last post