Below is the common error that I always have when I force my Firefox to close.
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.
You can’t fix it by log out from the system. You can only do 2 things, kill the Firefox process or restart your system. The second option will take a longer time, so let’s do the first one.
Open your Linux terminal (Applications>Accessories>Terminal) then type: ps ax | grep firefox.
You will see the PID number on the left side. PID is Program Identifier. The number can be different.
Have to have stop the process by kill the PID one by one.
Now, start your Firefox again. If you see the screen below mean the problem is fixed.
in short: killall firefox-bin
This hasn’t happen to me in Linux yet but it used to happen once in a while in Windows. What I’d do is just go to the task manager(Ctrl+Alt+Delete) and end the process there.
Thanks for bringing it up though!:)
I just wish I could use FF3 in Gentoo, FF2 is good but not as cool.
-Clinton
Cheers for this. Has happened to me and I’m only a linux neophyte so didn’t know what to do. Now I will in as long as I remember.
Dom
I am a Win XP user and this happens quite regularly for me when I try to open FF 3 immediately after I close it. I wait for some time before trying to open FF 3 and it will open properly !
This has been happening to me quite a bit lately. Haven’t had any problems with firefox before now, but it’s just getting annoying.
It’s not that I can wait it out, I leave my computer on for most of the time, and after coming back after several hours and try to open it it’ll pop up.
Anyone know why it does this or how to prevent it?
After killing the process it just shows up with a new PID no matter how many times I kill it. Worse yet, rebooting isn’t correcting it either. This may have something to do with this being and LDAP authenticated machine.
Also this doesn’t happen with other (non-LDAP) accounts.
Removing the profile corrects the problem. Most likely there is a lock file somewhere in there that is causing this problem.
Firefox is renowned for this problem with not responding, there is a good thread on solving the problem here http://www.nettechguide.com/forums/showthread.php?t=111469
This is happening to me in Windows, but it is not showing up in Task Manager. What would you suggest I do?
Actually, I’ve never use Firefox in Win before I move to Ubuntu.
Have you tried with Log off? If not, then no choice, you have to reboot it.
Sorry, can’t help you.
Yeah – the “suggested solution” is KIND OF fine., SOMETIMES;
Except when Firefox IS just BOGGED DOWN and RUNNING the computer FLAT OUT servicing it’s own memory leaks…
Then this occasionally AWFUL program will sit there and do this crap of thrashing the disk cache for hours;
So the only thing that works then is hitting the power off button; otherwise nothing clicked on will come up for 1/2 an hour…
And getting into a terminal to kill off FF – yeah “Like When”.
I’d like a simple KEY command to just HALT all the running process’s like Ctrl Alt Del, so I could THEN go into System Monitor and kill off Firefox there….
You know that works like smashing my laptop with a big hammer on the CPU.
Someone else summed it up like this:
“Our problem is that its near impossible to kill processes whilst they are running amock (this would help, and could give gnome-system-monitor a better nice level too automatically). Microsoft has implemented this perfectly. If there are dodgy processes running, its always VERY easy to kill them. With us, you have to spend 15mins waiting for menus to open, etc. And then since gnome-system-monitor will run with low privileges, it will be quite unresponsive.”
This WORKS:
Alt-F2 to bring up run dialog, enter xkill then click on the app you want to terminate.
(that is easy I can remember that)
There are combinations of keys listed:
Putting the “System Monitor” and “Force Quit” applets on your tool bar / panel and then clicking on them.
Not tried by me:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
* CTRL + ALT+ F2 (get to a terminal, you can then run top/kill/pkill to discover and kill the offending process)
* ALT+ SYSRQ + R then CTRL + ALT+ F2 (as above, but first try to regain control of the keyboard)
* CTRL + ALT + Backspace (kills the graphic session and goes to a console, all graphical applications are terminated too)
* ALT+ SYSRQ + R then ALT + Backspace (as above, but first try to regain control of the keyboard)
* CTRL + ALT + DEL (reboot)
* ALT+ SYSRQ + R then CTRL + ALT + DEL (as above, but first try to regain control of the keyboard)
* ALT+ SYSRQ + R + S + U + B (forces a clean reboot even when the keyboard is not responding)
is from a wiki. SYSRQ is the print screen key on my keyboard. it may differ for you.
here is a good site with more answers to your question:
http://www.freesoftwaremagazine.com/columns/closing_down_gnu_linux_safely_with_sysrq+
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
For the keyboard binding part: bind gnome-system-monitor to Ctrl+Alt+Del key combo.
gconftool-2 -t str –set /apps/metacity/global_keybindings/run_command_9 “Delete”
gconftool-2 -t str –set /apps/metacity/keybinding_commands/command_9 “gnome-system-monitor”
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Try SHIFT+BACKSPACE. The caveat: All of your programs will close. But then, it would kill X.
Or another thing: Try pressing the X Button many times while the application does not respond. A popup window will appear asking you if you want to force kill the application or not. Just kill the application.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ctrl + alt + backspace
http://maketecheasier.com/4-ways-to-get-yourself-out-of-a-ubuntu-crash/2008/09/01
2) Restart ‘X’
If the whole system comes to a freeze and does not accept any keyboard or mouse input, try to restart ‘X’ by pressing ‘Ctrl + Alt + Backspace‘. This will kill all processes and log you out. If this works, it should bring you to the login screen again.
3) Use MagicSys Key to kill all processes
If the crash is so serious that Ctrl + Alt + Backspace have no effect at all, try pressing the MagicSysKey ‘Alt + SysRq + K’ to kill all processes. The MagicSysKey is a set of keyboard combination that allow the users to perform various low level commands regardless of the system’s state using the SysRq key. In case you are wondering where the SysRq key is, in most keyboard configuration, it is found under the Print Screen button. In some laptop configuration, you might have to press the ‘Fn‘ button to access the SysRq key.
In short, press Alt + SysRq (possibly together with the ‘Fn‘ button) + K to kill all processes.
4) If all the above fail…
Try this MagicSysKey combination. It will sure work.
Press and hold Alt + SysRq, then one by one, press and release the following characters in the respective order: ‘R’ ‘E’ ‘I’ ‘S’ ‘U’ ‘B’. The system will perform a series of tasks and finally reboot the computer, safely.
This method should be used only if all other methods fail. If you have difficulty in remembering the character sequence, just remember the opposite of ‘BUSIER’.
hello, spring is cooming! good post there, tnx for taufanlubis.wordpress.com
I am a Win XP user and this happens quite regularly for me when I try to open FF 3 immediately after I close it. I wait for some time before trying to open FF 3 and it will open properly !
ок : мирово
Unfortunately this doesn’t work for me. Since FF 13 the file parent.lock isn’t removed from the profile. Actually system allowed to read and write access to that file even if the profile is in use by active firefox process. Anyway launching that -profile dir with -no-remote option in the Java results that error when no other FF processes are running. Surprisingly if you start the same command from the command prompt it works.