Andrei Thorp wrote: > Excerpts from Tim Gelter's message of Mon Jul 20 11:18:38 -0400 2009: >> Andrei Thorp wrote: >>> Excerpts from Tim Gelter's message of Mon Jul 20 10:48:54 -0400 2009: >>>> Damien Churchill wrote: >>>>> 2009/7/20 Dario <carotinobg@xxxxxxxx>: >>>>>> 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 >>>> 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) >> I appreciate the offer, but it'd be easy enough to do something like: >> alias firefox="killall firefox && firefox" >> What I'm looking for is an answer to why Firefox has this issue on arch, >> but not on other mainstream distros. Or am I really the only user >> experiencing this issue? (other than the couple of guys who responded >> saying that deleting a lock file or two solved the issue for them) > > Yeah, I figured you'd know how to do this. I can't speak for everyone, > but I have no such issues like this with Firefox personally, I'm sorry > to say. To whomever might have insight into what's happening, here is what happens if I attach to the running firefox process after closing firefox. I can also attach a trace of firefox from the beginning of operation if that would help. If this is better meant to be included as a bug report, I can certainly do that but I fear it'll be rejected as "works for me" by a developer as it seems it only affects some of us. # ps -ef | grep -i firefox tgelter 4688 4329 2 08:40 ? 00:01:23 /usr/bin/firefox root ~ # strace -p 4688 Process 4688 attached - interrupt to quit futex(0x7fea3538c0d0, FUTEX_WAIT_PRIVATE, 2, NULL ^C <unfinished ...> Process 4688 detached
Attachment:
signature.asc
Description: OpenPGP digital signature
