Equivalent to xdotool for Wayland
up vote
11
down vote
favorite
I'm looking for a solution working in Wayland to get mouse position, move it and click inside a bash
script, all things xdotool
can do for X server.
xdotool getmouselocation
is still working, but
xdotool mousemove
xdotool click
have no impact on the mouse cursor in GNOME Wayland session.
scripts wayland xdotool
add a comment |
up vote
11
down vote
favorite
I'm looking for a solution working in Wayland to get mouse position, move it and click inside a bash
script, all things xdotool
can do for X server.
xdotool getmouselocation
is still working, but
xdotool mousemove
xdotool click
have no impact on the mouse cursor in GNOME Wayland session.
scripts wayland xdotool
2
See also superuser.com/questions/1032270/… and unix.stackexchange.com/questions/381831/…
– Ben Creasy
Feb 18 at 9:32
add a comment |
up vote
11
down vote
favorite
up vote
11
down vote
favorite
I'm looking for a solution working in Wayland to get mouse position, move it and click inside a bash
script, all things xdotool
can do for X server.
xdotool getmouselocation
is still working, but
xdotool mousemove
xdotool click
have no impact on the mouse cursor in GNOME Wayland session.
scripts wayland xdotool
I'm looking for a solution working in Wayland to get mouse position, move it and click inside a bash
script, all things xdotool
can do for X server.
xdotool getmouselocation
is still working, but
xdotool mousemove
xdotool click
have no impact on the mouse cursor in GNOME Wayland session.
scripts wayland xdotool
scripts wayland xdotool
edited Nov 18 '17 at 20:12
dessert
21.3k55896
21.3k55896
asked Sep 17 '17 at 9:37
mxdsp
2,36611846
2,36611846
2
See also superuser.com/questions/1032270/… and unix.stackexchange.com/questions/381831/…
– Ben Creasy
Feb 18 at 9:32
add a comment |
2
See also superuser.com/questions/1032270/… and unix.stackexchange.com/questions/381831/…
– Ben Creasy
Feb 18 at 9:32
2
2
See also superuser.com/questions/1032270/… and unix.stackexchange.com/questions/381831/…
– Ben Creasy
Feb 18 at 9:32
See also superuser.com/questions/1032270/… and unix.stackexchange.com/questions/381831/…
– Ben Creasy
Feb 18 at 9:32
add a comment |
1 Answer
1
active
oldest
votes
up vote
3
down vote
This is because such features have been explicitly removed from Wayland for security reasons. The major concerns were reading other programs input and allowing fake input to be sent to other programs which would allow different attack vectors.
Some window-managers might implement some sort of macro feature in the future but as of now there is no such feature that I know of.
Implementing this would mean to implement it for each of the different window managers which surely will take still a while.
I suggest using Xorg instead of Wayland for now if you need to use such features.
1
I don't know if you are aware of any of the discussions, but there was a RFC on a mailing list: RFC: Interface for injection of input events and Add an API for taking screenshots and recording screencasts. It sounds like the challenges could be addressed with some additional hardening work.
– Ben Creasy
Feb 18 at 9:36
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
This is because such features have been explicitly removed from Wayland for security reasons. The major concerns were reading other programs input and allowing fake input to be sent to other programs which would allow different attack vectors.
Some window-managers might implement some sort of macro feature in the future but as of now there is no such feature that I know of.
Implementing this would mean to implement it for each of the different window managers which surely will take still a while.
I suggest using Xorg instead of Wayland for now if you need to use such features.
1
I don't know if you are aware of any of the discussions, but there was a RFC on a mailing list: RFC: Interface for injection of input events and Add an API for taking screenshots and recording screencasts. It sounds like the challenges could be addressed with some additional hardening work.
– Ben Creasy
Feb 18 at 9:36
add a comment |
up vote
3
down vote
This is because such features have been explicitly removed from Wayland for security reasons. The major concerns were reading other programs input and allowing fake input to be sent to other programs which would allow different attack vectors.
Some window-managers might implement some sort of macro feature in the future but as of now there is no such feature that I know of.
Implementing this would mean to implement it for each of the different window managers which surely will take still a while.
I suggest using Xorg instead of Wayland for now if you need to use such features.
1
I don't know if you are aware of any of the discussions, but there was a RFC on a mailing list: RFC: Interface for injection of input events and Add an API for taking screenshots and recording screencasts. It sounds like the challenges could be addressed with some additional hardening work.
– Ben Creasy
Feb 18 at 9:36
add a comment |
up vote
3
down vote
up vote
3
down vote
This is because such features have been explicitly removed from Wayland for security reasons. The major concerns were reading other programs input and allowing fake input to be sent to other programs which would allow different attack vectors.
Some window-managers might implement some sort of macro feature in the future but as of now there is no such feature that I know of.
Implementing this would mean to implement it for each of the different window managers which surely will take still a while.
I suggest using Xorg instead of Wayland for now if you need to use such features.
This is because such features have been explicitly removed from Wayland for security reasons. The major concerns were reading other programs input and allowing fake input to be sent to other programs which would allow different attack vectors.
Some window-managers might implement some sort of macro feature in the future but as of now there is no such feature that I know of.
Implementing this would mean to implement it for each of the different window managers which surely will take still a while.
I suggest using Xorg instead of Wayland for now if you need to use such features.
edited Nov 18 '17 at 20:10
dessert
21.3k55896
21.3k55896
answered Nov 18 '17 at 18:02
Videonauth
23.4k126898
23.4k126898
1
I don't know if you are aware of any of the discussions, but there was a RFC on a mailing list: RFC: Interface for injection of input events and Add an API for taking screenshots and recording screencasts. It sounds like the challenges could be addressed with some additional hardening work.
– Ben Creasy
Feb 18 at 9:36
add a comment |
1
I don't know if you are aware of any of the discussions, but there was a RFC on a mailing list: RFC: Interface for injection of input events and Add an API for taking screenshots and recording screencasts. It sounds like the challenges could be addressed with some additional hardening work.
– Ben Creasy
Feb 18 at 9:36
1
1
I don't know if you are aware of any of the discussions, but there was a RFC on a mailing list: RFC: Interface for injection of input events and Add an API for taking screenshots and recording screencasts. It sounds like the challenges could be addressed with some additional hardening work.
– Ben Creasy
Feb 18 at 9:36
I don't know if you are aware of any of the discussions, but there was a RFC on a mailing list: RFC: Interface for injection of input events and Add an API for taking screenshots and recording screencasts. It sounds like the challenges could be addressed with some additional hardening work.
– Ben Creasy
Feb 18 at 9:36
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f956640%2fequivalent-to-xdotool-for-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
2
See also superuser.com/questions/1032270/… and unix.stackexchange.com/questions/381831/…
– Ben Creasy
Feb 18 at 9:32