Why can't I kill a terminal window with xkill in Wayland?
When I run xkill in terminal a X (cross sign) appears which seems to kill that GUI process (application) on which it is hovered and clicked. I expect the same behavior for GNOME Terminal (since in my understanding it is also a GUI application). But I get different behaviors under different display manager.
Under x11:

Under Wayland:

It seems xkill can't kill terminal in Wayland.
command-line xorg wayland xkill
add a comment |
When I run xkill in terminal a X (cross sign) appears which seems to kill that GUI process (application) on which it is hovered and clicked. I expect the same behavior for GNOME Terminal (since in my understanding it is also a GUI application). But I get different behaviors under different display manager.
Under x11:

Under Wayland:

It seems xkill can't kill terminal in Wayland.
command-line xorg wayland xkill
1
Note that Wayland is not a display manager but rather a display server protocol, which is a rather big difference. X server software likexkilldoes very well work in (supposedly all) different X display managers, but naturally not in Wayland ones – and the other way around.
– dessert
50 mins ago
add a comment |
When I run xkill in terminal a X (cross sign) appears which seems to kill that GUI process (application) on which it is hovered and clicked. I expect the same behavior for GNOME Terminal (since in my understanding it is also a GUI application). But I get different behaviors under different display manager.
Under x11:

Under Wayland:

It seems xkill can't kill terminal in Wayland.
command-line xorg wayland xkill
When I run xkill in terminal a X (cross sign) appears which seems to kill that GUI process (application) on which it is hovered and clicked. I expect the same behavior for GNOME Terminal (since in my understanding it is also a GUI application). But I get different behaviors under different display manager.
Under x11:

Under Wayland:

It seems xkill can't kill terminal in Wayland.
command-line xorg wayland xkill
command-line xorg wayland xkill
edited 53 mins ago
dessert
22.4k56198
22.4k56198
asked 1 hour ago
KulfyKulfy
4,26151342
4,26151342
1
Note that Wayland is not a display manager but rather a display server protocol, which is a rather big difference. X server software likexkilldoes very well work in (supposedly all) different X display managers, but naturally not in Wayland ones – and the other way around.
– dessert
50 mins ago
add a comment |
1
Note that Wayland is not a display manager but rather a display server protocol, which is a rather big difference. X server software likexkilldoes very well work in (supposedly all) different X display managers, but naturally not in Wayland ones – and the other way around.
– dessert
50 mins ago
1
1
Note that Wayland is not a display manager but rather a display server protocol, which is a rather big difference. X server software like
xkill does very well work in (supposedly all) different X display managers, but naturally not in Wayland ones – and the other way around.– dessert
50 mins ago
Note that Wayland is not a display manager but rather a display server protocol, which is a rather big difference. X server software like
xkill does very well work in (supposedly all) different X display managers, but naturally not in Wayland ones – and the other way around.– dessert
50 mins ago
add a comment |
1 Answer
1
active
oldest
votes
According to a bug report and response by Jean-Batiste Lallement:
This is a known issue with wayland documented upstream on
https://fedoraproject.org/wiki/How_to_debug_Wayland_problems#Many_well-known_X11_utilities_don.27t_work
Don't hesitate to file any bug you may find.
To quote Fedora documentation:
Power users are familiar with a large range of X11-related utilities,
like xkill, xrandr, xdotool, xsel. These tools won’t work under
Wayland session, or will only work with XWayland applications but not
Wayland applications. Some tools might have a replacement which allows
to perform similar tasks.
Thus, it's a well known issue. You may want to submit a bug report (and probably it will be marked a duplicate) or wait until upstream fixes things.
For the time being, you may want to stick with the pkill or kill in terminal
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1111346%2fwhy-cant-i-kill-a-terminal-window-with-xkill-in-wayland%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
According to a bug report and response by Jean-Batiste Lallement:
This is a known issue with wayland documented upstream on
https://fedoraproject.org/wiki/How_to_debug_Wayland_problems#Many_well-known_X11_utilities_don.27t_work
Don't hesitate to file any bug you may find.
To quote Fedora documentation:
Power users are familiar with a large range of X11-related utilities,
like xkill, xrandr, xdotool, xsel. These tools won’t work under
Wayland session, or will only work with XWayland applications but not
Wayland applications. Some tools might have a replacement which allows
to perform similar tasks.
Thus, it's a well known issue. You may want to submit a bug report (and probably it will be marked a duplicate) or wait until upstream fixes things.
For the time being, you may want to stick with the pkill or kill in terminal
add a comment |
According to a bug report and response by Jean-Batiste Lallement:
This is a known issue with wayland documented upstream on
https://fedoraproject.org/wiki/How_to_debug_Wayland_problems#Many_well-known_X11_utilities_don.27t_work
Don't hesitate to file any bug you may find.
To quote Fedora documentation:
Power users are familiar with a large range of X11-related utilities,
like xkill, xrandr, xdotool, xsel. These tools won’t work under
Wayland session, or will only work with XWayland applications but not
Wayland applications. Some tools might have a replacement which allows
to perform similar tasks.
Thus, it's a well known issue. You may want to submit a bug report (and probably it will be marked a duplicate) or wait until upstream fixes things.
For the time being, you may want to stick with the pkill or kill in terminal
add a comment |
According to a bug report and response by Jean-Batiste Lallement:
This is a known issue with wayland documented upstream on
https://fedoraproject.org/wiki/How_to_debug_Wayland_problems#Many_well-known_X11_utilities_don.27t_work
Don't hesitate to file any bug you may find.
To quote Fedora documentation:
Power users are familiar with a large range of X11-related utilities,
like xkill, xrandr, xdotool, xsel. These tools won’t work under
Wayland session, or will only work with XWayland applications but not
Wayland applications. Some tools might have a replacement which allows
to perform similar tasks.
Thus, it's a well known issue. You may want to submit a bug report (and probably it will be marked a duplicate) or wait until upstream fixes things.
For the time being, you may want to stick with the pkill or kill in terminal
According to a bug report and response by Jean-Batiste Lallement:
This is a known issue with wayland documented upstream on
https://fedoraproject.org/wiki/How_to_debug_Wayland_problems#Many_well-known_X11_utilities_don.27t_work
Don't hesitate to file any bug you may find.
To quote Fedora documentation:
Power users are familiar with a large range of X11-related utilities,
like xkill, xrandr, xdotool, xsel. These tools won’t work under
Wayland session, or will only work with XWayland applications but not
Wayland applications. Some tools might have a replacement which allows
to perform similar tasks.
Thus, it's a well known issue. You may want to submit a bug report (and probably it will be marked a duplicate) or wait until upstream fixes things.
For the time being, you may want to stick with the pkill or kill in terminal
answered 59 mins ago
Sergiy KolodyazhnyySergiy Kolodyazhnyy
71.1k9147312
71.1k9147312
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1111346%2fwhy-cant-i-kill-a-terminal-window-with-xkill-in-wayland%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Note that Wayland is not a display manager but rather a display server protocol, which is a rather big difference. X server software like
xkilldoes very well work in (supposedly all) different X display managers, but naturally not in Wayland ones – and the other way around.– dessert
50 mins ago