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 Setup: Client: Intrepid Ibex up-to-date amd64 with /home mounted NFS Server: FreeBSD 7 with a UFS2 volume exported Could someone confirm and/or reopen the bug? I am very willing to help troubleshoot, but I'll need some guidance - I don't know too much about NFS locking. Thanks, Steven Schlansker -- 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
