Excerpts from Tim Gelter's message of Mon Jul 20 10:48:54 -0400 2009:
2009/7/20 Dario <carotinobg@yahoo.it>:
Hi!
In data lunedì 20 luglio 2009 06:48:00, Tim Gelter ha scritto:
"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." Mmm I remember something like this happening on Windows (*cough*) machines at school. The solution was to clear the hidden Application Data (or what is called) folder under Documents and Settings. Here probably is something like a lock file, I think.
Ciao!
Carotinho Chiacchiera con i tuoi amici in tempo reale! http://it.yahoo.com/mail_it/foot/*http://it.messenger.yahoo.com
In ~/.config/mozilla/firefox/[profile] there will be 2 files, "lock" and ".parent_lock" that need to be removed, at least those are the offending 2 when this has happened to me. In my case, this isn't a lock file issue. As I explained in my email
Damien Churchill wrote: that triggered this thread, the firefox process does in fact continue running after I attempt to close firefox. It'll run (consuming very little resources) for as long as it takes (minutes, hours, whatever) for me to decide to launch firefox again. At this point, I must kill the existing firefox process before launching firefox once more. Again, this isn't a lock file issue in my case.
I don't know what you issue is (though I don't find Firefox good in general), but I can provide you a way to automatically kill Firefox on firefox exit if you like... (just a wrapper shell script/alias) -- Andrei Thorp, Developer: Xandros Corp. (http://www.xandros.com)