I have the same problem - I am using central HOME directories, mounted with NFS. Sometimes, I cannot start Firefox (same message as in title).
I can (temporarily solve it, if I restart the nfs server (I use nfs-kernel-server), but the error reoccurs after a few days. I also have a problem with openoffice (with Locking Enabled) despite having nfs-common installed on the clients (but I did not find statd lockd tools? are they included somewhere else?). What I use: - Server: Edgy, nfs-kernel-server - Client: Edgy, nfs-common What does not help: - removing ~/.mozilla on client - restarting client - (re)mount nfshomes on client What _does_ help: - on client: mount nfshomes with "nolock" option - on server: init.d/nfs-kernel-server restart So, to me, it looks like a locking problem. For now I can work around this if I disable nfs locking completely (nolock), but this is no solution. How can I get the locking tools to work with ubuntu? Thank you, Matthias -- "Firefox is already running, but is not responding" https://bugs.launchpad.net/bugs/73457 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
