Linux firefox is already running but

Исправлена ​​проблема «Firefox уже запущен» в Linux

Я пытаюсь открыть Firefox в CentOS, но получаю следующее сообщение:

Firefox уже запущен, но не отвечает

и Firefox не открывается. Я попробовал это в командной строке:

но это не сработало. Кроме того, я не знаю, в каком каталоге я должен выполнять правильные команды.

Как я могу это исправить?

1) файл с именем .parentlock
-AND-
2) символическая ссылка с именем lock
. в

/ .mozilla / firefox / случайная строка буквенно-цифровых символов .default /

Первый присутствует во время работы Firefox, чтобы предотвратить одновременную запись более одного экземпляра в один и тот же набор файлов профиля, и если Firefox не закрывается чисто, ни один из них не может быть удален.

Сообщение об ошибке, полученное в этом случае, должно быть:

Из любой точки файловой системы (или удалив это, если в pwd отчетах ), заменив случайную строку буквенно-цифровых символов на папку профиля FF на вашем компьютере, выполните (при условии, что первое предложение выполнено), чтобы удалить их, если не запущен процесс Firefox. ,

/.mozilla/firefox/random string of alphanumeric characters.default rm

/.mozilla/firefox/random string of alphanumeric characters.default/.parentlock

/.mozilla/firefox/random string of alphanumeric characters.default/lock`

Более менее авторитетная информация здесь .

Источник

«Firefox is already running but is not responding» error — How to fix

All of your personal settings, bookmarks, and other information are kept in your Firefox profile. Firefox needs an unlocked profile to start up, and if the profile is locked, it displays the message, Firefox is already running, but is not responding A copy of Firefox is already open . This article explains what to do if you see this message and how to prevent it from showing at startup.

Table of Contents

End Firefox processes

If Firefox did not shut down normally when you last used it, Firefox might still be running in the background, even though it is not visible. If you try to open it while it’s running, an error message will appear with the option to click Close Firefox . If that doesn’t solve the problem, restart your computer or try the following options. Restart your computer to see if the problem goes away or try the following options.

Ubuntu Linux

1. Click on System and choose Administration .
2. In Administration, click on System Monitor . Here you will find firefox-bin one or more times.
3. Highlight the listing and click End Process for each one.

Use the Windows Task Manager to close the existing Firefox process

1. Right-click on an empty spot in the Windows task bar and select Task Manager (or press Ctrl + Shift + Esc ).
2. When the Windows Task Manager opens, select the Processes tab.
3. Select the entry for firefox.exe (press F on the keyboard to find it) and click End Process .
4. Click Yes in the «Task Manager Warning» dialog that appears.
5. Repeat the above steps to end all additional firefox.exe processes, then exit the Windows Task Manager.
6. Start Firefox normally.

Remove the profile lock file

Firefox may have shut down abnormally, leaving the lock file in place. To fix this, open the profile folder (see Finding your profile without opening Firefox) and delete the parent.lock file lock and .parentlock files .parentlock file .

Remove the -no-remote startup option

If you start Firefox with the -no-remote command line option, try removing this option.

Initialize the connection to a file share

If you store the profile on a file share, try accessing the file share beforehand using Windows Explorer.

Check access rights

Firefox must also have the right to create files in the profile folder. The error can occur if you try to use a profile from a file system mounted with read-only permission (e.g. a remote Windows share which doesn’t have «Allow network users to change my files» checked).

To check if the profile folder has the proper permissions:

1. Find your Firefox profile folder — see Finding your profile without opening Firefox.
   • If you only have one profile, its folder would have «default» in the name.
2. Right-click on your profile folder and select Properties .
3. Click on the General tab.
4. Make sure Read-only is not checked marked.

1. Find your Firefox profile folder — see Finding your profile without opening Firefox.
   • If you only have one profile, its folder would have «default» in the name
2. Hold down the Ctrl key while you click on your profile folder, and select Get Info .
3. Make sure Ownership & Permissions is set to Read & Write.

1. Find your Firefox profile folder — see Finding your profile without opening Firefox
   • If you only have one profile, its folder would have «default» in the name.
2. Right-click on your profile folder and select Properties .
3. Click on the Permissions tab.
4. Make sure Folder access is set to Create and delete files.

Restore data from a locked profile

If you are unable to unlock the profile using the above methods, use the Profile Manager to create a new profile and migrate your data from the locked profile to the new profile. For information on how to do this, see Recovering important data from an old profile.

These fine people helped write this article:

Volunteer

Grow and share your expertise with others. Answer questions and improve our knowledge base.

Related Articles

Firefox won’t start — find solutions

This article describes what to do if Firefox doesn’t open when you click the Firefox icon. If you get a message you can dismiss (e.g.

How to run Firefox when your profile is missing or inaccessible

If you see a «Profile Missing» error message that says, Your Firefox profile cannot be loaded. It may be missing or inaccessible it usually means.

Источник

Taufan Lubis – Ubuntu Linux

Be free…. be yourself with Linux.

Firefox Error – Firefox is already running, but not responding

September 24, 2008 by taufanlubis

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.

Share this:

Like this:

Related

Posted in How To | 16 Comments

16 Responses

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.

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.

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.”

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:

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

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 !

Источник