Slackware This Forum is for the discussion of Slackware Linux.
|
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
05-24-2006, 04:13 PM
|
#1
|
Member
Registered: Jan 2006
Location: USA
Distribution: Any distro I can get my hands on!
Posts: 162
Rep:
|
Can't kill firefox
I have been having a lot of trouble with firefox lately. It locks up quite a bit. In KDE I use 'ctrl-atl-esc' to kill firefox and if it won't start back up I use 'ctrl-esc' and kill the firefox proccess.
In gnome I can't seem to kill the firefox-bin proccess. I use xkill to kill firefox then I can't open it back up. So I try to kill the proccess but it doesn't work.
Quote:
nate@nate:~$ ps -A | grep firefox
2605 ? 00:00:38 firefox-bin
2607 ? 00:00:00 firefox-bin <defunct>
nate@nate:~$ kill 2605
nate@nate:~$ kill 2607
nate@nate:~$ ps -A | grep firefox
2605 ? 00:00:38 firefox-bin
2607 ? 00:00:00 firefox-bin <defunct>
|
I don't know why I can't kill the proccess?
PS: How do you type in " | "? I can't seem to find it on my keyboard.
Last edited by natewlew; 05-24-2006 at 04:17 PM.
|
|
|
05-24-2006, 04:18 PM
|
#2
|
Senior Member
Registered: Aug 2005
Distribution: Slackware, RHEL
Posts: 1,271
|
Quote:
Originally Posted by natewlew
I have been having a lot of trouble with firefox lately. It locks up quite a bit. In KDE I use 'ctrl-atl-esc' to kill firefox and if it won't start back up I use 'ctrl-esc' and kill the firefox proccess.
In gnome I can't seem to kill the firefox-bin proccess. I use xkill to kill firefox then I can't open it back up. So I try to kill the proccess but it doesn't work.
I don't know why I can't kill the proccess?
PS: How do you type in " | "? I can't seem to find it on my keyboard.
|
Try kill -9 "pid" and see if that works.
|
|
|
05-24-2006, 04:27 PM
|
#3
|
Member
Registered: Jan 2004
Location: /lost+found
Distribution: Slackware 14.2
Posts: 849
Rep:
|
Maybe killall firefox will work for you.
Quote:
PS: How do you type in " | "? I can't seem to find it on my keyboard.
|
I don't understand your question.
|
|
|
05-24-2006, 04:43 PM
|
#4
|
Senior Member
Registered: Oct 2003
Location: lost in the midwest...
Distribution: Slackware
Posts: 1,098
Rep:
|
"|" is located (in the us anyways) under the backspace key and shares with "\"
try "killall firefox"
that usually works for me, too.
|
|
|
05-24-2006, 04:44 PM
|
#5
|
Member
Registered: Oct 2005
Posts: 518
Rep:
|
You can also try the pkill command.
|
|
|
05-24-2006, 05:19 PM
|
#6
|
Member
Registered: Jan 2006
Location: USA
Distribution: Any distro I can get my hands on!
Posts: 162
Original Poster
Rep:
|
Quote:
nate@nate:~$ kill -9 "pid"
bash: kill: pid: arguments must be process or job IDs
nate@nate:~$ kill -9 "pid" 2605
bash: kill: pid: arguments must be process or job IDs
nate@nate:~$ ps -A | grep firefox
nate@nate:~$
|
Thanks, that did it (not sure which one).
Quote:
"|" is located (in the us anyways) under the backspace key and shares with "\"
|
Thank You
|
|
|
05-24-2006, 05:26 PM
|
#7
|
Senior Member
Registered: Aug 2005
Distribution: Slackware, RHEL
Posts: 1,271
|
Quote:
Originally Posted by natewlew
Thanks, that did it (not sure which one).
Thank You
|
Well, actually, the "pid" part mean to put in whatever PID that firefox was running. For example, if firefox was running a pid of 2063, to kill the process, you would have to do "kill -9 2063", without the quotes of course.
|
|
|
05-24-2006, 05:37 PM
|
#8
|
Member
Registered: Oct 2003
Location: Heidelberg, Germany
Distribution: Slackware 11.0; Kubuntu 6.06; OpenBSD 4.0; OS X 10.4.10
Posts: 345
Rep:
|
When you killed it, did firefox die gracefully? I mean, it didn't mess up your screen and lock out your keyboard did it?
I had a problem with a slowdown yesterday, and when I did a `ps ax` it showed a firefox process I couldn't explain. At the time, firefox wouldn't redraw its window after being brought back from minimize. I thought killing the unexplained firefox process my help things, but it ended up kicking me out of X and leaving me with an unusable console filled with colored lines.
Could be the nvidia driver too, though. I haven't finished testing.
|
|
|
05-25-2006, 04:41 PM
|
#9
|
Member
Registered: Jan 2006
Location: USA
Distribution: Any distro I can get my hands on!
Posts: 162
Original Poster
Rep:
|
Quote:
Originally Posted by stormtracknole
Well, actually, the "pid" part mean to put in whatever PID that firefox was running. For example, if firefox was running a pid of 2063, to kill the process, you would have to do "kill -9 2063", without the quotes of course.
|
Thanks for the instruction.
Quote:
When you killed it, did firefox die gracefully? I mean, it didn't mess up your screen and lock out your keyboard did it?
|
No, I didn't have that problem.
|
|
|
05-26-2006, 02:25 AM
|
#10
|
Member
Registered: Sep 2004
Location: On a compile thread
Distribution: CentOS, Debian, Fedora, Gentoo, Mandriva, Slackware, Ubuntu
Posts: 42
Rep:
|
Quote:
Originally Posted by stormtracknole
Well, actually, the "pid" part mean to put in whatever PID that firefox was running. For example, if firefox was running a pid of 2063, to kill the process, you would have to do "kill -9 2063", without the quotes of course.
|
Addendum: Don't use kill -9 often. Kill and killall are prefered, as they send signals. kill -9 rips the fabric of time and space to terminate your thread. It looks awefull to the tapestry. Kinda like Baelfire, to the WoT fans [I am NOT one].
|
|
|
05-26-2006, 05:24 AM
|
#11
|
Member
Registered: Oct 2003
Location: Heidelberg, Germany
Distribution: Slackware 11.0; Kubuntu 6.06; OpenBSD 4.0; OS X 10.4.10
Posts: 345
Rep:
|
Quote:
Originally Posted by ORBiTrus
kill -9 rips the fabric of time and space to terminate your thread. It looks awefull to the tapestry.
|
Well, that would explain the colored stripes across my screen. When it happens again, I'll just clutch my towel a little closer and think to myself, "Don't panic."
|
|
|
05-26-2006, 06:36 AM
|
#12
|
Senior Member
Registered: Aug 2003
Location: UK
Distribution: Slackware
Posts: 3,467
Rep:
|
Quote:
Originally Posted by hussar
an unusable console filled with colored lines.
Could be the nvidia driver too, though. I haven't finished testing.
|
nvidia driver does that if you have framebuffer console enabled
|
|
|
05-26-2006, 06:46 AM
|
#13
|
Member
Registered: Sep 2004
Location: Hyderabad
Distribution: FEDORA,REDHAT,HOST
Posts: 440
Rep:
|
killall firefox-bin
|
|
|
05-26-2006, 10:41 AM
|
#14
|
Senior Member
Registered: Aug 2005
Distribution: Slackware, RHEL
Posts: 1,271
|
Quote:
Originally Posted by ORBiTrus
Addendum: Don't use kill -9 often. Kill and killall are prefered, as they send signals. kill -9 rips the fabric of time and space to terminate your thread. It looks awefull to the tapestry. Kinda like Baelfire, to the WoT fans [I am NOT one].
|
Hmm...that's weird. I've never had any problems with kill -9.
|
|
|
All times are GMT -5. The time now is 07:14 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|