On Thu, Dec 26, 2002 at 02:39:05PM -0500, Beartooth wrote:
> It used to be -- in RH 7.2, anyway -- when something got
> hung up, that you could right-click on its little spot on the
> panel, whatever that's called, and along with choices like
> Maximize, Minimize, etc., you got one for Kill App. Very useful for
> us subtechnoids, who don't have command line kills at our finger
> tips. I hope very much that this is some kind of oversight, or
> well-meaning paternalistic wrongness ("protect the poor little user
> from herself"), which will be rectified in Phoebe. Any point in
> saying so on the phoebe list, or is it already too late for that?
> And if so, how do I file an RFE -- or more properly a Request For
> Re-Enhancement??
"kill app" always did something completely stupid - it called close()
on the application's X server connection. If the app was stuck in an
infinite loop or otherwise stuck, "kill app" wouldn't. Kill the app
that is. It didn't work, it's that simple. Quite apart from any
usability rationale.
If you close a GTK 2 app (and hopefully Qt3.1 apps, though I haven't
checked if Troll Tech added support), if the app is locked up metacity
will offer to kill it for you. And when metacity kills it will (when
possible) use "kill", not close() on the X server connection. kwin may
do the same, I don't know.
If you run non-GTK2/Qt3.1 apps, add a launcher to your panel that runs
xkill. Very easy, if you actually know enough about the technical
details to have any business calling close() on an X server connection
in the first place. (If you don't understand what that implies, then
you should not use xkill, because you won't understand why xkill
frequently doesn't work or what to do when it fails.)
Another GUI approach to the problem is System Tools -> System Monitor
and kill from there.
And if you have an app that locks up all the time, please report that
bug...
Havoc
--
Psyche-list mailing list
Psyche-list@redhat.com
https://listman.redhat.com/mailman/listinfo/psyche-list
