If an application stops responding how do I force it to quit without rebooting
thanks
(Not pretty but) Usually if you click the living daylights out of the close button, you’ll get a terminate box pop up.
Otherwise you can stop user tasks with the system monitor
After that it gets a little more complicated…
caf4926 wrote:
> (Not pretty but) Usually if you click the living daylights out of the
> close button, you’ll get a terminate box pop up.
Or if you click it just once and then wait the same length of time as
you’d otherwise spend clicking the living daylights, you may find a box
still pops up saying that the program is not responding 
YMMV of course.
On 06/07/2011 12:06 PM, jimt123 wrote:
>
> If an application stops responding how do I force it to quit without
> rebooting
since you don’t tell your desktop environment i’ll assume it is the same
as mine:
- press and hold Alt, then press F2
- a small blank will pop up at the top center of the screen, just to the
left of the blank, are two tiny icons, a wrench/spanner on the left and
a ‘heartbeat’ monitor looking thing to its right…
-click on the monitor icon
-find the name of the application not responding
-highlight it with a single left click, then click the “End Process”
button…
alternatively:
-open a terminal
-type in and enter top
-find the non-responding program
-in the first column will be a four digit number
-press ‘q’ (which will end top and return you to the prompt)
-carefully type in and enter kill [1234] or whatever the number is
-type exit and enter
another alternative:
-click on the non-responding window to give it focus
-press Ctrl+Alt+Esc
-your mouse pointer turns into a skull and crossbones
-hold the skull over the non-responding application and single left click
another…nah! that is enough for now…
–
dd CAVEAT: http://is.gd/bpoMD
via NNTP openSUSE 11.4 [2.6.37.6-0.5] + KDE 4.6.0 + Thunderbird 3.1.10
Acer Aspire One D255, 1.66 GHz Atom, 1 GB RAM, Intel Pineview graphics
- When your gecko is broken you have a reptile dysfunction! *
On Tue, 07 Jun 2011 10:20:20 +0000, DenverD wrote:
> -open a terminal
> -type in and enter top
> -find the non-responding program
> -in the first column will be a four digit number -press ‘q’ (which will
> end top and return you to the prompt) -carefully type in and enter
> kill [1234] or whatever the number is -type exit and enter
Or in top, you can just press ‘k’ and enter the process ID.
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
Alt, then press F2
xkill
On 06/07/2011 07:12 PM, Jim Henderson wrote:
> Or in top, you can just press ‘k’ and enter the process ID.
i must have forgotten that some years ago…right after i forgot what i
had for breakfast.
the test will be if i remember that the next time i need it (if not i’ll
do “q kill [PID]” like usual)
–
dd CAVEAT: http://is.gd/bpoMD
via NNTP openSUSE 11.4 [2.6.37.6-0.5] + KDE 4.6.0 + Thunderbird 3.1.10
Acer Aspire One D255, 1.66 GHz Atom, 1 GB RAM, Intel Pineview graphics
- When your gecko is broken you have a reptile dysfunction! *
thanks everyone
In KDE you can simply use the key combination [CTRL][ALT][ESC] (this runs
xkill).
–
PC: oS 11.3 64 bit | Intel Core2 Quad Q8300@2.50GHz | KDE 4.6.3 | GeForce
9600 GT | 4GB Ram
Eee PC 1201n: oS 11.4 64 bit | Intel Atom 330@1.60GHz | KDE 4.6.0 | nVidia
ION | 3GB Ram
Thanks for these folks, I get a lot of hang/freezes with Windows apps under wine/xover (my bad, prolly), and these killers will be v. handy, ty ty…
> -open a terminal
> -type in and enter top
> -find the non-responding program
> -in the first column will be a four digit number -press ‘q’ (which will
> end top and return you to the prompt) -carefully type in and enter
> kill [1234] or whatever the number is -type exit and enter
Or in top, you can just press ‘k’ and enter the process ID.