Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The "move" command doesn't work anymore (macOS Monterey 12.6.3) #168

Open
alin89c opened this issue Apr 26, 2023 · 9 comments
Open

The "move" command doesn't work anymore (macOS Monterey 12.6.3) #168

alin89c opened this issue Apr 26, 2023 · 9 comments

Comments

@alin89c
Copy link

alin89c commented Apr 26, 2023

First I got this warning in Terminal:
WARNING: Accessibility privileges not enabled. Many actions may fail.
Enable the checkbox for the containing app in:
System Preferences → Security & Privacy → Accessibility

Then, after enabling the checkbox for the containing app (Terminal and Script Editor), I ran "cliclick m:0,0" (got no warning this time, but the mouse pointer still didn't move). The "click" command works though...

Is this a known issue? Is there anything I can do to fix this problem I have with cliclick? Thank you!

@joelc0193
Copy link

joelc0193 commented Jun 3, 2023

Looks like it works if you move the cursor at least twice:

cliclick m:0,0 m:100,100

@alin89c
Copy link
Author

alin89c commented Jun 3, 2023

Hi, and thanks! Tried it and it works (on my OpenCore Ventura 13.3.1 Retina Mid 2012 MacBook Pro). Good job!

@joelc0193
Copy link

Hi, and thanks! Tried it and it works (on my OpenCore Ventura 13.3.1 Retina Mid 2012 MacBook Pro). Good job!

is was ChatGPT who gave me the idea while debugging

@BlueM
Copy link
Owner

BlueM commented Jul 22, 2023

As I haven’t been able to reproduce this behavior (neither #169 on a different Mac running macOS 13), I don’t see how I could provide a fix.

@shuiwujiao
Copy link

ChatGPT suggests that the terminal application itself may not be authorized to use "accessibility". For example, if you connect through a terminal or sshd, you need to allow the terminal or sshd to use "accessibility".
This method works well on my PC.

@BlueM
Copy link
Owner

BlueM commented Sep 18, 2023

@shuiwujiao: the author of the issue mentioned he did grant the accessibility privileges.

@alin89c
Copy link
Author

alin89c commented Sep 19, 2023

Maybe this issue is related only to Macs running an officially unsupported MacOS... Good thing I have this workaround (to input the values twice).

@jamesdh
Copy link

jamesdh commented Mar 20, 2024

I just now tried cliclick myself for the first time and experienced this issue. @joelc0193's comment worked for me also.

@jamesdh
Copy link

jamesdh commented Mar 20, 2024

@BlueM for what it's worth, I only experience this bug using iTerm. It doesn't reproduce using Terminal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants