Timeline for Fix "firefox is already running" issue in Linux
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 11, 2013 at 19:55 | comment | added | user66001 |
NOTE: The above will not allow Firefox to perform closing operations (like the other pkill/kill options discussed elsewhere on this question, will, as they currently are) and will lead to (amongst other things) the lock symlink not being deleted, which will cause the message in this question to remain. See my answer for more details.
|
|
| Jun 9, 2013 at 18:09 | history | edited | Devyn Collier Johnson | CC BY-SA 3.0 |
corrections
|
| Jun 9, 2013 at 16:14 | comment | added | Rafael Cavalcanti | Not really. killall matches the pattern exactly. What you said is valid for pkill: it kills all processes containing that pattern (unless you pass -x in the arguments). For instance, "pkill refox" will kill firefox, but "killall refox" won't do anything (unless you have a "refox" process running). | |
| Jun 8, 2013 at 18:32 | history | answered | Devyn Collier Johnson | CC BY-SA 3.0 |