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
edited Jan 20 at 12:08
dessert
23.6k666103
asked Jan 20 at 11:54
KulfyKulfy
4,64151642
|
show 3 more comments
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
edited Jan 20 at 12:08
dessert
23.6k666103
asked Jan 20 at 11:54
KulfyKulfy
4,64151642
4
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
Jan 20 at 12:11
1
You should see the same behaviour with other GNOME applications (ones running in Wayland instead of running under the XWayland compatibility layer), e.g. Files, Documents etc.
– pomsky
Jan 20 at 13:45
1
@pomsky Is there anyway I can determine which application is running under which layer?
– Kulfy
Jan 20 at 14:27
1
"Is there anyway I can determine which application is running under which layer?" is a good question. Maybe worth a separate question thread at AskUbuntu :-)
– sudodus
Jan 20 at 14:52
1
@sudodus Yeah. But I think I should read more about Wayland. I'll try to have a self-answered Q&A later on.
– Kulfy
Jan 20 at 16:44
|
show 3 more comments
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
edited Jan 20 at 12:08
dessert
23.6k666103
asked Jan 20 at 11:54
KulfyKulfy
4,64151642
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 Jan 20 at 12:08
dessert
23.6k666103
asked Jan 20 at 11:54
KulfyKulfy
4,64151642
edited Jan 20 at 12:08
dessert
23.6k666103
asked Jan 20 at 11:54
KulfyKulfy
4,64151642
edited Jan 20 at 12:08
dessert
23.6k666103
edited Jan 20 at 12:08
dessert
23.6k666103
edited Jan 20 at 12:08
dessert
23.6k666103
23.6k666103
asked Jan 20 at 11:54
KulfyKulfy
4,64151642
asked Jan 20 at 11:54
KulfyKulfy
4,64151642
asked Jan 20 at 11:54
KulfyKulfy
4,64151642
4,64151642
4
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
Jan 20 at 12:11
1
You should see the same behaviour with other GNOME applications (ones running in Wayland instead of running under the XWayland compatibility layer), e.g. Files, Documents etc.
– pomsky
Jan 20 at 13:45
1
@pomsky Is there anyway I can determine which application is running under which layer?
– Kulfy
Jan 20 at 14:27
1
"Is there anyway I can determine which application is running under which layer?" is a good question. Maybe worth a separate question thread at AskUbuntu :-)
– sudodus
Jan 20 at 14:52
1
@sudodus Yeah. But I think I should read more about Wayland. I'll try to have a self-answered Q&A later on.
– Kulfy
Jan 20 at 16:44
|
show 3 more comments
4
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
Jan 20 at 12:11
1
You should see the same behaviour with other GNOME applications (ones running in Wayland instead of running under the XWayland compatibility layer), e.g. Files, Documents etc.
– pomsky
Jan 20 at 13:45
1
@pomsky Is there anyway I can determine which application is running under which layer?
– Kulfy
Jan 20 at 14:27
1
"Is there anyway I can determine which application is running under which layer?" is a good question. Maybe worth a separate question thread at AskUbuntu :-)
– sudodus
Jan 20 at 14:52
1
@sudodus Yeah. But I think I should read more about Wayland. I'll try to have a self-answered Q&A later on.
– Kulfy
Jan 20 at 16:44
4
4
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
Jan 20 at 12:11
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
Jan 20 at 12:11
1
1
You should see the same behaviour with other GNOME applications (ones running in Wayland instead of running under the XWayland compatibility layer), e.g. Files, Documents etc.
– pomsky
Jan 20 at 13:45
You should see the same behaviour with other GNOME applications (ones running in Wayland instead of running under the XWayland compatibility layer), e.g. Files, Documents etc.
– pomsky
Jan 20 at 13:45
1
1
@pomsky Is there anyway I can determine which application is running under which layer?
– Kulfy
Jan 20 at 14:27
@pomsky Is there anyway I can determine which application is running under which layer?
– Kulfy
Jan 20 at 14:27
1
1
"Is there anyway I can determine which application is running under which layer?" is a good question. Maybe worth a separate question thread at AskUbuntu :-)
– sudodus
Jan 20 at 14:52
"Is there anyway I can determine which application is running under which layer?" is a good question. Maybe worth a separate question thread at AskUbuntu :-)
– sudodus
Jan 20 at 14:52
1
1
@sudodus Yeah. But I think I should read more about Wayland. I'll try to have a self-answered Q&A later on.
– Kulfy
Jan 20 at 16:44
@sudodus Yeah. But I think I should read more about Wayland. I'll try to have a self-answered Q&A later on.
– Kulfy
Jan 20 at 16:44
|
show 3 more comments
2 Answers
2
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
answered Jan 20 at 12:01
Sergiy KolodyazhnyySergiy Kolodyazhnyy
72.5k9151316
4
I believe this isn't a bug but it is supposed to be like that.
– Kulfy
Jan 20 at 14:30
@Kulfy: Why do you think I don't use Wayland?
– Joshua
Jan 20 at 20:28
@Kulfy This may not be a bug in the sense of software being broken, but it is a bug in the sense that Wayland promises maintaining backward compatibility with X11 applications.
– Sergiy Kolodyazhnyy
Jan 20 at 20:53
@SergiyKolodyazhnyy Then why I was able to kill nautilus in Wayland by clicking on desktop? Is it because it was running under XWayland layer?
– Kulfy
Jan 21 at 7:34
@Kulfy Likely, yes. The quoted Fedora documentation mentions that. Nautilus may be an XWayland application, Gnome Terminal should be an XWayland application as well since it works in X11, unless there exists two versions of it. As for believing whether it's a valid bug or not, I would leave this to the upstream developers to decide. At the very least clarifications from the developers would be nice. Until then, we'll just have to rely on the cited articles.
– Sergiy Kolodyazhnyy
Jan 21 at 8:09
add a comment |
This is by design of Wayland.
As you are using Wayland, this is expected that you can not use X11 tool named xkill to kill a client by its X resource (part of x11-utils package) here.
Also you can not use xdotool, xinput (that is good as you will have more secure GUI) here and others.
answered Jan 20 at 11:59
N0rbertN0rbert
23.1k649110
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
2 Answers
2
active
oldest
votes
2 Answers
2
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
answered Jan 20 at 12:01
Sergiy KolodyazhnyySergiy Kolodyazhnyy
72.5k9151316
4
I believe this isn't a bug but it is supposed to be like that.
– Kulfy
Jan 20 at 14:30
@Kulfy: Why do you think I don't use Wayland?
– Joshua
Jan 20 at 20:28
@Kulfy This may not be a bug in the sense of software being broken, but it is a bug in the sense that Wayland promises maintaining backward compatibility with X11 applications.
– Sergiy Kolodyazhnyy
Jan 20 at 20:53
@SergiyKolodyazhnyy Then why I was able to kill nautilus in Wayland by clicking on desktop? Is it because it was running under XWayland layer?
– Kulfy
Jan 21 at 7:34
@Kulfy Likely, yes. The quoted Fedora documentation mentions that. Nautilus may be an XWayland application, Gnome Terminal should be an XWayland application as well since it works in X11, unless there exists two versions of it. As for believing whether it's a valid bug or not, I would leave this to the upstream developers to decide. At the very least clarifications from the developers would be nice. Until then, we'll just have to rely on the cited articles.
– Sergiy Kolodyazhnyy
Jan 21 at 8:09
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
answered Jan 20 at 12:01
Sergiy KolodyazhnyySergiy Kolodyazhnyy
72.5k9151316
4
I believe this isn't a bug but it is supposed to be like that.
– Kulfy
Jan 20 at 14:30
@Kulfy: Why do you think I don't use Wayland?
– Joshua
Jan 20 at 20:28
@Kulfy This may not be a bug in the sense of software being broken, but it is a bug in the sense that Wayland promises maintaining backward compatibility with X11 applications.
– Sergiy Kolodyazhnyy
Jan 20 at 20:53
@SergiyKolodyazhnyy Then why I was able to kill nautilus in Wayland by clicking on desktop? Is it because it was running under XWayland layer?
– Kulfy
Jan 21 at 7:34
@Kulfy Likely, yes. The quoted Fedora documentation mentions that. Nautilus may be an XWayland application, Gnome Terminal should be an XWayland application as well since it works in X11, unless there exists two versions of it. As for believing whether it's a valid bug or not, I would leave this to the upstream developers to decide. At the very least clarifications from the developers would be nice. Until then, we'll just have to rely on the cited articles.
– Sergiy Kolodyazhnyy
Jan 21 at 8:09
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
answered Jan 20 at 12:01
Sergiy KolodyazhnyySergiy Kolodyazhnyy
72.5k9151316
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 Jan 20 at 12:01
Sergiy KolodyazhnyySergiy Kolodyazhnyy
72.5k9151316
answered Jan 20 at 12:01
Sergiy KolodyazhnyySergiy Kolodyazhnyy
72.5k9151316
answered Jan 20 at 12:01
Sergiy KolodyazhnyySergiy Kolodyazhnyy
72.5k9151316
answered Jan 20 at 12:01
Sergiy KolodyazhnyySergiy Kolodyazhnyy
72.5k9151316
72.5k9151316
4
I believe this isn't a bug but it is supposed to be like that.
– Kulfy
Jan 20 at 14:30
@Kulfy: Why do you think I don't use Wayland?
– Joshua
Jan 20 at 20:28
@Kulfy This may not be a bug in the sense of software being broken, but it is a bug in the sense that Wayland promises maintaining backward compatibility with X11 applications.
– Sergiy Kolodyazhnyy
Jan 20 at 20:53
@SergiyKolodyazhnyy Then why I was able to kill nautilus in Wayland by clicking on desktop? Is it because it was running under XWayland layer?
– Kulfy
Jan 21 at 7:34
@Kulfy Likely, yes. The quoted Fedora documentation mentions that. Nautilus may be an XWayland application, Gnome Terminal should be an XWayland application as well since it works in X11, unless there exists two versions of it. As for believing whether it's a valid bug or not, I would leave this to the upstream developers to decide. At the very least clarifications from the developers would be nice. Until then, we'll just have to rely on the cited articles.
– Sergiy Kolodyazhnyy
Jan 21 at 8:09
add a comment |
4
I believe this isn't a bug but it is supposed to be like that.
– Kulfy
Jan 20 at 14:30
@Kulfy: Why do you think I don't use Wayland?
– Joshua
Jan 20 at 20:28
@Kulfy This may not be a bug in the sense of software being broken, but it is a bug in the sense that Wayland promises maintaining backward compatibility with X11 applications.
– Sergiy Kolodyazhnyy
Jan 20 at 20:53
@SergiyKolodyazhnyy Then why I was able to kill nautilus in Wayland by clicking on desktop? Is it because it was running under XWayland layer?
– Kulfy
Jan 21 at 7:34
@Kulfy Likely, yes. The quoted Fedora documentation mentions that. Nautilus may be an XWayland application, Gnome Terminal should be an XWayland application as well since it works in X11, unless there exists two versions of it. As for believing whether it's a valid bug or not, I would leave this to the upstream developers to decide. At the very least clarifications from the developers would be nice. Until then, we'll just have to rely on the cited articles.
– Sergiy Kolodyazhnyy
Jan 21 at 8:09
4
4
I believe this isn't a bug but it is supposed to be like that.
– Kulfy
Jan 20 at 14:30
I believe this isn't a bug but it is supposed to be like that.
– Kulfy
Jan 20 at 14:30
@Kulfy: Why do you think I don't use Wayland?
– Joshua
Jan 20 at 20:28
@Kulfy: Why do you think I don't use Wayland?
– Joshua
Jan 20 at 20:28
@Kulfy This may not be a bug in the sense of software being broken, but it is a bug in the sense that Wayland promises maintaining backward compatibility with X11 applications.
– Sergiy Kolodyazhnyy
Jan 20 at 20:53
@Kulfy This may not be a bug in the sense of software being broken, but it is a bug in the sense that Wayland promises maintaining backward compatibility with X11 applications.
– Sergiy Kolodyazhnyy
Jan 20 at 20:53
@SergiyKolodyazhnyy Then why I was able to kill nautilus in Wayland by clicking on desktop? Is it because it was running under XWayland layer?
– Kulfy
Jan 21 at 7:34
@SergiyKolodyazhnyy Then why I was able to kill nautilus in Wayland by clicking on desktop? Is it because it was running under XWayland layer?
– Kulfy
Jan 21 at 7:34
@Kulfy Likely, yes. The quoted Fedora documentation mentions that. Nautilus may be an XWayland application, Gnome Terminal should be an XWayland application as well since it works in X11, unless there exists two versions of it. As for believing whether it's a valid bug or not, I would leave this to the upstream developers to decide. At the very least clarifications from the developers would be nice. Until then, we'll just have to rely on the cited articles.
– Sergiy Kolodyazhnyy
Jan 21 at 8:09
@Kulfy Likely, yes. The quoted Fedora documentation mentions that. Nautilus may be an XWayland application, Gnome Terminal should be an XWayland application as well since it works in X11, unless there exists two versions of it. As for believing whether it's a valid bug or not, I would leave this to the upstream developers to decide. At the very least clarifications from the developers would be nice. Until then, we'll just have to rely on the cited articles.
– Sergiy Kolodyazhnyy
Jan 21 at 8:09
add a comment |
This is by design of Wayland.
As you are using Wayland, this is expected that you can not use X11 tool named xkill to kill a client by its X resource (part of x11-utils package) here.
Also you can not use xdotool, xinput (that is good as you will have more secure GUI) here and others.
answered Jan 20 at 11:59
N0rbertN0rbert
23.1k649110
add a comment |
This is by design of Wayland.
As you are using Wayland, this is expected that you can not use X11 tool named xkill to kill a client by its X resource (part of x11-utils package) here.
Also you can not use xdotool, xinput (that is good as you will have more secure GUI) here and others.
answered Jan 20 at 11:59
N0rbertN0rbert
23.1k649110
add a comment |
This is by design of Wayland.
As you are using Wayland, this is expected that you can not use X11 tool named xkill to kill a client by its X resource (part of x11-utils package) here.
Also you can not use xdotool, xinput (that is good as you will have more secure GUI) here and others.
answered Jan 20 at 11:59
N0rbertN0rbert
23.1k649110
This is by design of Wayland.
As you are using Wayland, this is expected that you can not use X11 tool named xkill to kill a client by its X resource (part of x11-utils package) here.
Also you can not use xdotool, xinput (that is good as you will have more secure GUI) here and others.
answered Jan 20 at 11:59
N0rbertN0rbert
23.1k649110
edited Jan 20 at 12:15
answered Jan 20 at 11:59
N0rbertN0rbert
23.1k649110
answered Jan 20 at 11:59
N0rbertN0rbert
23.1k649110
answered Jan 20 at 11:59
N0rbertN0rbert
23.1k649110
23.1k649110
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
4
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
Jan 20 at 12:11
1
You should see the same behaviour with other GNOME applications (ones running in Wayland instead of running under the XWayland compatibility layer), e.g. Files, Documents etc.
– pomsky
Jan 20 at 13:45
1
@pomsky Is there anyway I can determine which application is running under which layer?
– Kulfy
Jan 20 at 14:27
1
"Is there anyway I can determine which application is running under which layer?" is a good question. Maybe worth a separate question thread at AskUbuntu :-)
– sudodus
Jan 20 at 14:52
1
@sudodus Yeah. But I think I should read more about Wayland. I'll try to have a self-answered Q&A later on.
– Kulfy
Jan 20 at 16:44