How do I abort xkill?
10 views
Skip to first unread message
Kenny McCormack
Jan 30, 2018, 5:18:27 PM1/30/18
to
I've discovered something a little annoying about xkill.
That is, there doesn't seem to be any way to get out of it without killing
anything. Nothing in the man page suggests any way to do this.
I found this out when I happened to run it by accident and then decided I
didn't want to kill anything. I was kinda stuck, since I couldn't click
on any window without killing it. (If I could have ssh'd in, I suppose I
could have killed it that way - but this particular machine was not
ssh-able)
Am I missing something? Is there a way?
--
The randomly chosen signature file that would have appeared here is more than 4
lines long. As such, it violates one or more Usenet RFCs. In order to remain
in compliance with said RFCs, the actual sig can be found at the following URL:
http://user.xmission.com/~gazelle/Sigs/BestCLCPostEver
That is, there doesn't seem to be any way to get out of it without killing
anything. Nothing in the man page suggests any way to do this.
I found this out when I happened to run it by accident and then decided I
didn't want to kill anything. I was kinda stuck, since I couldn't click
on any window without killing it. (If I could have ssh'd in, I suppose I
could have killed it that way - but this particular machine was not
ssh-able)
Am I missing something? Is there a way?
--
The randomly chosen signature file that would have appeared here is more than 4
lines long. As such, it violates one or more Usenet RFCs. In order to remain
in compliance with said RFCs, the actual sig can be found at the following URL:
http://user.xmission.com/~gazelle/Sigs/BestCLCPostEver
Lew Pitcher
Jan 30, 2018, 6:03:31 PM1/30/18
to
Kenny McCormack wrote:
> I've discovered something a little annoying about xkill.
>
> That is, there doesn't seem to be any way to get out of it without killing
> anything. Nothing in the man page suggests any way to do this.
[snip]
> I've discovered something a little annoying about xkill.
>
> That is, there doesn't seem to be any way to get out of it without killing
> anything. Nothing in the man page suggests any way to do this.
> Am I missing something? Is there a way?
The man page seems to give clues...
"If a pointer button is pressed over a non-root window, the server will
close its connection to the client that created the window."
"-button number
This option specifies the number of pointer button that should be
used in selecting a window to kill. ... By default, the first button
in the pointer map (which is usually the left-most button) is used."
It looks like, if you don't specify "any" (that is, if you let the button
number default), then the /other/ buttons will _abort_ the kill.
Try aborting by pressing the right (or centre) mouse button (assuming that
you didn't specify that button as the kill button).
--
Lew Pitcher
"In Skills, We Trust"
PGP public key available upon request
Kenny McCormack
Jan 30, 2018, 6:27:52 PM1/30/18
to
In article <p4qtis$avs$1...@dont-email.me>,
"root window" (right?)) and it will be a no-op (right?).
I've had mixed results with this. On at least one occasion, my system
started acting generally weird after this - and I'm pretty sure that some
system-critical desktop process had, in fact, been killed. So, I've stayed
away from this since then.
> "-button number
> This option specifies the number of pointer button that should be
> used in selecting a window to kill. ... By default, the first button
> in the pointer map (which is usually the left-most button) is used."
>
>It looks like, if you don't specify "any" (that is, if you let the button
>number default), then the /other/ buttons will _abort_ the kill.
>
>Try aborting by pressing the right (or centre) mouse button (assuming that
>you didn't specify that button as the kill button).
Yes. That works. Thanks.
--
The randomly chosen signature file that would have appeared here is more than 4
lines long. As such, it violates one or more Usenet RFCs. In order to remain
in compliance with said RFCs, the actual sig can be found at the following URL:
http://user.xmission.com/~gazelle/Sigs/GodDelusion
Lew Pitcher <lew.p...@digitalfreehold.ca> wrote:
>Kenny McCormack wrote:
>
>> I've discovered something a little annoying about xkill.
>>
>> That is, there doesn't seem to be any way to get out of it without killing
>> anything. Nothing in the man page suggests any way to do this.
>
>[snip]
>> Am I missing something? Is there a way?
>
>The man page seems to give clues...
> "If a pointer button is pressed over a non-root window, the server will
> close its connection to the client that created the window."
This implies that you can just click on the desktop background (which is a
>Kenny McCormack wrote:
>
>> I've discovered something a little annoying about xkill.
>>
>> That is, there doesn't seem to be any way to get out of it without killing
>> anything. Nothing in the man page suggests any way to do this.
>
>[snip]
>> Am I missing something? Is there a way?
>
>The man page seems to give clues...
> "If a pointer button is pressed over a non-root window, the server will
> close its connection to the client that created the window."
"root window" (right?)) and it will be a no-op (right?).
I've had mixed results with this. On at least one occasion, my system
started acting generally weird after this - and I'm pretty sure that some
system-critical desktop process had, in fact, been killed. So, I've stayed
away from this since then.
> "-button number
> This option specifies the number of pointer button that should be
> used in selecting a window to kill. ... By default, the first button
> in the pointer map (which is usually the left-most button) is used."
>
>It looks like, if you don't specify "any" (that is, if you let the button
>number default), then the /other/ buttons will _abort_ the kill.
>
>Try aborting by pressing the right (or centre) mouse button (assuming that
>you didn't specify that button as the kill button).
--
The randomly chosen signature file that would have appeared here is more than 4
lines long. As such, it violates one or more Usenet RFCs. In order to remain
in compliance with said RFCs, the actual sig can be found at the following URL:
Lew Pitcher
Jan 30, 2018, 7:02:44 PM1/30/18
to
Kenny McCormack wrote:
> In article <p4qtis$avs$1...@dont-email.me>,
> Lew Pitcher <lew.p...@digitalfreehold.ca> wrote:
>>Kenny McCormack wrote:
>>
>>> I've discovered something a little annoying about xkill.
>>>
>>> That is, there doesn't seem to be any way to get out of it without
>>> killing
>>> anything. Nothing in the man page suggests any way to do this.
>>
>>[snip]
>>> Am I missing something? Is there a way?
>>
>>The man page seems to give clues...
>> "If a pointer button is pressed over a non-root window, the server will
>> close its connection to the client that created the window."
>
> This implies that you can just click on the desktop background (which is a
> "root window" (right?)) and it will be a no-op (right?).
Given the default xkill commandline
> In article <p4qtis$avs$1...@dont-email.me>,
> Lew Pitcher <lew.p...@digitalfreehold.ca> wrote:
>>Kenny McCormack wrote:
>>
>>> I've discovered something a little annoying about xkill.
>>>
>>> That is, there doesn't seem to be any way to get out of it without
>>> killing
>>> anything. Nothing in the man page suggests any way to do this.
>>
>>[snip]
>>> Am I missing something? Is there a way?
>>
>>The man page seems to give clues...
>> "If a pointer button is pressed over a non-root window, the server will
>> close its connection to the client that created the window."
>
> This implies that you can just click on the desktop background (which is a
> "root window" (right?)) and it will be a no-op (right?).
xkill
I've tried a right-click on the desktop, which seems to dismiss xkill with
no side effects. YMMV
> I've had mixed results with this. On at least one occasion, my system
> started acting generally weird after this - and I'm pretty sure that some
> system-critical desktop process had, in fact, been killed. So, I've
> stayed away from this since then.
>
>> "-button number
>> This option specifies the number of pointer button that should be
>> used in selecting a window to kill. ... By default, the first
>> button in the pointer map (which is usually the left-most button) is
>> used."
>>
>>It looks like, if you don't specify "any" (that is, if you let the button
>>number default), then the /other/ buttons will _abort_ the kill.
>>
>>Try aborting by pressing the right (or centre) mouse button (assuming that
>>you didn't specify that button as the kill button).
>
> Yes. That works. Thanks.
Kenny McCormack
Jan 31, 2018, 1:11:09 AM1/31/18
to
In article <p4r133$8af$1...@dont-email.me>,
Lew Pitcher <lew.p...@digitalfreehold.ca> wrote:
...
established that right-clicking is the magic bullet for how to get out of
xkill without killing anything.
The issue is that before this thread's existence, I didn't know that and,
when I left clicked on the desktop (to get out of xkill), it killed something.
Anyway, it is all good, so no worries now.
--
When someone tells me he/she is a Christian I check to see if I'm
still in posession of my wallet.
Lew Pitcher <lew.p...@digitalfreehold.ca> wrote:
...
>> This implies that you can just click on the desktop background (which is a
>> "root window" (right?)) and it will be a no-op (right?).
>
>Given the default xkill commandline
> xkill
>I've tried a right-click on the desktop, which seems to dismiss xkill with
>no side effects. YMMV
Right - but that's because you "right clicked" and because we've now
>> "root window" (right?)) and it will be a no-op (right?).
>
>Given the default xkill commandline
> xkill
>I've tried a right-click on the desktop, which seems to dismiss xkill with
>no side effects. YMMV
established that right-clicking is the magic bullet for how to get out of
xkill without killing anything.
The issue is that before this thread's existence, I didn't know that and,
when I left clicked on the desktop (to get out of xkill), it killed something.
Anyway, it is all good, so no worries now.
--
When someone tells me he/she is a Christian I check to see if I'm
still in posession of my wallet.
Richard Tobin
Jan 31, 2018, 8:50:01 AM1/31/18
to
In article <p4rmls$aop$1...@news.xmission.com>,
for me. But I'm not using anything as sophisticated as a desktop,
just fwm2.
-- Richard
Kenny McCormack <gaz...@shell.xmission.com> wrote:
>>Given the default xkill commandline
>> xkill
>>I've tried a right-click on the desktop, which seems to dismiss xkill with
>>no side effects. YMMV
>Right - but that's because you "right clicked" and because we've now
>established that right-clicking is the magic bullet for how to get out of
>xkill without killing anything.
>
>The issue is that before this thread's existence, I didn't know that and,
>when I left clicked on the desktop (to get out of xkill), it killed something.
Left-clicking in the background makes it exit without killing anything
>>Given the default xkill commandline
>> xkill
>>I've tried a right-click on the desktop, which seems to dismiss xkill with
>>no side effects. YMMV
>Right - but that's because you "right clicked" and because we've now
>established that right-clicking is the magic bullet for how to get out of
>xkill without killing anything.
>
>The issue is that before this thread's existence, I didn't know that and,
>when I left clicked on the desktop (to get out of xkill), it killed something.
for me. But I'm not using anything as sophisticated as a desktop,
just fwm2.
-- Richard
Andre Majorel
Jan 31, 2018, 9:00:57 AM1/31/18
to
On 2018-01-30, Kenny McCormack <gaz...@shell.xmission.com> wrote:
> In article <p4qtis$avs$1...@dont-email.me>,
> Lew Pitcher <lew.p...@digitalfreehold.ca> wrote:
>> "If a pointer button is pressed over a non-root window, the server will
>> close its connection to the client that created the window."
>
> This implies that you can just click on the desktop background (which is a
> "root window" (right?)) and it will be a no-op (right?).
>
> I've had mixed results with this. On at least one occasion, my system
> started acting generally weird after this - and I'm pretty sure that some
> system-critical desktop process had, in fact, been killed. So, I've stayed
> away from this since then.
I seem to remember that some window managers create a
> In article <p4qtis$avs$1...@dont-email.me>,
> Lew Pitcher <lew.p...@digitalfreehold.ca> wrote:
>> "If a pointer button is pressed over a non-root window, the server will
>> close its connection to the client that created the window."
>
> This implies that you can just click on the desktop background (which is a
> "root window" (right?)) and it will be a no-op (right?).
>
> I've had mixed results with this. On at least one occasion, my system
> started acting generally weird after this - and I'm pretty sure that some
> system-critical desktop process had, in fact, been killed. So, I've stayed
> away from this since then.
pseudo-root window on top of the real one (don't ask me for what
purpose, that part escapes me now). xkill could conceivably be
fooled into thinking that it is a non-root window.
--
André Majorel http://www.teaser.fr/~amajorel/
Si le nationalisme est un vice, le patriotisme peut-il être une vertu ?
Spiros Bousbouras
Sep 18, 2018, 3:26:27 PM9/18/18
to
On Wed, 31 Jan 2018 06:11:08 +0000 (UTC)
gaz...@shell.xmission.com (Kenny McCormack) wrote:
> In article <p4r133$8af$1...@dont-email.me>,
> Lew Pitcher <lew.p...@digitalfreehold.ca> wrote:
> ...
> >> This implies that you can just click on the desktop background (which is a
> >> "root window" (right?)) and it will be a no-op (right?).
> >
> >Given the default xkill commandline
> > xkill
> >I've tried a right-click on the desktop, which seems to dismiss xkill with
> >no side effects. YMMV
>
> Right - but that's because you "right clicked" and because we've now
> established that right-clicking is the magic bullet for how to get out of
> xkill without killing anything.
>
> The issue is that before this thread's existence, I didn't know that and,
> when I left clicked on the desktop (to get out of xkill), it killed something.
>
> Anyway, it is all good, so no worries now.
If you're really curious , you can get the list of processes running before
gaz...@shell.xmission.com (Kenny McCormack) wrote:
> In article <p4r133$8af$1...@dont-email.me>,
> Lew Pitcher <lew.p...@digitalfreehold.ca> wrote:
> ...
> >> This implies that you can just click on the desktop background (which is a
> >> "root window" (right?)) and it will be a no-op (right?).
> >
> >Given the default xkill commandline
> > xkill
> >I've tried a right-click on the desktop, which seems to dismiss xkill with
> >no side effects. YMMV
>
> Right - but that's because you "right clicked" and because we've now
> established that right-clicking is the magic bullet for how to get out of
> xkill without killing anything.
>
> The issue is that before this thread's existence, I didn't know that and,
> when I left clicked on the desktop (to get out of xkill), it killed something.
>
> Anyway, it is all good, so no worries now.
starting xkill and compare it with the list of processes running after left
clicking on the root window. This way you can see if anything was killed.
Reply all
Reply to author
Forward
0 new messages