[Bug 73457] Re: MASTER "Firefox is already running, but is not responding" when /home is an NFS directory

[Alexander Sack]

On Mon, Nov 03, 2008 at 09:36:07PM -0000, stevenschlansker wrote:
> I apologize for resurrecting this bug report from the dead, but I
> anticipate that if I file a new report it will just be marked as a
> duplicate of this one :)
> 
> I recently upgraded a few machines to Intrepid and am now experiencing this problem.  Same symptoms - 90% of the time firefox says it's already running or refuses to start at all (no windows or anything).  Firefox is already not running.  There's no stale lockfiles.
> Remounting the NFS file system with nolock mitigates the problem, but that's obviously not an acceptable long-term solution
> 

I have at least one more report about NFS /home and problems with
"already running".

>From current evaluation its the places.sqlite file in your profile.

AFAIR, mvoing that to a different place and moving immediately back
will fix that. Seemed a bit like a lock to me. Also it only happens
when cold booting or when umount doesnt properly work on shutdown.

You think thats the same bug?

How did you check that there is no stale lock file on nfs client side?

 - Alexander

-- 
MASTER "Firefox is already running, but is not responding" when /home is an NFS directory 
https://bugs.launchpad.net/bugs/73457
You received this bug notification because you are a member of Mozilla
Bugs, which is subscribed to firefox in ubuntu.